What can replace Netlify with ruble payments?

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.

Can I deploy Next.js or a static site?

Yes. The platform detects the framework (Next.js, static, SPA) and builds it. A push to the main branch rebuilds and deploys automatically.

Do I need a VPN to reach the dashboard?

No. The dashboard and sites open from Russia directly, no VPN required.

Why doesn't a Russian card work for paying Netlify?

Netlify bills through a foreign payment processor, and it doesn't accept cards from Russian banks — after Russian banks were cut off from Visa and Mastercard, these payments fail on the payment system's side, regardless of card limit or how the details were entered.

Can I pay Netlify with a virtual card or through an intermediary?

Some people use virtual cards from foreign banks or intermediary services that take rubles and pay Netlify on their behalf. There are risks: a markup on top of the bill (usually significant), the card or intermediary account can stop working without notice, and closing documents for a legal entity are usually not available through an intermediary.

How is Dada Cloud different for people looking to replace Netlify because of payments?

Pay with a Russian ruble card directly, no intermediaries or markups. For legal entities there's an invoice and closing documents. The deploy flow is similar to Netlify: connect a GitHub repo, push to the main branch, and the app is live.

Netlify alternative for Russia

Netlify is handy for deploying sites from GitHub, but in Russia its dashboard and some sites won't open without a VPN, and you can't pay with a Russian card. Dada Cloud gives you the same path: connect a repo, push, and get a live HTTPS URL in minutes. Pay in rubles, servers in Russia, opens without a VPN.

Create account Learn more

Why teams move from Netlify to Dada Cloud

Pay with a Russian card

Russian card, invoice and closing documents for legal entities. No foreign card or intermediaries.

Deploy from GitHub, like Netlify

Connect a repo, push to the main branch — automatic rebuild and deploy. The framework (Next.js, static, SPA) is detected for you.

Opens without a VPN

Unlike Netlify, the dashboard and deployed sites are reachable from Russia directly, with no workarounds.

HTTPS domain out of the box

Right after the deploy the site is reachable over a valid TLS certificate. Your own domain connects in a couple of steps.

Managed PostgreSQL alongside

Netlify has no built-in database — you need an external provider. Here managed PostgreSQL is created next to the app and DATABASE_URL is injected automatically.

Data in Russia (152-FZ)

Sites and databases run on servers inside Russia — what the personal-data law requires.

How to move from Netlify to Dada Cloud

No need to rewrite the site — you're moving build and deploy configuration, six steps.

Connect a repo or upload an archive

In the console: Projects → Git → Connect, the same GitHub repo you had on Netlify, access via a GitHub App. Don't want to set up git — deploy straight from a zip or tar.gz instead.

netlify.toml isn't read here — check the autodetect

There's no direct netlify.toml equivalent. Dada detects the framework from manifests in the repo (package.json, requirements.txt, Dockerfile) — static sites, React/Vite SPAs, Next.js, Nuxt, SvelteKit, Python and others — and fills in the build command for you. Need a nonstandard build step — deploy from your own Dockerfile instead, it takes priority.

Check the build command and port

The autodetect result is shown on the app-creation screen before the first deploy. Framework, build command and start command can be edited by hand there if detection is off.

Move over your environment variables

Copy values from Netlify → Site configuration → Environment variables into the app's settings → environment variables. You can set a separate value for the preview address without cloning the whole environment.

Push to the main branch

A push to main triggers an automatic rebuild and deploy, same as a commit-triggered deploy on Netlify. The build log is visible in the console, and errors are immediately visible.

Connect a domain

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 (dada-domain-verify=...), a subdomain via CNAME, with a Let's Encrypt certificate issued automatically after verification.

What Netlify had and where it moved to in Dada Cloud

Point by point — what carries over directly and what's named differently.

Netlify	Dada Cloud	Note
Netlify Site (from GitHub)	App in Dada Cloud	Same principle: one repo equals one app with auto-build on push.
netlify.toml	Framework autodetect or a Dockerfile	There's no separate config file: build settings are detected automatically or set by hand on the app, with a Dockerfile for the nonstandard case.
Deploy Previews (per PR)	Live-preview link for a deploy (*.pv.dada-tuda.ru)	Not the same thing: it isn't an automatic preview URL per PR, but an HMAC-protected link for viewing an already-deployed environment, including embedding it in the console.
Netlify Environment variables	App environment variables + preview override	A separate value for the preview address is set per variable, not as a full environment clone.
Netlify DNS / custom domain + TLS	Domains + managed TLS	The apex is verified with a TXT record, a subdomain via CNAME, with a Let's Encrypt certificate issued automatically.
Dollar usage-billing	Fixed ruble plans	Pay by Russian card, invoice, or contract with closing documents.

What doesn't move over directly

Being upfront about the differences so there are no surprises after the move.

Netlify Functions and Edge Functions

There's no serverless-function deploy type in Dada Cloud — an app always runs as a container service, not as a function invoked on demand. Function logic needs to move into the service itself (an API route inside the app) or onto a separate App Server.

The _redirects file and Netlify redirect rules

There's no _redirects file convention. Redirects and rewrite rules are configured at the app level, in the server or framework code, not through a platform config file.

Netlify Forms

There's no backend-less HTML form handling — you need to implement form submission yourself as a handler inside the app.

Netlify Identity

There's no ready-made auth-as-a-service for site visitors — user authentication needs to be built into the app itself or handled by an external service.

Split Testing (branch-based A/B)

There's no built-in split testing between deploy branches.

Replacing Netlify in Russia — FAQ

Often not: the dashboard and some deployed sites won't open without a VPN, and you can't pay with a Russian card. Data is stored abroad — which doesn't meet 152-FZ. Dada Cloud solves it: access without a VPN, ruble payments and servers in Russia.

Get your backend live from GitHub today

Connecting a repo takes a minute. You only pay for what you actually use.

Create account