the blog

Writing

What we built, what it cost, and what broke on the way. Everything here is something that actually happened on this platform — there is no roadmap post coming. RSS.

The worst moment of every two hoursEvery project has a Metrics tab now. CPU, memory, disk, network and HTTP for each service, thirty days back. Here is how it is built, which numbers we decided to show you, and the read that worked everywhere except production.Axon is open sourceAxon is the memory every Gagarin project carries. Your coding agent writes down decisions and gotchas once, and the next session reads them back in 1,500 tokens. The code is on GitHub now, under MIT.Leaving Railway in an afternoonA web service, a worker, a Postgres and a cron job, moved from Railway to Gagarin between lunch and dinner. Every command, the one line that changed, and the two habits you drop on the way.Pure cinemaThe console has a LIVE switch now. Flip it, tell your agent to deploy, and watch the project draw itself. Some features deliver a capability. This one is just a pleasure to look at.Gagarin vs RailwayRailway has four regions, replicas and billing on actual CPU use. Gagarin has one region, free traffic, and deletes that wait for a person. The figures, worked out.Gagarin vs RenderRender has five regions, a free tier, preview environments and cheaper compute at the same size. Gagarin has free traffic, cheaper disk, and deletes that wait for a person.Assembly requiredClouds sell parts. Turning twenty of them into somewhere you can deploy is a second job nobody pays for, and what you build is a worse PaaS than the one you could have rented.Bloated clouds, anyone?Clouds had to serve everyone, so they got bloated and gave up on the developer experience that made them worth having. A rant, and what I did about it.Two strangers' repos, deployed by agents, unaidedWe handed two agents two repositories neither had ever seen and let them deploy, with nobody to ask. Both got there. Then we counted what broke.A database, two services and an address, in five commandsA walk through an ordinary deploy — the Dockerfile, the five commands, what the engine says back, and the one command it refuses.