autoscaling

It's not clear to me that the _entire_ Neon stack is OSS and available to self-host (though they do share a lot of OSS code, which is great), and in any case, it's not currently supported/documented beyond some "local development" instructions, e.g. "We do not officially support use of autoscaling externally" [0] > Can’t you use a cloud provider and have them host this for you? If it really is all OSS, then I guess the moat is the impressive execution of this team. [0] https://github.com/neondatabase/autoscaling

I consider Kubernetes to be an excellent framework to build these kinds of applications. The difference here is Gitpod being stateful, which is notoriously hard on Kubernetes, though easier now than ever before! To clarify on one of your points, Kubernetes itself has nothing to do with actually setting the security boundaries. It only providers a schema to describe resources and policies, and then an underlying system (perhaps Cilium for networking, or Kata Containers for micro VMs) can ensure that the resources created actually follow those schemas and policies. For example, Neon have built https://github.com/neondatabase/autoscaling which manages Neon Instances with Kubernetes by running them with QEMU instead. This allows them to do live migrations and resource (de)allocation while the service is running, without having to replace Kube

Sure! Each instance of Postgres runs inside a qemu VM, inside a kubernetes pod. The VM provides isolation, autoscaling, metrics, and (eventually) live migrations. These VMs share AWS Metal nodes. Source code here: https://github.com/neondatabase/autoscaling

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

Take a look at this issue: https://github.com/neondatabase/autoscaling/issues/104. There is an image there that explains it.