Deployments

How to publish with your own Vercel account

How to publish with your own Vercel account

Publishing to your own Vercel account is an older TeleportHQ option. It is available only for websites created before 5 May 2026. If your project qualifies, the Publish tab shows a Web / Vercel switch: choose Vercel, click Configure, paste a Vercel token, click Continue, then click Publish. All newer projects publish on TeleportHQ hosting.

Before you start

  • Check that you can use it. The Vercel switch appears only for projects created before 5 May 2026 that are not web apps. If you don't see it, publish on TeleportHQ hosting instead: see How to publish your site.
  • Plan. You need a Trial, Pro or Premium workspace. Without one, the Publish with Vercel section shows an Upgrade Now button instead of Configure.
  • A Vercel account and token. Create a token in your Vercel account at vercel.com/account/tokens.
  • Role. You need the Owner, Admin or Designer role.
  • TeleportHQ forms don't work on your own Vercel account. TeleportHQ forms only accept submissions from the project's TeleportHQ address (ending in .teleporthq.app or .teleporthq.site) and the custom domain connected to the project in TeleportHQ. On a site published to your own Vercel account, submissions are refused with "Domain not allowed" and nothing is saved. The Publish window doesn't warn you about this. If your site has forms, publish on TeleportHQ hosting. See Why is my form not working?.

Steps

  1. Open your project in the editor.
  2. At the top right, click Publish. The Publish window opens on the Publish tab.
  3. At the top, click Vercel in the Web / Vercel switch. The Publish with Vercel section opens.
  4. Click Configure.
  5. Paste your Vercel token in the field Add your token here.
  6. Click Continue. You see "Vercel account successfully connected. Publish to see the result."
  7. At the bottom of the window, click Publish.

Check that it worked

A message appears: "Your application is ready at: …". The Publish with Vercel section shows the address and the status Published. The deployment also appears in your own Vercel dashboard.

Change the token

Click Update token. The field shows stars in place of the saved token: replace them with the new token and click Continue. For security, TeleportHQ can't show a saved token again: "You can find your token in your Vercel account. For security reasons after the token is saved we cannot show it again."

Troubleshooting

The Vercel switch isn't there The project was created on or after 5 May 2026, or it's a web app. Publishing to your own Vercel account isn't available for it. If a website becomes a web app, the switch disappears. Use TeleportHQ hosting.

"Publishing to a custom Vercel account is no longer available for this project. Please publish via TeleportHQ hosting." Same cause as above. Switch to Web and publish on TeleportHQ hosting.

"Invalid characters: < , > , { , }" The token contains characters a Vercel token doesn't have. Copy the token again from Vercel.

"There was a problem saving the token, please retry or contact support" or "Could not save Vercel token: …" Try again. If it keeps failing, create a new token in Vercel.

"Subscribe to a paid plan for unlimited downloads, custom domains and public deployments." Your workspace has no active plan. Click Upgrade Now.

Good to know

  • No staging. Staging is only available on TeleportHQ hosting: projects published to your own Vercel account have a single environment, and the Deployments list only shows publishes on TeleportHQ hosting.
  • Custom domains are set up in Vercel. The TeleportHQ domain settings belong to the Web switch, so connect a domain to your Vercel-hosted site in your Vercel dashboard.
  • Older guides are out of date. The token used to be set in Project settings. It is now set in the Publish window. In Project settings, the Integrations group only holds a GitHub token.
  • Installable app. Once your token is saved, the Publish with Vercel section also has the installable app (PWA) option. See How to make your site installable as an app (PWA).
  • Other ways to host your site yourself: download your code or export it to GitHub (paid plans).
Share

Related Articles

How to publish your site

In TeleportHQ, click Publish at the top right of the editor, keep Production selected, and click Publish to Production; a progress bar beside the button shows each step, and after a few minutes your site is live on a free TeleportHQ address that you can share.

How to see and manage your deployments

In TeleportHQ, click Publish, then Deployments, to see every publish of your site with its address, date, status and Production or Staging label, and use each row's ⋮ menu to Redeploy, Promote to Production, read Build Logs or Delete it.

How to download your site as code (React, Next.js, Vue, HTML and more)

On a paid TeleportHQ plan (Pro or Premium), click Code at the top right of the editor, open the Download tab, pick a format such as HTML, React or Next and click Download ZIP to save your website's source code; a trial can't download code and web apps can't be downloaded.

How to export your project to GitHub

On a paid TeleportHQ plan, open Code → Download, pick a format, click Export to GitHub, paste a classic GitHub personal access token with the repo scope and click Export to GitHub again; TeleportHQ creates or updates a repository with your website's code.

How to connect your own domain

In TeleportHQ, publish your site to Production, then open Publish → Production → Custom domain → Configure, type your domain, choose the default address, and add the DNS records TeleportHQ shows at your domain provider.

Why is my form not working?

A TeleportHQ form usually stops collecting submissions because the site is hosted outside TeleportHQ ("Domain not allowed"), the changes weren't published, the form's storage is off or handled by a workflow, an action attribute overrides it, a field rule refuses the value, the form expired or hit a limit, or reCAPTCHA keys don't match the domain.