Stackado integrations
Vercel integration
Connect your Vercel account to publish Sudio sites in projects you own, follow deployment progress, and manage the site's domains.
When you need this integration
Use it for Connected publishing, where your GitHub repository and Vercel project stay in your own accounts. Managed publishing uses hosting operated by Stackado and does not require you to connect a personal Vercel account. A site that only sends changes to GitHub can continue using its existing deployment setup.
Before you connect
- Sign in to the Stackado workspace that owns the site.
- Use an account with permission to manage the site's publishing providers.
- Have access to the Vercel account or team where you want the site hosted.
- Connect GitHub too if you will publish through Sudio. GitHub authorizes repository access separately from Vercel.
Connect Vercel
- Open Sudio from Stackado and open your site.
- Open Publish, expand the publishing settings, and find Connected providers.
- Select Connect Vercel. On Vercel's own screen, choose the intended account or team and review the project access and permissions before installing.
- Return to Sudio and check that the Vercel connection is shown as connected. Once GitHub and Vercel are both connected, choose Connected under Ownership when you want the site published in your accounts.
Always start the connection from Sudio. The return must match the workspace, person and browser session that started setup. Opening a Vercel installation link on its own can return an expired-setup message; start again with Connect Vercel. If that action reports that the integration is unavailable, contact Stackado support.
What access you approve
| Permission | Access | Purpose |
|---|---|---|
| Projects | Read and write | Find and create projects and manage their settings. |
| Deployments | Read and write | Start and cancel builds, read build logs, and follow deployment progress. |
| Domains | Read and write | Connect, verify, redirect and remove site addresses. |
| Project environment variables | Read and write | Manage integration-owned runtime settings that connect your published site to Stackado. |
| Team and current user | Read | Identify the connected account and check that access still works. |
| Integration configuration | Read | The basic installation permission required by Vercel. |
Vercel controls which projects the installation can access. To review or change that access, open the Stackado installation under Integrations in your Vercel dashboard. Stackado does not ask for billing access or permission to manage all environment variables across your account.
Preview, publish and deployment updates
Connecting Vercel does not publish the site. In Sudio, build a preview, review it, then confirm publishing when it is ready. Moving an existing site between Managed and Connected ownership has its own confirmation.
Sudio receives deployment-created, succeeded, failed and cancelled events from Vercel and updates the release status. If an event is delayed, Sudio can check the build with Vercel. A build error is shown as an error; the site is only marked published once the release has completed.
If you use an access token
Sudio also offers Connect Vercel with an access token in its publishing settings. Use that protected form, with the team ID if needed. Do not put the token in a chat or support message. Token connections check builds directly with Vercel and do not receive integration webhooks.
Reconnect or remove access
If the connection needs attention, check that you still have access to the Vercel team and the selected projects, then reconnect from Sudio. For an expired return or an ended Stackado session, sign in again and restart setup in the same browser. If you cancelled setup on Vercel, no connection was completed.
To remove the installation, open Integrations in Vercel and uninstall Stackado. Sudio marks the removed connection as disconnected and stops using it for future publishing. If you connected with an access token, delete that token in your Vercel account to revoke its access. Sudio will need a new connection before it can publish again. Existing sites are not deleted by Sudio when you disconnect.
Your data and terms
Sudio stores the Vercel access token encrypted and keeps connection, project, deployment and domain information needed to operate publishing. Vercel receives the project configuration, site code and runtime settings needed to build and host the site. Our Privacy Policy explains data handling, retention and how to request access or deletion. The Stackado Terms of Service, including the use license, apply to this integration. Your use of Vercel also remains subject to Vercel's own terms and charges.
Get help
Contact Stackado support or email hello@stackado.com. We reply within one business day. Include your workspace, the site address, the error message and when it happened. Keep access tokens, secrets and environment-variable values out of the message.
For other connected accounts, read the Integration Hub guide.