(Neon ceo) 1. You should try and see the experience 2. It scales to 0. If you have lots of projects aurora costs really add up 3. It supports branches and integrates with vercel. You can have environment for every dev and every pr. 4. We will be on multiple clouds soon 5. We are just getting started

Hello, not parent

I wish you the best of luck, but please know that for a lot of us time is money and also literally our most invaluable / irreplaceable asset, and also tech startups who want us to make a bet on them need to have some sort of value proposition given the risk of "you might die or disapear or be aqui-hired in three months after we moved" so I would encourage to not answering this as your 1).

To me the instinctive reaction is "it's for when you will have time to fool around and figure it out by yourself". It is my opinion only, it's worth nothing more than that, and I realize you didn't ask for it, but I just wanted to let you know.

In the linked article it says:

"Unlike AWS Aurora we decided to open source all the changes in Postgres and also send them upstream as well as fully open source our cloud native storage."

Also, at the top right there's a link to the GitHub repo: https://github.com/neondatabase/neon

You can find replies from folks in this thread as well discussing self hosted deployments and you can find an entire discord channel dedicated to that topic here: https://discord.gg/92vNTzKDGp

I'm not associated with Neon and I've never used it before and I certainly don't disagree with your sentiment, but it seems like Neon has gone above and beyond in making sure that workloads could continue to run in the event the company fails and broadly assuaging those concerns.

The full control plane is not open source, so if you use tenants or many of the not-in-postgres features you will need to implement the control plane. It's not too much work to do so - there's already a few open source projects starting to do so - but just be aware of that.

We have a toy control plane implementation in the neon repo aliased to `cargo neon`, but also available as `neon_local`. I'm honestly not sure if open-sourcing the production control plane is in our future.

(Neon engineer)

(From molnett.com) For us that self-host, the architecture of building cold storage on top of Object Storage and warm storage on top of NVMEs is unbeatable. It enables us to build a much more cost-effecting offering while keeping Postgres as our database.

> Neon ceo) [...] It scales to 0.

> (Neon DevRel here) [...] However, many production databases won't scale to zero often.

I think a planned consistent message might be best

(employee)

Neon won't pull the rug from under an active production database by scaling to 0 when there are still active queries, instead it'll scale databases to 0 only after a longer period of inactivity. So production databases are less likely to scale to 0 because they generally are active most of the time, yet Neon does scale to 0 when it's possible and allowed.

> (Neon ceo) 1. You should try and see the experience

And what would be that "experience"? Bro, it's a managed Postgres instance. From what you've wrote the main points are:

1) It costs less than Aurora (some numbers on that?)

2) It integrates with Vercel (some hobbyist PaaS)

Branching would be valuable

> Bro, it's a managed Postgres instance

I could've sworn I closed my Reddit account. I thought neon was meant to be a bit like Git with data, with branches etc, as well as autoscaling and nice stuff like that.

Is 5 a reference to how you naked the prices so Neon doesn’t work for light-workload, moderate storage databases anymore? $69+ a month for a Segment data warehouse holding 10gb is obnoxious. It was under $10 before the switch. What’s next? $690/mo?