I found their docker-compose more helpful than their chart: https://github.com/neondatabase/neon/blob/main/docker-compos...

But I also needed to read their Ansible files to understand how they manage their infra better. Those are deleted now, but luckily you can just look at the history (commit that deleted it: https://github.com/neondatabase/neon/commit/0d3d022eb1fe4a42...)

I found installation instructions for Neon including Ansible files here: https://percona.community/labs/serverless-postgresql/docs/in...

That is super helpful and also kinda weird that it's on the percona website and not somewhere in the Neon docs

Yes, you'd have to do some own work to set up a direct competitor from the provided pieces.

They have published a new piece which is how they vertically autoscale Postgres in Kubernetes: https://github.com/neondatabase/autoscaling

Neon CEO here.

Autoscaling with live VM migrations is quite cool. Here is a blog post on it: https://neon.tech/blog/scaling-serverless-postgres

And yes, the code is open feel free to use it!

Yeah I'm not complaining - I mention it because if you're a bit.io customer that wants to migrate to another serverless Postgres solution you won't be able to do it by "just" running the linked helm charts.

(In my opinion) when someone says here's the helm chart I assume running "helm install $THING" would give me a running version of $THING, so it's more so no one has the wrong expectations (like I would)