Yeah! these are just normal websockets. We're definitely interested in supporting and testing more protocols and ways of accessing postgres and neon as we can. We're also super excited to see the development and adoption of new protocols!

Well, the data is absolutely not ephemeral: it's safely tucked away in S3.

But to crib from https://neon.tech, you might choose Neon because it's scalable, cost-effective, and easy to deploy and manage. Or you might choose it for its copy-on-write branching and point-in-time recovery, all open-source, and all on top of the solid, performant, feature-rich foundation that is Postgres. :)

Neon separates storage and compute. The compute part is serverless and can scale up and down on demand. The storage has multiple layers: Safekeepers for durability and Pageservers to reconstruct pages from WAL.

The data is also offloaded to S3. Here is a diagram that describes the architecture: https://neon.tech/_next/image?url=https%3A%2F%2Fneon-hwp.dre...

To follow up on Raouf's comment, here is a blog post[0] that describes Neon's architecture in more detail.

[0]: https://neon.tech/blog/architecture-decisions-in-neon

Fair point! We'll fix this. In the meantime, the graphs show latency distributions, so the X axis is time (in milliseconds) and the Y axis is a simple count.

Thank you. We fixed it now.