Do I need a card to pay?

No, if the free plan (2 apps, 1 database, 1 domain) covers you. Paid plans are billed with a Russian card, an invoice, or a contract with closing documents for legal entities — no foreign card needed.

Where do I move the environment variables from Vercel?

Into app settings -> "Environment variables" in Dada Cloud, copying values from Vercel Project Settings by hand — there's no automatic import from Vercel.

Is a custom domain with HTTPS supported?

Yes. Add the domain in the Domains tab (apex via a TXT record, subdomain via CNAME); the Let's Encrypt certificate is issued automatically once ownership is verified.

Moving from Vercel to Dada Cloud: a step-by-step guide

If Vercel no longer takes a Russian card and you've decided to move the project — here are the concrete steps for an existing repo: what carries over automatically, what you need to check by hand, and where your vercel.json settings ended up in Dada Cloud.

Create account Learn more

5 steps to migrate

No code rewrite needed — it's the deploy configuration that moves.

Connect the repo

In the console: Projects -> Git -> Connect. The same GitHub repo you had on Vercel, access via the GitHub App, no keys to paste by hand.

Check the framework auto-detect

Dada detects the framework (Next.js, Vite, static and others) from the repo and fills in the build command, start command and output directory. If detection is wrong or the project has its own Dockerfile, the same screen lets you override the framework, build command, start command and output dir manually.

Move the environment variables

Copy values from Vercel Project Settings -> Environment Variables into Dada: app settings -> environment variables. Build-time, runtime and secret scopes are supported; there's no automatic import from Vercel, so this is a one-time manual copy.

Connect the domain

Add the domain in the Domains tab: an apex domain is verified with a TXT record, a subdomain with a CNAME to the app's address. Ownership verification is currently manual (a "verify" button); once verified, the Let's Encrypt certificate is issued automatically.

Push and check the build

A push to the main branch triggers an automatic rebuild and deploy. The build log is visible in the console, so a failure is easy to diagnose and retry without opening a new PR.

What was in Vercel, and where it moved in Dada Cloud

An honest map of what carries over 1:1, and what doesn't.

Vercel	Dada Cloud	Note
vercel.json (build, rewrites, headers)	Framework override + build/start command in Git Import	Build settings carry over 1:1. There's no separate config file for rewrites and custom headers in Dada Cloud — those rules need to move into the framework's own code (e.g. next.config.js for Next.js).
Environment Variables	App settings -> Environment variables	Build/runtime/secret scopes are preserved; values are copied over by hand.
Custom Domain + automatic TLS	Domains -> add a domain	The Let's Encrypt certificate is issued automatically once domain ownership is verified.
Vercel Postgres / an external database	Managed PostgreSQL next to the app	DATABASE_URL is injected into the service automatically — no separate external database provider needed.

Before you migrate

Rewrites and headers from vercel.json

There's no ready-made import for the config file — redirect and header rules move into the framework's own code (e.g. next.config.js).

No preview deploy per pull request

Unlike Vercel Preview Deployments, an app has one production address that updates on a push to the main branch.

Migrating from Vercel — FAQ

In most cases yes — Dada detects Next.js automatically and uses the standard build and start commands. If the project used rewrites/headers in vercel.json, those rules need to move into code (e.g. next.config.js) — there's no ready-made 1:1 import for that config.

Migrate the project in one push

Connect the same GitHub repo and get a working address in minutes — ruble payments, servers in Russia.

Start the migration