This sounds cool (but it's not something we've built at Neon).

In case it's useful, I can clarify:

* Every Neon database is accessible over an ordinary TCP Postgres connection (as well as WebSockets and http).

* Our JavaScript serverless driver is based on node-postgres and is a drop-in replacement for it. So for JS, no rewriting is needed.

Assuming that doesn't help, do you specifically need http (rather than WebSockets), and a proxy that speaks the pg protocol?

If not, the simplest thing might be to (1) use Neon, or run a WebSocket proxy next to your own database (e.g. https://github.com/neondatabase/wsproxy); and (2) find/write a similar WebSocket proxy, but in reverse — i.e. one that listens out for TCP/socket connections and tunnels them over WebSockets — to run next to the agents.