Neon WS Proxy
Neon WS Proxy is a lightweight WebSocket→TCP proxy for Neon’s serverless Postgres tooling. It accepts wss connections and forwards them to Postgres as TCP; one-sentence value: it enables Neon’s serverless driver to connect over wss so edge and serverless runtimes can reach Postgres with lower latency.
It targets developers using Neon’s serverless driver on edge runtimes, small teams building serverless apps, and platform/ops on small infrastructure. It solves blocked outbound TCP from edge/serverless environments, simplifies local development and ephemeral CI tunnels, and provides a minimal proxy when full connection pooling is unnecessary.
Use Cases
- Local Next.js development: run Docker proxy for Neon serverless driver.
- Edge-hosted hobby projects that restrict outbound TCP.
- Codespaces/CI ephemeral DB tunnels for pull-request testing.
- Serverless functions and edge dashboards needing Postgres queries.
- Lightweight proxy for dev/test instead of pgbouncer.
Strengths
- Enables wss-to-TCP forwarding for Neon serverless driver.
- Lower-latency edge and serverless Postgres connections.
- Runs as simple Go binary or Docker image.
- Small focused codebase: minimal operational surface and debugging.
- Can front Neon-hosted or self-hosted Postgres instances.
- Quick local or containerized deployment for dev and test.
- Self-host friendly; trivial deployment on Coolify (assumed).
Limitations
- Not a connection pooler; forwards connections, not multiplexes them.
- Limited operational maturity and no formal release tags (Unverified).
- Adds an extra network hop; verify TLS and auth controls.
- Not suited alone for high-concurrency production workloads.
- Potential vendor-lock patterns when paired with Neon-specific drivers.
Final Thoughts
Try it now if you need a quick local or edge wss bridge for development, Codespaces, or small serverless deployments. Wait if you require production-grade pooling, high concurrency, or formal support and observability.
Choose a managed proxy when you need connection pooling, autoscaling, monitoring, and vendor SLAs; managed options add pooling and operational support that this lightweight proxy does not provide.