Lovable app deployment
Deploy an app built with Lovable to production.
Keep the source generated in Lovable, sync it to GitHub, and move it into an Adios workspace for a real production build, preview, diagnostics, and an approval-gated release.
Source to production
- 01Lovable source
- 02Adios workspace
- 03Build + preview + logs
- 04Human production approval
Production stays separated from the agent's preparation work until you approve the release.
Source
Reviewable files and config
Preview
Healthy before production
Evidence
Build output and runtime logs
Control
Human approval gate
Deployable projects
Keep the generated app. Add the production contract.
Adios works from the project source and its normal framework commands. It does not require the app to be regenerated in a proprietary format.
- Lovable React and Vite web applications
- Supabase-connected frontends
- Web apps that call external APIs
- Projects that need custom domains, secrets, and runtime logs
GitHub source handoff
Move the Lovable source—not just the preview.
Connect the Lovable project to GitHub from Settings → Connectors → GitHub. Lovable creates and syncs the repository; Adios can then work from that durable source history rather than a copied build artifact.
Lovable project
→ Settings → Connectors → GitHub
→ Synced GitHub repository
→ Adios workspaceExample agent prompt
Ask for a verified release, not only a deploy command.
Use this in the Adios AI workspace after the Lovable project is synced to GitHub.
“Import this Lovable repository into an Adios workspace. Inspect the Vite or React build, identify every required public and server-side environment variable, create adios.yaml, run a production build, open a preview, and report any source or configuration changes before production approval.”
Reviewable configuration
The agent writes down how the app should run.
The exact manifest should match the repository. This example makes a conventional Node.js production build, port, and health endpoint explicit so the release can be reviewed and repeated.
Learn how adios.yaml worksname: vibe-app
region: de
build_cmd: npm ci && npm run build
start_cmd: npm start
runtime:
name: node@24
port: 3000
health_path: /api/healthSource-to-release workflow
Five checks between generated code and production.
- 01
Inspect the project source
Identify the framework, package manager, build output, start command, expected port, environment variables, and any stateful services before creating a release.
- 02
Make the runtime contract visible
Write or update adios.yaml so the build command, start command, runtime, port, health check, secrets, and managed resources can be reviewed beside the code.
- 03
Build and open a preview
Run the production build in an isolated workspace, start the application, and inspect a preview URL before treating the project as deployable.
- 04
Read logs and repair failures
Use build output, runtime logs, and the configured health path to diagnose failures. Apply the fix to source, then rebuild the same project rather than patching production by hand.
- 05
Review and approve production
Check the final source diff, configuration, preview, and health result. A person approves the production deployment after the agent has prepared a healthy release.
When the build fails
Give the agent evidence it can act on.
A Lovable preview can hide assumptions that surface in a clean production build, such as missing environment variables or a client-side routing fallback. Adios keeps the failure, source change, and rebuilt preview in the same reviewable workflow.
build · failed
↓ inspect output
source + adios.yaml · updated
↓ rebuild and health check
preview · healthy
↓ human review
production · ready for approval
Framework deployment
Match the generated project to its runtime.
Deploy React
Vite and other React frontends served as static or Node-backed applications.
Open runtime guideDeploy Next.js
Server-rendered routes, route handlers, static output, and persistent Node.js apps.
Open runtime guideDeploy Postgres
Managed relational data for apps that need durable state and a private connection string.
Open runtime guideFAQ
Deploying Lovable apps with Adios.
Does Adios import a Lovable project directly?
The reliable handoff is the project source in GitHub. Connect Lovable to GitHub, let it sync the repository, and use that repository as the source for the Adios workspace and deployment.
Can I keep editing in Lovable after connecting GitHub?
Lovable documents two-way GitHub sync for a connected project. Coordinate branches and commits carefully so changes made in Lovable, locally, or through an Adios workspace do not overwrite one another.
Does Adios deploy only Next.js apps?
No. Adios supports explicit build and start commands for common frontend, full-stack, API, worker, and data-backed projects. The detected framework changes the runtime contract; the source-to-preview-to-production workflow stays consistent.
Can the AI agent deploy to production without approval?
No. The agent can prepare source, configuration, builds, previews, and diagnostics, but the production transition is approval-gated so a person can review the release first.
What happens when the production build fails?
The build output and runtime logs remain available to the workspace. The agent can use that evidence to update the source or configuration and run a new build before asking for production approval.
Vibe coding tools
Deploy from another AI coding workflow.
From source to healthy release
Let Lovable prepare the deploy. Keep production approval yours.
Start with the source you already have, verify it in an Adios preview, and promote only the release you reviewed.
Start free trial