Before the usual comments, yes, native TCP is faster and exposing Redis directly to the internet is dangerous.
The problem is that Redis has traditionally been difficult to use from serverless platforms and environments with dynamic IP addresses, strict firewall policies or networking restrictions where opening a Redis port is either impractical or impossible.
Cloudflare recently introduced Workers support to address this problem. While that approach works, it still relies on creating Redis connections from a serverless runtime, which can become inefficient when every request establishes a new connection.
Rubix Redis Bridge takes a different approach. Similar to Upstash, it exposes Redis through an HTTP API gateway instead of exposing Redis itself. Unlike projects such as Webdis or other Redis-over-HTTP gateways, Rubix Redis Bridge supports Pub/Sub, is written in Rust, and includes strict security boundaries designed to minimise the attack surface of an internet-facing Redis service.
The bridge does not create a new Redis connection for every HTTP request or rely on inefficient command loops. Commands are pipelined where appropriate and grouped into MULTI/EXEC transactions where possible to reduce round trips and improve efficiency.
Current benchmarks show approximately a 25 to 33 percent operational overhead compared to direct Redis TCP connections while still achieving around 7,000 to 10,000 operations per second, depending on workload.
Why Rubix Redis Bridge instead of Upstash?
Rubix Redis Bridge delivers a comparable HTTP API while remaining completely self-hosted.
Key advantages include:
No vendor lock-in. No enterprise licensing restrictions. Freedom to choose Redis, Valkey, DragonflyDB, KeyDB or other compatible backends. Infrastructure remains under your control. Costs are based on your own hosting rather than managed service pricing. Compatible with Upstash Redis SDKs, Rate Limiter and Realtime. Your data remains yours and is stored wherever you choose to host it.
https://github.com/rubix-studios-pty-ltd/rubix-redis-bridge
Check it out, be aggressive and judgemental, as this will allow us to fix, optimise and continue to develop this project.