Pay with a Russian card
Russian card, invoice and closing documents for legal entities. No foreign card or intermediaries.
DigitalOcean restricted signups and payments for Russia, and you can't pay with a Russian card. Dada Cloud gives you the same building blocks: your own servers (App Servers), app deploys from GitHub and managed PostgreSQL. Pay in rubles, documents for legal entities, servers in Russia.
Russian card, invoice and closing documents for legal entities. No foreign card or intermediaries.
A Droplet equivalent: spin up a VM for your workloads — MySQL, Redis, any containers and services.
An App Platform equivalent: connect a repo, push to the main branch — automatic build and deploy, framework detected for you.
A DO Managed Databases equivalent: managed PostgreSQL is created next to the app and DATABASE_URL is injected automatically.
Unlike DigitalOcean, access and payment from Russia are open — no workarounds or intermediaries.
Apps, servers and databases run inside Russia — what the personal-data law requires.
The path is clear for App Platform and for a plain droplet alike.
An App Platform app moves over as a normal app from a repository. A droplet running Docker may not need moving at all: connect it as your own server and run it from the console.
Connect the GitHub repository, set the start command and the environment variables. An existing docker-compose.yml works too — there is nothing to rewrite for the platform.
A PostgreSQL dump loads into a managed instance on servers in Russia. The app receives DATABASE_URL once the database is attached, with no config edits.
Spaces speaks the S3 protocol, and so does the platform's object storage, so the transfer runs through rclone or aws-cli directly between endpoints without a round trip to your machine.
DigitalOcean resources and their equivalents here.
| DigitalOcean | Dada Cloud | What to watch |
|---|---|---|
| App Platform | App from a repository | Push to a branch rebuilds and deploys |
| Droplet | App Server | The machine can stay put and just be connected |
| Managed Database | Managed PostgreSQL | pg_dump across; servers in Russia |
| Spaces | S3 object storage | rclone moves it endpoint to endpoint |
| Load Balancer | Built into the app | No separate resource to create |
| DOKS | Apps or compose on a server | No direct manifest import |
Three places where a one-to-one move is not possible.
DigitalOcean's networking primitives do not transfer: load balancing and HTTPS are on by default for an app here, so there is no separate resource to create.
If the workload lives in a cluster with its own manifests, there is no direct import. Services move over one at a time as apps, or run on your own server through compose.
A whole VM image does not move. What moves is what is inside it — containers, data and environment variables — or the machine is connected as an App Server and stays at its current provider.
DigitalOcean restricted signups and payments for Russian users, and you can't pay with a Russian card. Data is stored abroad — which doesn't meet 152-FZ. Dada Cloud solves it: access and payment from Russia, servers inside the country.
Yes. App Servers are your virtual servers where you can run MySQL, Redis, containers and any services, just like a Droplet.
Yes. Apps deploy straight from GitHub: a push to the main branch triggers an automatic rebuild and deploy, framework detected for you.
Yes. Managed PostgreSQL is created next to the app and DATABASE_URL is injected automatically — no separate provider needed.
Pay with a Russian card; for legal entities there's an invoice and closing documents. No foreign cards or intermediaries.
No, and most people do not. The machine is connected as an App Server: it stays at DigitalOcean or any other provider, while deploys, logs and metrics run from the console. What usually moves is the data and the apps, not the VM.
Yes, object storage with an S3-compatible API. The transfer runs through rclone or aws-cli directly between endpoints: the protocol is identical, so it is one command plus transfer time.
The model is different: not per-hour billing for a droplet size, but a plan with quotas on apps, databases, domains and members. For a typical project on a couple of services that is more predictable — the monthly invoice does not depend on idle hours.
Yes, that is the main agency case. Each client machine is connected separately, access is granted per project rather than as a root key to the whole fleet, and every server shows up in one console.
Create an account and deploy your first app. The Free plan costs $0.