Pay with a Russian card directly
Russian card, invoice and closing documents for legal entities. No foreign card and no payment intermediaries taking a markup.
Fly.io alternative for Russia
Fly.io can't be paid for with a Russian card — a whole industry of payment intermediaries with markups exists just to solve that. Dada Cloud gives you the same path: connect a GitHub repo, push, and get a live HTTPS address with managed PostgreSQL next to it in minutes. Pay in rubles directly, no intermediaries, servers in Russia.
Why teams move from Fly.io to Dada Cloud
Deploy from GitHub
Connect a repo, push to the main branch — automatic build and deploy, framework detected for you.
Managed PostgreSQL next to it
Managed PostgreSQL is created next to the app and DATABASE_URL is injected into the service automatically.
Live HTTPS in minutes
Every app gets an HTTPS address right away; a custom domain is a couple of steps.
Data in Russia (152-FZ)
Apps and databases run on servers inside Russia — what the personal-data law requires.
No workarounds
Signup and payment from Russia are open directly — no VPN, intermediaries or foreign cards.
How to move an app off Fly.io
From fly.toml to a live address with no VPN — four steps.
01
Reuse the same image or repository
If the app was built from a Dockerfile, nothing changes: the platform builds from the same repository. A prebuilt image from a registry can also be deployed directly.
02
Move the secrets
fly secrets become the app's environment variables. Values are kept on the platform side and never reach the repository or the build logs.
03
Move the data off the volumes
A Fly.io volume is a disk attached to one machine. Here the data goes to managed PostgreSQL, to a persistent volume on the app, or to object storage when it is user files.
04
Switch the domain and check the region
The app is served from servers in Russia and opens without a VPN. Once you have verified it on the HTTPS address you were given, point DNS at your own domain and the certificate is issued automatically.
What becomes what
Fly.io concepts and their equivalents here.
| Fly.io | Dada Cloud | What to watch |
|---|---|---|
| Machine / app | App from a repository | Same Dockerfile, nothing to rewrite |
| fly.toml | Settings in the console or API | The config file is not read |
| fly secrets | Environment variables | They never reach the build logs |
| Volume | Persistent volume or storage | User files belong in object storage |
| Fly Postgres | Managed PostgreSQL | Backups and monitoring out of the box |
| Regions worldwide | Servers in Russia | Closer for a Russian audience, not a global CDN |
Where the model differs
Fly.io is built around machines all over the world; this is a different shape.
Anycast and scattered regions
Fly.io spreads machines across continents. Here the app runs on servers in Russia — closer and faster for a Russian audience, but it is not a replacement for global delivery from a dozen regions.
fly.toml is not read
App configuration lives in the console and the API rather than in a repository file. Variables, the start command and resources are set once when the app is created.
Scale to zero
Fly.io machines can sleep until the first request. Here the app runs continuously, and billing follows the plan's quotas rather than seconds of machine time.
Replacing Fly.io in Russia — FAQ
Does Fly.io work in Russia?
The service is reachable, but you can't pay for it with a Russian card — people use payment intermediaries with a markup. Data is stored abroad, which doesn't meet 152-FZ. Dada Cloud solves both: direct ruble payment and servers inside Russia.
How much does paying for Fly.io from Russia cost via intermediaries?
Intermediaries add a fee on top of the Fly.io bill plus an exchange markup. With Dada Cloud you pay with a Russian card directly, no intermediary fee: Free — 0 RUB, Startup — 990 RUB/mo, Business — 2900 RUB/mo.
How do I replace Fly.io with ruble billing?
Dada Cloud is a Russian platform with the same git push to prod flow: pay with a Russian card, invoice and closing documents, managed PostgreSQL next to the app, servers in Russia.
Is the deploy just as simple?
Yes. Connect a GitHub repo, push to the main branch — build and deploy happen automatically, no separate environment setup needed.
Does Fly.io work in Russia?
Formally the service is available, but at some Russian ISPs its addresses are intermittently unreachable without a VPN, and the plans cannot be paid with a Russian card. Those two points, not the platform’s capabilities, are what usually sends people looking for a replacement.
I need the same Dockerfile — will it work?
Yes. Builds run from the repository using your Dockerfile, with nothing to rewrite. If the image is already built and sitting in a registry, it can be deployed directly.
What do I do with Postgres on Fly.io?
Fly Postgres is an app on their machines, not a managed database. Here you take a dump and load it into managed PostgreSQL, which comes with scheduled backups, per-schema restore and monitoring out of the box.
What if the app needs several regions?
The platform is not a replacement for geographically distributed placement: apps run on servers in Russia. For an audience inside the country that is a latency win; for global static delivery you want a CDN in front of the app.
Give your code a public address
Create an account and deploy your first app. The Free plan costs $0.