U
Undasite
Deploy · Bots · Analysis

Undasite

Undasite + Vercel

Deploy your Undasite trading sites to your own Vercel account.

Last updated 23 August 2026

What this integration does

Undasite is an app builder for white-label Deriv trading sites, bots, and analysis tools. When you connect Vercel, new sites are created as projects on your Vercel team — not on a shared Undasite host. You keep hosting, billing, and custom domains on an account you control.

Connect from Undasite

  • Sign in at undasite.com.
  • Open Settings and go to Vercel hosting.
  • Choose Connect with Vercel. Approve the team (and projects, if asked) on Vercel.
  • You are returned to Undasite. Settings should show Vercel connected. You can then deploy from App Builder.

You must be signed in to Undasite before you start Connect. If you are not, sign in first, then try again so the one-time authorization code is not wasted.

What Undasite is allowed to do

After you approve the integration, Undasite uses a scoped Vercel token for the team you selected. Typical actions:

  • Create and update Vercel projects for your Undasite templates
  • Create production deployments
  • Set project environment variables needed for branding, OAuth, and Deriv WebSocket access
  • Attach and verify custom domains on those projects

Undasite does not need a Full Account personal token for this flow. You can disconnect at any time from Vercel (Integrations) or by replacing the connection in Undasite Settings.

Deploy after connecting

  1. Pick a template in App Builder and complete branding + Deriv OAuth.
  2. Deploy. The project is created on the Vercel team you approved.
  3. Attach a custom domain from the site dashboard when you are ready.

Troubleshooting

  • Connect is not set up — the Undasite instance is missing integration credentials. Contact support.
  • Authorization cancelled — start Connect again from Settings and approve the same team you want sites to land on.
  • Deploy still asks for Vercel — refresh Settings and confirm “Vercel connected” is shown, then retry the deploy.
  • Wrong team — reconnect and select the correct Vercel team during install.

Related