Pay with a Russian card
A Russian card, an invoice and closing documents. No foreign card, intermediaries or workarounds to pay for the subscription.
Vercel and Railway are convenient, but you can't pay for them with a Russian card or keep data inside Russia. Dada Cloud covers exactly that: connect a GitHub repo, push, and get a live HTTPS URL in minutes. No VPN, ruble payments, servers in Russia.
A Russian card is declined by Vercel, Mir is not supported at all, and virtual cards or intermediaries break exactly when the automatic charge lands. The full breakdown of every payment route still open, the risks of each, and what to do if the charge is failing right now lives on a separate page.
Paying for Vercel from Russia — every route reviewed→A Russian card, an invoice and closing documents. No foreign card, intermediaries or workarounds to pay for the subscription.
Both the panel and your deployed apps open from Russia directly — neither you nor your users need a VPN to reach them.
Apps and databases run on servers inside Russia — what the personal-data law requires and what foreign hosting structurally can't offer.
The same flow as Vercel: connect a repo, push to the main branch, and it rebuilds and deploys automatically. The framework is detected for you.
Right after the deploy the app is reachable over a valid TLS certificate. Your own domain connects in a couple of steps, the certificate is issued automatically.
Not just the frontend: managed PostgreSQL and S3 storage are created next to the app, and the connection string is injected into the service automatically.
Four steps to get the same push-and-it's-live flow. For a step-by-step migration of an existing Vercel project, see the dedicated /migrate-vercel guide.
In the console: Projects → Git → Connect, access via a GitHub App. Setting up git isn't required — you can deploy straight from a zip or tar.gz.
The platform reads the repo's package.json: finds the next dependency and enables the Next.js framework with port 3000 by default. A Dockerfile in the repo takes priority over autodetect.
Add the values from Vercel Project Settings → Environment Variables into the app's settings. A separate value can be set for the preview address without cloning the whole environment.
Right after deploy the site is reachable at a name-hash.dada-tuda.ru address over HTTPS. Your own domain is added under the Domains tab: the apex is verified with a TXT record, a subdomain via CNAME, with a Let's Encrypt certificate issued automatically.
Not config files — product concepts: what's named differently and what doesn't carry over at all.
| Vercel | Dada Cloud | Note |
|---|---|---|
| Vercel Deployment (project from GitHub) | App in Dada Cloud | Same principle: push to the main branch triggers auto-build and deploy. |
| Preview Deployments (a URL per PR) | PR environments + live-preview links (*.pv.dada-tuda.ru) | For a connected repo with auto-deploy on, a pull request labeled 'preview' gets its own environment with its own address; the live-preview link additionally gives protected access to any deployed environment. |
| Serverless Functions / Edge Functions | A regular container service | There's no separate on-demand function deploy type — all code, including API routes, runs inside one app service. |
| Vercel Postgres | Managed PostgreSQL next to the app | DATABASE_URL is injected into the service automatically, no separate database provider needed. |
| Vercel Blob | S3-compatible storage (Storage) | Created next to the app, accessed with keys from the panel. |
| Dollar usage-billing | Fixed ruble plans | Pay by Russian card, invoice, or contract with closing documents. |
Being upfront about the differences so there are no surprises after the move.
There's no on-demand function deploy type in Dada Cloud — an app always runs as a persistent container service. Function logic moves in as a regular API route inside the app itself.
There's no separate edge-execution layer spread across dozens of regions — app code runs in one place, like an ordinary self-hosted Next.js deployment.
next/image still works inside the app itself, but there's no separate managed edge-CDN image-resizing service the way Vercel provides one.
There's no managed Redis/KV store — the only managed database offered is PostgreSQL. Key-value storage needs its own container.
The site and deployed projects usually open, but you can't pay for a paid plan with a Russian card, and data is stored abroad — which doesn't meet 152-FZ requirements for Russian citizens' personal data. Dada Cloud solves both: ruble payments and servers in Russia.
Dada Cloud is a Russian platform with the same GitHub-to-production flow: pay with a Russian card, get an invoice and closing documents for legal entities, no foreign cards or intermediaries.
No. You connect the same GitHub repo, the platform detects the framework and builds the project. A push to the main branch rebuilds and deploys the app automatically.
Yes. Managed PostgreSQL is created inside the platform next to the app, and DATABASE_URL is injected into the service automatically — no separate external database provider needed.
Yes. Apps and databases run on servers in Russia, meeting the 152-FZ and 242-FZ requirements to store Russian citizens' personal data within the country.
Officially, not with a Russian card — Vercel accepts Visa/Mastercard from foreign banks and PayPal. Some people use virtual cards from foreign banks or intermediary services that take rubles and pay Vercel on their behalf. There are risks: a markup on top of the bill, the card or intermediary account can stop working without notice, and closing documents for a legal entity are usually not available through an intermediary. If staying on Vercel specifically isn't the point and a working GitHub-to-production deploy is, a Russian alternative like Dada Cloud removes the payment question entirely: a Russian card, directly, no intermediaries.
Create an account and deploy your first app. The Free plan costs $0.