Product roadmap

Relay’s primary lane is Pusher-compatible excellence: lowest-friction migration, stable wire protocol, first-class Laravel + SDK ergonomics, and honest operational visibility. Durability, stream processing, and deep automation build on top of that spine—they are sequenced so the core path stays fast and reliable.

Sequenced priorities

1. Core path hardening — Relay ↔ Laravel ↔ Redis connectivity, clear env documentation, dashboard preflight (System preflight for admins), and predictable limits (Semantics & guarantees).
2. Explicit semantics — Published limits and delivery expectations (this site + API docs) kept in sync with PlanEnforcementService and relay behavior.
3. Observability — Trace ids on publish, in-app trace lookup, DLQ visibility, and correlation across logs (shipping incrementally).
4. Durable streams & advanced processing — Event store, replay, routing, and integrations after the core path is reliable for most tenants.

What “availability” means here

• Instance availability: run multiple relay processes with Redis fan-out; health checks on /health.
• Operational availability: admins can see traffic snapshots and system checks when tokens and URLs are configured.
• Regional / multi-region deployments are a separate architecture decision (DNS, latency, data residency)—not implied by single-region relay docs alone.

Questions or priorities for your org: use dashboard support channels or your account team.