tuqo

Migrate a static site from Vercel or Netlify

Vercel and Netlify are great platforms. You may still want to move: to pay in rubles, to host the site and its data in Russia, or because your audience there has trouble reaching foreign hosting. If you have a static site or a frontend build (Vite, React, Vue, Astro, SvelteKit static, Next.js export), moving to Tuqo takes a few minutes.

Use the same repository you deploy to Vercel or Netlify:

  1. Open the site in the Tuqo panel → the Git CD tab.
  2. Connect a Git service (GitHub or GitFlic with your account; GitVerse, GitLab or Gitea with a token).
  3. Pick the repository and branch → Link.

From then on every git push publishes the site automatically, just like on Vercel or Netlify, but without their config files. The build runs on Node 20 (npm ci or npm install, depending on whether there is a lock file, then npm run build), and the output is taken from dist, build, out, _site, public or another common output folder. More in auto-deploy from Git.

Option 2. Upload a finished build

If you would rather not connect Git, build locally and upload the dist folder: drag it into the panel, publish it with the CLI, or ask an AI agent over MCP to do it.

npm run build
TUQO_API_KEY=tqk_xxx_yyy npx @tuqo/cli deploy ./dist --site <site_id> --wait

Important: static only

Tuqo serves static files. Server-side parts do not move over:

  • Serverless and Edge Functions (Vercel or Netlify Functions) do not run. Move that logic to third-party APIs or client-side calls. For contact forms there is a built-in option: Tuqo forms accept submissions from static pages with no backend.
  • Next.js: use the static export (output: 'export'); SSR and ISR are not supported.
  • Redirects and headers from vercel.json or netlify.toml (and Netlify’s _redirects and _headers files) are not applied. Tuqo resolves clean URLs (/about → about.html) and folder indexes on its own. For an unknown path it serves your 404.html if the site has one, and otherwise falls back to index.html, so SPA routes work out of the box.

Domain and SSL

Attach your custom domain: custom domains are on paid plans, or on Free with the Custom domain add-on (see pricing). The SSL certificate is free and issued automatically. Then point your DNS records from Vercel or Netlify to Tuqo.

What you get

  • Billing in rubles (Russian bank cards only) and infrastructure in Russia.
  • Auto-deploy from Git on push, free SSL, version rollback on paid plans.
  • Control from an AI agent over MCP, and forms that collect submissions without a backend.

Git CD → · Pricing → · Comparisons (in Russian): vs Vercel, vs Netlify

Related guides

← All guides