Before you begin
- Use a saved project you can open in the editor and a plan with Pro publishing access.
- Have access to the Vercel account or team that will own the deployment.
- Review your pages and choose the intended HTML, React or Vue project output.
Connect and deploy
- 1
Open Publish
Choose Publish in the editor toolbar. If prompted, choose Connect Vercel and authorize the intended Vercel account or team. You can also manage the connection from Integrations.
- 2
Choose the destination
Under Destination, choose Create new Vercel project or an existing project you can access. For a new project, enter a lowercase project name using letters, numbers and hyphens.
- 3
Choose the environment
Select Preview to check a deployment before going live, or Production to deploy to the project’s live site.
- 4
Start the deployment
Choose Create preview or Publish to Production. Wait for the deployment to finish, then use Open site to review the result.
Match the application framework
Choose an existing Vercel project with a compatible framework and its root directory set to the repository root. The selected project’s build settings apply. If the existing settings belong to a different application, choose a compatible project or create a new one.
| Project output | Generated application |
|---|---|
| React | Next.js |
| Vue | Nuxt |
| HTML | HTML / Vite |
Set environment variables
Environment variables are managed in Vercel; the Unbondr publish dialog does not collect them. If the first deployment creates a new project but fails because values are missing, add the values to that created project and select it as the destination for the next deployment.
Use the destination application’s normal rules for public and server-only variables. Adding a variable does not create application logic or a backend that is not part of the generated project.
- 1
Open the project in Vercel
Open the exact Vercel project selected in Unbondr, then go to its Settings → Environment Variables.
- 2
Add the values your application needs
Enter each variable name and value. Apply it to Preview, Production, or both, according to the environments you intend to deploy.
- 3
Deploy again
Return to Unbondr, select the same Vercel project and environment, and deploy again. A new deployment uses the applicable project environment variables.
Publish an updated version
Saving in the editor does not automatically deploy. Repeat Publish after the changes you want to release. A Preview deployment does not replace the Production site; choose Production when you intend to update the live project.
Direct publishing does not require a GitHub push first. Your hosting remains in your Vercel account and follows that account’s usage and plan.
- 1
Edit and save
Make the next changes to your visual pages in the same builder project.
- 2
Select the existing Vercel project
Open Publish and select the previously used project under Destination. Choose the intended Preview or Production environment.
- 3
Deploy the latest version
Choose Create preview, Publish to Production, or Deploy again, depending on the current dialog state. Wait for the new deployment to finish and review its result.
Check deployment status and errors
| Message or symptom | What to check |
|---|---|
| Deployment is building or queued | Wait for the result in the publish dialog. If status checks stop, choose Resume status checks when available. |
| Build failed | Open Vercel for build logs. Check the actual build error, required environment variables and the selected project’s build settings before deploying again. |
| Framework or root directory mismatch | Choose a compatible project at the repository root, or create a new Vercel project. |
| Connection, account or team permission error | Reconnect the intended Vercel account or team and confirm access to the selected project. |
| Invalid request or rejected project settings | Read the detailed error and check the destination name, framework and project settings. Repeating the same request without correcting the cause will not change the result. |