Cloud is Simple
We have the proof right here
No form and no password. Sign in with GitHub or Google and the account exists, or let your agent run gg login and open the link it gives you.
You have a project folder. Click it.
Your agent drives it. You read it.
You say what you want in plain language. Your agent does the rest through one of three doors, and every door obeys the same rules. No manifest, no config file, nothing for you to learn.
The agent types, not you.
gg is the command line your agent uses. It is there for you as well, but nothing about gagarin ever requires you to open a terminal.
It already knows how.
One install teaches your coding agent gagarin: the rules, every command, every error and how to act on it. You never explain any of it.
Or no terminal at all.
For agents that call tools rather than type commands: the same API, the same credential, the same refusals.
Adding is always free. Nothing here can break what already runs.
Each answers approval_required and emails you a button. Every time. No flag grants it to an agent, and asking nicely doesn’t either.
You configure none of it. A working application in five minutes, and a rogue agent that couldn’t break it if it tried.
Three numbers. No tiers.
You pay for what runs, by the minute. There is no plan to choose, no seat to buy, no bandwidth meter, and no price that appears only after a call.
Any service, resource or job while it is up. Call it $10 a month for a small one. Stopped is $0.
Volumes and database storage. It only grows when you ask it to.
Not discounted — not metered. Domains and certificates are part of the platform, and so is the person who answers your email.
New accounts start with $5 on the house and no card is asked for until it runs low. We warn you before the balance reaches zero; if it does, your services stop and nothing is deleted — volumes, domains and data wait for you to put money back.
The full price list, including what a typical project costs →Who is behind it.
Ten-odd years of writing software, from small teams to Plata Bank, with a BSc in Computer Science from the University of Southampton. Everywhere I have worked, deployment turned out to be the worst part of the job, and always for the wrong reason. Not because the problem is deep, but because nobody wants to own the whole of it.
I got tired of waiting for someone else to fix it. That is why the cloud is small, why the list of things we will not build is public, and why I want to hear from everyone who puts something on it.
Reading the platform from your browser… api.gagarin.cloud/healthz/platform needs no credential and answers 200 only when all three of the above do.
The things people ask first.
So you’re like Railway?
On the surface, yes: containers, databases, domains, an agent that drives it. Most platforms cover that ground now, and most of them draw a dependency graph too. The difference is what the graph does. On every one whose documentation we have read, an edge is a variable reference, and on the private network every service can reach every other whether the line is drawn or not. Here the graph is the firewall, the credential store and the delete guard, because there is exactly one place the truth lives and everything else is derived from it.
What happens when I want to leave?
gg eject prints the Kubernetes manifests the platform itself reconciles from, out of the same renderer, so they cannot drift from what is running. Your images were always yours, in a registry you can pull from. The long version.
What can’t it do? Honestly.
Databases run as one pod each, with nightly dumps kept fourteen days: there is no replication and no point-in-time recovery yet, so a project that cannot lose a day should not keep its only copy here. Services do not autoscale. Regions: one, Paris. The list of things we have decided never to build is public too, with reasons, so that a year from now we cannot quietly change our minds. That list.
Can my agent really drive it?
That is the assumption the whole thing was built on. Every error carries a stable code and a fix_hint, so an agent branches on the code instead of reading tea leaves, and the agent skill ships inside the CLI so it can never disagree with it. Point yours at llms.txt and it will take it from there.
Does the safety get in my way?
It gets in the way of exactly five things, and shipping is not one of them. You can deploy, migrate, roll back, add a domain, resize, and read anything, all without asking anyone. Deleting a service, destroying a resource and removing a live address are what wait on a button in your inbox, pressed while signed in as you — each of them a thing you do a handful of times a year, and each of them a thing you cannot undo.
Who else is on it?
Not many people yet, and we are not going to invent logos for this page. Signup opened on 5 September 2026. What you can check instead is the platform itself: the panel above reads the same health endpoint that wakes us up, from your browser, right now, and everything shown on this page is a recording of a real project you can reproduce in ten minutes with $5 of free credit.
Is my data in the EU?
Managed Kubernetes at Scaleway in fr-par, Paris. A French company, French data centres, EU law. Nothing is replicated outside it.
Put one project on it this afternoon.
Sign in with GitHub or Google, and the account exists. No password, no list, no invitation, no card — and $5 of credit waiting, which is about three weeks of a small service.
Your agent gets in the same way. It runs gg login and hands you a link and a code; you sign in, check the code matches, and approve. Claude and ChatGPT connect to mcp.gagarin.cloud/mcp and ask you to sign in just the same. Nobody can sign you up by typing your address, because there is no address to type.