SSE streaming to millions, brokerless.
RevenProx is a high-performance Server-Sent Events proxy built in Zig. It fans real-time event streams out to 10M+ concurrent clients across a distributed NNG mesh — with JWT auth, topic-based routing, and a memory footprint small enough to make it affordable.
Real-time delivery, without a broker
Everything a streaming edge needs to hold millions of long-lived connections and route events precisely.
Massive scale
Designed for 10M+ concurrent SSE connections across 100+ proxy instances — real-time delivery that grows horizontally.
Brokerless architecture
No central message broker. State and messages flow across a fully distributed NNG mesh, so there is nothing to bottleneck or babysit.
Topic-based routing
UUID-based topics route events efficiently to exactly the clients that subscribed — no fan-out waste.
JWT authentication
Secure, webhook-based token verification with caching and a circuit breaker to protect upstreams under load.
Built in Zig
Maximum performance with a minimal, predictable memory footprint — no garbage collector, no heavyweight runtime.
Production-ready
Rate limiting, connection pooling, graceful shutdown, and first-class observability are built in.
One binary, then stream
Build with Zig, point clients at a topic, and start delivering events.
# Clone and build a single static binary
git clone https://github.com/dotcommoners/revenprox.git
cd revenprox
zig build -Doptimize=ReleaseSafe
# Run the proxy
./zig-out/bin/sse-proxy --config config/proxy.toml
# Subscribe a client to a topic (JWT-authenticated)
curl -N "http://localhost:8080/events/my-topic" -H "Authorization: Bearer <jwt>"Where RevenProx fits
AI inference & token streaming
Stream LLM tokens and agent events to huge audiences without a broker bottleneck.
Live dashboards & notifications
Push metrics, alerts, and real-time updates to millions of open browser tabs.
Build logs & live feeds
Relay CI/CD output, activity feeds, and one-way event streams at the edge.
Questions
What is RevenProx?
RevenProx is an open-source, high-performance Server-Sent Events (SSE) proxy written in Zig. It relays long-lived SSE streams to very large numbers of concurrent clients, using a brokerless NNG mesh for distributed state, topic-based routing for targeted delivery, and JWT authentication for security. It is MIT-licensed and self-hostable.
How many connections can RevenProx handle?
RevenProx is architected for 10M+ concurrent connections spread across 100+ proxy instances. Because it is brokerless and horizontally scalable, you add capacity by adding instances to the NNG mesh rather than scaling a central broker.
Why build an SSE proxy in Zig?
Zig gives RevenProx maximum throughput with a minimal, predictable memory footprint and no garbage collector — ideal for holding millions of idle-but-open streaming connections where per-connection overhead dominates cost.
How is it different from using Nginx or a generic reverse proxy for SSE?
RevenProx is purpose-built for SSE at scale rather than a general reverse proxy adapted to it. It adds distributed, brokerless state synchronization (bloom + merkle + vector clocks), UUID topic routing, per-topic fan-out, JWT verification with caching and a circuit breaker, and connection pooling tuned for millions of long-lived streams.
Is RevenProx open source and self-hostable?
Yes. RevenProx is MIT-licensed and runs on your own infrastructure. It builds to a single binary with Zig and ships with Docker and Kubernetes deployment guides.
Stream at scale
Read the docs, browse the source, or reach out. Open source and self-hostable.