rubix-studios-pty-ltd/rubix-redis-bridge — explained in plain English
Analysis updated 2026-05-18
Expose a private Redis instance over HTTP for serverless functions that can't open a direct TCP connection.
Swap Upstash's hosted SDKs to point at a self-hosted Redis bridge with the same request format.
Enforce a command allowlist and hard-denied commands before requests reach Redis.
Monitor the bridge's health and metrics through Prometheus-compatible endpoints.
| rubix-studios-pty-ltd/rubix-redis-bridge | dhkts1/teamclaude-rs | eternal-flame-ad/unitdc-rs | |
|---|---|---|---|
| Stars | 5 | 5 | 5 |
| Language | Rust | Rust | Rust |
| Last pushed | — | — | 2024-10-12 |
| Maintenance | — | — | Stale |
| Setup difficulty | — | easy | moderate |
| Complexity | — | 2/5 | 2/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Rubix Redis Bridge is a self hosted piece of software that sits in front of a Redis database, a fast in memory data store many applications use for caching and quick lookups, and exposes it over a web style HTTP API instead of Redis's normal direct connection protocol. It is aimed at teams who like the simplicity of Upstash, a hosted Redis-over-HTTP service, but want to run that same kind of API themselves on their own private infrastructure. The bridge is meant for situations where an application cannot make a normal direct connection to Redis, such as serverless functions, services running inside Docker or Tailscale private networks, or other integrations that only speak HTTP. Applications that already use Upstash's own developer libraries for Redis, rate limiting, or realtime features can point those same libraries at this bridge instead, since it is built to accept the same request format. Before any command reaches the actual Redis database, the bridge checks a bearer token to confirm the caller is authorized, and applies a configurable policy of which Redis commands are allowed or specifically blocked, on top of limits on request size, argument count, and how long a request is allowed to run. It supports sending a single command, a batch of commands as a pipeline, or a set of commands as a managed transaction, plus a realtime subscription feature for streaming updates as they happen. It also exposes health check endpoints and metrics in a format the Prometheus monitoring tool can read. The project is designed to be run as a Docker container, configured through environment variables such as which Redis server to connect to, what token to require, and which specific Redis commands to permit. It is released under the MIT License and includes automated tests to check it stays compatible with the official Upstash software development kits.
A self-hosted HTTP gateway that exposes Redis with Upstash-compatible endpoints, token auth, and command allowlisting.
Mainly Rust. The stack also includes Rust, Axum, Redis.
Mainly developer.
This repo across BitVibe Labs
double-check against the repo, no cap.