Skip to main content
When your app is ready for your team, click Publish to publish it to a production URL. Vybe handles the entire build and deployment process — you do not need to configure hosting, CI/CD pipelines, or infrastructure.

​
How to deploy

1

Open your app in the editor

Navigate to the app you want to deploy. Make sure you have tested it in the preview and are satisfied with the current state.
2

Click Publish

Click the Publish button in the editor toolbar. Vybe begins building your app immediately.
3

Wait for deployment to complete

After clicking Publish, you’ll see a Publishing indicator while Vybe builds and deploys your app.
4

Access your live app

Your app is now live at its production URL:
https://<app-slug>-<org-slug>.vybe.build
Share this URL with your team. Only authenticated members of your organization with access to the app can view it.
Make sure your app builds successfully in the preview before deploying. You can ask the AI to run type checks to catch errors early.

​
What happens during deployment

When you click Deploy, Vybe runs through several steps behind the scenes:
  1. Build — Your Next.js app is compiled and optimized for production
  2. Environment injection — Database URLs, API keys, integration credentials, and server secrets are securely injected as environment variables
  3. Deploy — The built app is deployed to Vercel’s infrastructure with HTTPS and automatic scaling
  4. Register — Your production URL is activated and ready to serve traffic
The first time you deploy an app, Vybe creates a new Vercel project for it. Subsequent deployments update the existing project with your latest changes.

​
Handling deployment errors

If a deployment fails, Vybe displays the error details:
  • Error message — A description of what went wrong
  • Failed step — Which stage of the pipeline failed (build, deploy, etc.)
Common causes of deployment errors include:
  • TypeScript compilation errors in your code
  • Missing or misconfigured dependencies
  • Invalid environment variable references
Review the error details, fix the issue in the editor (or ask the AI to help), and deploy again.

​
Redeploying

After making changes to your app, click Deploy again to publish the updated version. Each deployment creates a new version of your app, replacing the previous one at the same production URL. There is no limit to how many times you can deploy. You can iterate quickly — make a change, deploy, test with your team, and repeat.

​
Deployment history

Vybe tracks your deployment history so you can see when each version was published and whether it succeeded or failed. This gives you a timeline of changes to your production app and helps you trace issues back to specific deployments.

​
What is next