11 engineers on Hacker News describe using Fly.io first-hand: 1 endorse it, 5 regret it, 3 are mixed.
“Fly, railway, render. Avoid. All have weird show stopper bugs for any reasonable scale”
regret · production · cmdtab · 2026-02-10 · source ↗ · wrong label?“our Fly.io release has failed due to size and memory usage during deployment, thankfully retries have worked”
mixed · production · doomspork · 2025-08-01 · source ↗ · wrong label?“About 6 months ago we migrated our most critical stuff from Fly to CF and boy every time Fly has issues I'm so glad we did.”
regret · production · pier25 · 2024-11-26 · source ↗ · wrong label?“I've used Fly in prod for 4 years and spilled much ink on this topic on their forums already.”
mixed · production · 4 yr · ignoramous · 2024-11-26 · source ↗ · wrong label?“we run the models on our own GPU clusters hosted in Fly.io... (which Fly doesn't support currently)”
mixed · production · reissbaker · 2024-07-24 · source ↗ · wrong label?“Our team ended up setting up a new project in fly to spin up an instance to keep us going”
regret · production · burnerbob · 2023-07-20 · source ↗ · wrong label?“I wish I could say I love fly.io, but it really is not ready yet for production. A few months back we migrated a non essential production app”
regret · production · sebslomski · 2023-02-27 · source ↗ · wrong label?“I actually gave fly.io a whirl over the weekend. was not fun.”
regret · personal · azlyrics · 2022-09-22 · source ↗ · wrong label?“Has been working flawlessly since then. Kudos to the team! I strongly recommend them!”
endorse · production · pcx · 2018-04-05 · source ↗ · wrong label?“I wrote an article about migrating to Fly.io and using Tailscale to continue connecting privately in production”
neutral · production · bsnnkv · 2022-12-16 · source ↗ · wrong label?“We run a lot of peoples' apps and have limited ability to have them add libraries or write new code.”
neutral · production · mrkurt · 2022-08-21 · source ↗ · wrong label?