Depending on what parts you want to self-host. You can already build and run all base components on your local machine, see instructions here: https://github.c

Depending on what parts you want to self-host. You can already build and run all base components on your local machine, see instructions here: https://github.com/neondatabase/neon/tree/d11c9f9fcb950ac263b1fa16651976ca11e96edf#running-local-installation https://github.com/neondatabase/neon/tree/d11c9f9fcb950ac263... . You can run the tests instead if you want more insight into how a particular piece works. You probably want to attach your S3-compatible storage to Pageserver and Safekeepers; some Ansible scripts with command-line flags are in the repository. To run Neon components on multiple machines, you should be able to create the `.neon` data directory via `neon_local init` and then share the generated configuration files across machines and tweak network settings. You can refer to our documentation to understand the terminology and the intended hosting configuration: https://neon.tech/docs/storage-engine/architecture-overview/ https://neon.tech/docs/storage-engine/architecture-overview/ However, there are still two missing bits: the self-hosting documentation and the Neon Control Plane (web UI + K8S-based compute nodes orchestrator). So you don't get automatic scale-to-zero at the moment out-of-the-box, although all hooks and the PostgreSQL proxy we're using at pg.neon.tech are there. We consider open-sourcing the Control Plane, so stay tuned. As for documentation and support, Nikita has already answered.