Smoke tests fail on every release
The container binds to 127.0.0.1 or to the wrong port, so fly-proxy cannot reach it, the smoke check times out, and the deploy rolls back without a useful clue in the output.
App bound to 0.0.0.0 and serving
Running on Fly.io?
A lot of the Fly apps we see came off Heroku in a rush, then sat on default machine sizes with half the regions left running after someone tested latency. We walk the fly.toml, the machine states and the volume layout until the real cause is on the screen, and we trim the bill on the way out.
What it is
Fly.io runs user code as Firecracker micro-VMs, which it calls Machines, on a network of edge regions. You push a Docker image or a Dockerfile, and the platform boots instances close to your users with public Anycast addresses and private WireGuard networking out of the box.
The company is based in Chicago and shipped its first public release in 2020, growing quickly as teams leaving Heroku looked for something with a similar developer story. It handles Postgres clusters, Redis via Upstash, persistent volumes and multi-region deploys, and the whole workflow is driven by a single CLI called flyctl.
The honest version
No technology is all upside. This is where Fly.io earns its place and where it tends to cause trouble.
Sound familiar?
The Fly.io problems that bring people to us, and what you have once each one is fixed.
The container binds to 127.0.0.1 or to the wrong port, so fly-proxy cannot reach it, the smoke check times out, and the deploy rolls back without a useful clue in the output.
App bound to 0.0.0.0 and serving
A database migration that needs more memory than the release VM has, or an environment variable that lives in the app and not in the release step, leaving the deploy stuck on step one.
Migrations run, deploy continues
A Rails or Node app sized for a Heroku performance dyno and running on a shared-cpu-1x on Fly, hitting the RAM ceiling as traffic warms up.
Right-sized Machines, memory watched
Standby regions nobody is actually using, a Postgres cluster larger than it needs to be, and a worker set to always-on when it could be scale-to-zero.
Costs reviewed region by region
The new Machine never passes its health check, the old one is already drained, and traffic is served by whichever instance happens to still be up.
Health checks honest, deploys green
A machine recreated in a new region without the volume attached, or a scale operation that spread Machines across regions where the disk does not exist.
Storage and compute co-located
A Dockerfile removed from the repository, a buildpack section that was never filled in, or a remote builder that failed to start and left nothing behind.
Build pipeline reproducible
A Fly org still registered to a developer who has moved on, with secrets set from a laptop that is no longer in the building and a fly.toml nobody has read.
Ownership moved, config written down
What we do
Ring us for one stuck deploy, or hand us the org and let us tidy the lot.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
We stand the app up on Fly in parallel, replicate the Postgres database with logical replication or a pg_dump restore window, and cut traffic over at the DNS layer during a quiet hour. Heroku stays running until the new side has been proven for at least a day, and workers are moved last so queues do not split across two platforms.
The container is almost certainly bound to localhost or to a port that does not match internal_port in fly.toml. Bind to 0.0.0.0 on the port Fly expects, confirm the health check path returns a 200, and the smoke test will pass. We see this one on roughly half the Heroku migrations we handle.
Not in the way RDS is. Fly Postgres is a template that installs standard Postgres with repmgr on Machines in your organisation. The daily operations, backups, failover testing and version upgrades still need somebody competent paying attention, and we do that for clients who prefer not to.
First confirm the actual resident memory of the process under load, since the app is often sized for a Heroku performance tier with four times as much RAM. Either move to a Machine with more memory, reduce worker concurrency, or address the underlying leak. We take a profile before changing sizes so the fix is pointed at the cause.
Render is the gentlest replacement if Heroku's feel is what you liked, Railway is the easiest for small side projects, and Fly wins when latency matters and you want code running close to users in several regions. We will give you a straight recommendation for your workload before any work is quoted.
The estimate is on us. Tell us which apps are on Fly and the symptoms you are seeing, and we come back with a scope and a number before any changes are pushed.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: