I haven't studied the CLA situation in order to know if a rug pull is on the table but Tofu and Valkey have shown that where there's a will there's a way
Thankfully, you can continue to pay Databricks whatever they ask for the privilege of them hosting it for you
[1] https://aws.amazon.com/blogs/database/introducing-scaling-to...
Either way, there are plenty of other serverless Postgres options out there, Supabase being one of the most popular.
You set up a database, you connect to it, they take care of the rest. It even scales to $0 if you don't use it.
Is that not serverless Postgres?
How is what Supabase offers different from what Neon offers from a user perspective?
Supabase gives you a server that runs classic Postgres in a process. Scaling in this scenario means you increase your server's capacity, with a potential downtime while the upgrade is happening.
You are confusing _managed_ Postgres for _serverless_.
Others in the serverless Postgres space:
- https://www.orioledb.com/ (pg extension)
- https://www.thenile.dev/ (pg "distribution")
- https://www.yugabyte.com/ (not emphasizing serverless but their architecture would allow for it)
After a funding round the value extraction from customers is just over the horizon