If you don’t care for the details, here is the pricing [3]. The linked blog post goes into depth around our decision-making process.
The key takeaway is that we will stick with (what we feel is) a generous free tier. This was critical for many of our users who are still in the "build" phase of their project/business.
Another key takeaway is predictability. We've talked to too many devs who have been caught out by Firebase's usage billing. Usually this is due to rogue API requests, which have a habit of spiking without any good debugging tools. To circumvent this, our usage pricing is centered around more "predictable" mechanisms (like storage), avoiding usage-billing on items like API requests. Even on our free tier you're able to make millions of requests per day (we have developers doing this already!). In the future we will introduce "usage caps" on our top tier, which will allow you to specify maximum spends. Finally, we're starting with soft-tiers, so nobody will be "unexpectedly" upgraded.
We're a startup ourselves, so we want to build a sustainable business. Even though we are offering a free tier, we're confident in our ability to support it long-term with the enterprise features we are building (SSO, multi-cloud). If you aren't confident in our business model though, we're open source. You can host it yourself[4]. Even better, everything we build is centered around Postgres, so you can pretty much `pgdump` your database and take it to your favourite Postgres platform.
We'd love to hear your feedback for the pricing. Also look out for a few more things we're releasing this week: Storage, a CLI, and some other Postgres-related items.
[1] Launch week: https://supabase.io/new/blog/2021/03/25/launch-week
[2] Open source products: https://supabase.io/docs#how-it-works
[3] Pricing: https://supabase.io/pricing
[4] Docker: https://github.com/supabase/supabase/tree/master/docker