Supabase Postgres available to everyone in public alpha

Supabase Postgres on is now in public alpha! This release is not intended for production workloads. We’ve made it available so all customers can give us feedback to help improve the product.

Anyone with a Fly account can provision a database in any region with:

fly ext supabase create

Here’s the annoucement from Supabase and our docs for getting started.

Here’s a perk: You can now test Supabase Branching, an opt-in feature which creates an ephemeral test environment for your git branches. These instances automatically pause when you aren’t using them to save on costs.

Learn more about how to use auto start-stop in your application: Automatically stop and start Machines · Fly Docs

Please give us feedback! We look forward to hearing from you. Stay tuned as we work towards a public beta release.


Just a point of feedback for both Fly and the Supabase team. Having a product in beta has an implication around the maturity of support and it isn’t quite there yet.

Since midnight yesterday (so now about 30 hours), our staging and production Supabase instance became unresponsive. The self-recovery tools aren’t working (staging has been stuck in “Restoring” for ~20 hours), there is no way to access either instance through the API, CLI, or the Supabase console. Emailing support got us no answer (we upgraded to the paid plan) until last night, and the response was “Wait until business hours”.

I think Supabase is a pretty great product, but for folks looking for some points about reliability, customer support and access, as well as maturity of tooling (even something as simple as being able to download backups so we could spin-up new instances with the most recent data) it is on the early side – especially the maturity around offering support, both self-service and access to folks who have tools to fix things on weekends.

1 Like

Supabase offers one free, resource-limited database per user. After that, all databases are billed on pay-as-you-go basis under the Supabase Pro plan. Check the official Supabase Pricing page for details.

Unfortunately I don’t really understand fully how pricing works. So I’d pay $25/month for the Pro plan, but since Fly machines and Supabase instances have different hardware and configurations, how exactly does the pay-as-you-go pricing work? It would be great to have an example in the Fly Supabase Postgres docs that explains it.

Congrats on the public launch :tada:

Any word on timeline for Auth availability?

We had to temporarily pause migration and swap back to non-Fly Supabase due to this limitation (didn’t realize it until we had started playing with our staging environment).

No timeline, though it’s being discussed. Note that this release is not intended for production workloads. Keep using Supabase’s platform until we’re out of alpha and beta.

Thanks @jay - we’ve taken this feedback to heart. To align with Supabase, we’ve changed the name of this release to ‘alpha’ and will update our documentation to clarify expectations for this release.

Note that while you will see estimated charges on your bill, we won’t actually bill you for this service yet. Charges are visible to elicit feedback about the billing process.

You can find a more detailed explanation here: How billing works | Supabase Docs

Further down the page you can find the costs for compute: How billing works | Supabase Docs

To clarify - you’ll be paying Supbase’s prices. Your database doesn’t run inside your organization, so you aren’t billed separately by

Why is the signup form for the alpha still live if the alpha is now generally available? I could have started playing with it days ago! Days!

Hi there

Is the 500GB Fly limit gone?

Fly Postgres, managed by Supabase
Database changes are continuously streamed to S3

How often does this happen?

Supabase’s current price for bandwidth is $0.09 per GB.

This one is a bit high, and made more sense for AWS.

This would mean that Supabase’s bandwidth pricing would be 4.5 times higher than in Europe.

Compute Add-ons | Supabase Docs

I’m guessing the IOPS numbers are gonna be different for ?
It made sense for AWS due to EBS, but provides much faster storage, and I’m hoping we are not going to get throttled.

“Continuously” means that changes are streamed using write-ahead logging to object storage.

We’ll take this under consideration, though final pricing is determined by Supabase.

These numbers haven’t been updated for Thanks for pointing it out. We don’t guarantee specific IOPS yet, but as this project develops, we’ll post more details on all these topics.