I just saw this was on fly and thought the same thing lol. But I also thought to myself “this is actually a good use for fly, nice simple app to see if there’s traction before moving to something reliable.”

Do you have any specific references or instances that indicate fly.io as being unreliable?

I had something deployed on fly for a few months and was regularly running into random restarts and connection issues. I ended up switching to DO’s app platform and haven’t seen any of that since.

Very anecdotal so take this lightly but the past year or so of Fly.io threads have had a lot of comments expressing negative experiences with reliability. I have no experience myself so I can't comment, but if you search for a fairly recent thread you'll probably find some people's experiences.

I was about to start building a new application and I really wanted to give Fly a shot, but the CLI literally wouldn’t connect to their builder API. The status page was all green, but clearly things weren’t working.

I moved to Render and I’ve had a much better experience.

Here’s a good thread where this is discussed in detail, plus my own anecdotal experience:

https://news.ycombinator.com/item?id=36808296

FlyIO deleted my database and I lost all data.

Fly told me in 7-days they would automatically update my redis database. My plan was to manually update it that weekend. 3 days later, I get an alert that they migrated the db early. b/c I didn't have storage enabled, all data was gone.

Support ticket:

https://community.fly.io/t/forced-migration-to-v2-with-decei...

Fly.io definitely has an innaproprately casual attitude, and it's a big deal they migrated you early.

However, they do point out that literally any reboot would have wiped your data and that that could have happened at any time previously. I think there's some truth to the suggestion I've seen on HN that the users running into the worst fly.io issues are the ones aiming to spend single digit amounts per month and not paying for enough machines and disk space to have reliability be possible

Like I said in the forum history, I should have paid for persistent storage, but this data lose could have been avoided during a planned reboot.

FlyIO knew that there was no storage attached to the redis instance and there would be data loss, but they still chose to reboot it ahead of schedule.

Does fly do runaway billing?

Bandwidth would be the concern, I think. They won't auto-scale machines up/down for you.

Fly bandwidth pricing is pretty competitive; if bandwidth is an issue your bill will be cheaper on Fly than most other providers.

... And it is hugged to death now.

Curious as a non dev, could this equally have been on vercel or netlify or does this type of app lend itself to fly?