Fly.io

“If they're not going to lawyer up when it comes to the 4th amendment, I will never use this service.”

“I've been watching Kurt's AI-pillness advancing over time, but I didn't expect it to metastasize so quickly.”

“Fly's support was absolutely top-notch, up to and including Kurt personally working with me to help debug our deployments”

“They are almost at Big Three cloud/Vercel level of cost with none of the stability.”

“today I operate a few production workloads on it that are very stable and reliable”

“the reality of using them was that I was dealing with major outages almost monthly”

“Fly's support was absolutely top-notch, up to and including Kurt personally working with me to help debug our deployments.”

“the way certain people at that company speak to others (e.g. that post) is why they will never count me as a customer”

“I clicked a button in my PaaS and I have an oncall responder and incident manager ready to go.”

“the CEO writing an article like that makes me think fly.io is a deeply unserious company”

“they lost a lot of aura among folks i know with the 'ai skeptics are nuts' article”

“the pricing is fixed - you pay $1.94/month (less if you suspend your machine) for the smallest instance”

“missing the pay-as-you-go pricing & rapid scaling model that makes Fly worth using”

“Fly, Render, and even Heroku still are all better choices then working with Railway I think”

“The initial setup and fly.io setup was worth me saving ~50 Euro/year”

“Fly and Render are what heroku would be if they didn't stop innovating.”

“I love fly, but it adds up when I have a bunch of small things that I want isolated”

“Moving the same workload to Hetzner or even a single Fly.io region dropped it by >80% without touching the app.”

“Scaling to zero with database persistence using litestream has cut my bill down to $0.1 per month”

“platforms like Railway and Fly have made deploys nearly painless”

“It took me thirty seconds to find the fly.io guidance to use BullMQ with Node+Redis.”

“Using either the fly command or their api, you can kick off a one-off machine that runs an arbitrary script on boot and dies when that script ends.”

“The whole selling point of fly is lightweight and fast VMs that can be "off" when not needed and start on-request.”

“The site loaded instantaneously on the first try, so fast I thought it was local.”

“They took all of the great things about Heroku but also dramatically improved and added new capabilities”

“the CEO responded to me personally in less than 10 minutes”

“great platform occasionally goes down and requires a bit of attention but the support forum is great”

“Cloudflare, Fly.io litestream offerings and Turso are pretty reasonably priced, given the global coverage.”

“Fly's replay mechanism is clever, but that initial bounce still adds latency.”

“found it was a lot more polished, and now have multiple production apps running there”

“The way they force at least one "fuck" into all of their promo is just so cool.”

“API downtime is a semi-frequent occurrence, as are transient API errors and slowness.”

“fly.io is doing really good work. I've super enjoyed building our product on their platform.”

“fly.io doesn’t support outbound ipv6 connections but defaults to a dns server that returns them”

“making it dead simple to get a VM at a domain or IP in a few seconds is good and useful”

“There's no reason to throw money at those providers when there are many options a dozen times cheaper.”

“they would go down all the time or have unexpected CI bugs/changes”

“outsourcing that to Cloudflare or Fastly or Fly.io or whomever is a reasonable strategy”

“For actual server paas that can run docker containers, render.com and fly.io are what heroku could have evolved to.”

“having a disk attached to a VM instance where you can write data is never a default and usually complicated or expensive to setup”