If you've ever tried to hit your own Redis from a Cloudflare Worker, you know how fast you hit a wall. Serverless and edge runtimes can't open raw TCP sockets — so talking to your existing databases means migrating to a vendor-managed DB, setting up a VPN, or just accepting it's not going to work. I built ZedGi to fix this. It's a TCP-to-HTTP proxy that lets you connect your own Redis, Postgres, or MySQL from any HTTP-only runtime over plain HTTPS. Register your service in the dashboard, drop in the JS or Python SDK, and you're connected. The key thing: your database credentials never touch our servers. They're encrypted client-side with X25519 + AES-256-GCM before they leave your browser. ZedGi never stores them, never logs them, never sees them. You might be thinking, "Cloudflare Hyperdrive already does this." It covers Postgres and MySQL, but not Redis — and it only works from Workers. ZedGi handles all three protocols and more, works from any runtime: Workers, Vercel Edge, Deno Deploy, or anything else that can make an HTTPS request. I built this because I kept running into the same dead ends: Redis pub/sub, Postgres LISTEN/NOTIFY, persistent connection pooling — all impossible from the edge without a stateful bridge. Now it works. What database protocol gives you the most headaches from edge runtimes? Happy to answer anything about the architecture or the zero-knowledge credential model.

ZedGi

ZedGi — TCP-to-HTTP proxy for Redis, Postgres, and MySQL

ZedGi — TCP-to-HTTP proxy for Redis, Postgres, and MySQL