Hobby Plan - Performance

The Hobby Plan description on https://fly.io/plans says:

Great for side projects, test environments, or projects with a small team. Run basic full-stack apps close to your users.

I am planning to deploy my app initially with the hobby plan. I will be running an API, and there will be mobile, web and desktop apps.

My app’s functionality is mostly CRUD, and usage will be intermittent, with a few hundred users in the first months.

The API will be an ASP.NET Core Web API on .NET 8, and there will be a Postgres database.

My guess is that the hobby plan should suffice, but I’d like some numbers on API call volumes and general performance numbers that the hobby plan can support. Is there any published data about throughput, latency etc. for each plan? As I said, my site will be low traffic with intermittent usage in the initial months. There might be an initial spike as I publicize it, but after that, I expect traffic to be intermittent. I just want to get an idea if it’s feasible to go live on a hobby plan.



I don’t think the Hobby Plan differs from the next plan up in terms of how much traffic is supported, latency, throughput etc.

From Plan Pricing · Fly it looks like moving to the next plan up simply adds more features, like email support (on the Hobby Plan you only have this forum to ask questions) and more regions. Despite its name, it can be used for production if you don’t need those.

Rather than the plan, I would think your choice and number of machine (cpu/ram) would be the factor in determining how many requests your app can handle. I don’t know anything about .NET and its resource requirements so couldn’t advise on that.


Thank you, @greg. This helps.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.