Ultra-low latency distributed messaging network
What we are working on now and what is coming next
Core systems that are operational today
QUIC relay backbone is live. Dozens of stationary PoPs spread across the globe plus up to 40 anycast access points worldwide. Relays discover each other, establish encrypted tunnels, and form a resilient mesh.
Publish/subscribe is working end-to-end. Writers publish to the nearest PoP, the relay mesh forwards along the best measured path, destination PoP fans out to all subscribed listeners.
Token-based authentication is in place. Clients receive access tickets with scoped permissions (publish/subscribe per channel). Tokens are validated on every PoP.
Central management service is operational: tenant management, token issuance, configuration push to PoPs.
Relays continuously measure RTT between each other and compute fastest paths using Distance Vector. Traffic is routed through the lowest-latency path in real time.
dashboard.fastpubsub.com — real-time world map of PoPs, overlay vs direct latency comparison, network anomaly detection. Uses our own FastPubSub infrastructure to deliver live updates to the browser.
Core infrastructure and tools needed before public launch
Per-PoP and per-channel metrics: message rates, connections, latency histograms, GeoIP, bot detection. Prometheus export + internal dashboards.
This is a key target of the project and work in this direction has been ongoing since day one. The current architecture still has a single point of failure that needs to be resolved. Goal: fully distributed/redundant model with replicated control plane, multi-path relay failover, and no single node whose loss breaks the system.
Lightweight libraries for JavaScript/TypeScript, Python, Go, Rust, C#, Java. Auto-reconnect, channel subscribe/publish, token refresh.
Web UI for tenant owners: manage channels, view live metrics, create tokens, see connection map. Built on top of Control Plane API.
Per-tenant and per-channel rate limits (msg/s, bytes/s, connections). Backpressure, slow-consumer drop policy, IP-based throttling.
Getting started guide, API reference, integration examples, security best practices, deployment guide for self-hosted scenarios.
Message counters per tenant, usage aggregation, quota enforcement. Foundation for paid tiers and metered billing.
Concepts we are thinking about. Not committed yet, but high potential.
Who is online in a channel, subscriber count.
A ready-made HTTPS endpoint on the nearest PoP where clients can POST events. We turn them into channel messages and fan out to listeners instantly. Universal webhook receiver with zero infrastructure for the client.
FastPubSub as a "network adapter" between external protocols and our channels. Connect existing systems without rewriting them for our SDK.
A customer-hosted node inside a private network. Exposes local WebSocket/HTTP endpoints and maintains an outbound-only mTLS tunnel (WebSocket or gRPC over TLS) to the FastPubSub fabric. No inbound firewall ports needed.
QUIC DATAGRAM as an additional transport option alongside WebSocket streams and QUIC streams. Unreliable delivery mode for real-time state updates and fast control signals where "latest matters, not every packet".