4 ms·
What happens to existing customers of Neon?
by anshumankmr 1y ago
What happens to existing customers of Neon?
- joshstrange 1y agoAsk the bit.io customers…. Most likely a holding state for a bit before databricks ruins it or shuts it down. I started looking around when the news broke last week or so for alternatives.
- anshumankmr 1y agoAny alternatives that you are aware of ? Most search results show me Supabase.
- joshstrange 1y agoSupabase is one that I'll consider, Xata [0] is another one that is interesting. Thankfully I just need "postgres", I don't need branching/PII-clearing/etc. That's all nice to have but I don't need it for my app. I really would prefer a managed DB for multiple reasons but I might need to look at just self-hosting. I might have spent less time futzing with my DB if I had done that from the start instead of going Aurora Serverless v1 -> Planetscale -> Neon. [0] https://xata.io/ https://xata.io/
- anshumankmr 1y agoSame here...I too just need Postgres... Will check out Xata, My workload isn't super critical.
- gniting 1y agoPrisma Postgres is also an option to dig into: https://prisma.io/postgres https://prisma.io/postgres
- plumeria 1y agoBranching is one of the most useful features of Neon.
- joshstrange 1y agoI believe that, it's a cool concept. But I was too nervous to build on top of that feature, I wanted to maintain my ability to leave Neon easily. After Planetscale (and using their version of schema branching) I didn't want to get pinched again when I went to switch (PS vs Neon branching was/is very different). I think one of the coolest features of neon is being able to quickly spin up new DBs via the API (single tenant DBs) and while that is cool, my client list is small so manually creating the DBs is not a problem (B2B).
- davidgomes 1y agohttps://neon.tech/databricks-faq https://neon.tech/databricks-faq