Skip to content
312 PoPs · 792ms Get a Live Demo →
Product Overview

Real Experience Score, streamed from 312 edge PoPs in under a second.

ZoneFlash is the only edge-native RUM platform that ingests user-experience telemetry at the nearest collector, then ships a single composite score to your console. Median time-to-first-insight is 792 ms — measured end-to-end, from browser event to dashboard cell, in the 2024 WebPerf Audit.

Get a Live Demo See Customer Results

Trusted by 1,840+ engineering teams · deployed in 47 countries · 9.4T events processed in 2024

zoneflash — rxs.stream / live LIVE
REGION RXS P95 LCP INP STATUS
us-east-2 98.4 1.12s 42ms nominal
fra-1 96.1 1.38s 58ms nominal
sin-3 91.7 1.94s 84ms watch
syd-1 88.2 2.21s 112ms watch
gru-1 94.6 1.55s 71ms nominal
nrt-2 99.1 0.98s 36ms nominal
stream latency 768 ms
EDGE · 312 PoPs
us-east-2
fra-1
sin-3
syd-1
gru-1
nrt-2
STREAM INGEST · TLS 1.3 / QUIC
aggregator.eu-west.rxs p50 112 ms
aggregator.us-east.rxs p50 104 ms
aggregator.ap-south.rxs p50 128 ms
ANALYTICS PLANE · RXS Engine
792ms median time-to-first-insight
312poPs active collectors, 6 continents
9.4T events processed in 2024
97.4% gross retention, FY22–FY24
Architecture

Ingest at the nearest PoP. Stream in under a second. See the regression in your console.

Every visitor event lands at one of 312 globally distributed collectors — never at a distant monolith. From there it travels through our QUIC-based stream aggregator and is scored against the Real Experience Score model within the same browser tick. There is no overnight batch window, no five-minute polling delay, no “explore” pane you have to refresh.

  • 01

    Local ingest, local hashing

    Each PoP hashes and rolls up events at the edge before they leave the region, so customer PII never traverses the public internet twice.

  • 02

    QUIC stream to the analytics plane

    Encrypted, multiplexed, and back-pressured. Aggregators fan into the RXS engine without dropping sessions under load spikes.

  • 03

    Console + webhook in the same tick

    Alerts, dashboards, and Slack/PD hooks all subscribe to the same stream — no second pipeline to maintain.

Integrations

Four paths into ZoneFlash. Pick the one that matches your stack.

No agent zoo. No sidecar sprawl. Whether you ship a React SPA, a Cloudflare Worker, or a Rust service on bare metal, the same RXS surface shows up in your console within the first deploy.

01

Frontend SDK

Drop into any SPA, SSR, or static site

  • Next.js · Nuxt · Remix · Astro
  • React · Vue · Svelte · SolidJS
  • Web Vitals auto-binding · custom metric hooks
~14 kB gzipped zero-config beacon
02

Edge Runtime Shim

Instrumentation at the request boundary

  • Cloudflare Workers · Vercel Edge · Fastly Compute
  • Deno Deploy · Netlify Edge Functions
  • Headers, TTFB, and origin-timing capture
~3 ms p99 overhead works with Wasm isolates
03

OpenTelemetry · eBPF Ingest

Server-side telemetry, one agent per host

  • OTLP/HTTP and OTLP/gRPC receivers
  • Native eBPF probes for Node, Go, Rust, JVM
  • Replaces four legacy agents per host
OTel 1.27+ Linux 5.10+ kernels
04

CDN Tap Integration

Pull logs from where the bytes already live

  • Cloudflare Logpush · Fastly Real-time Logs
  • Akamai DataStream · AWS CloudFront
  • No origin changes · no DNS reroute
5-min setup read-only IAM role
Compatibility Matrix

Frameworks, CDNs, edge runtimes — already shipping with ZoneFlash.

Every tile below is a first-class integration, not a community plugin. If your stack is here, the console will be live before your next deploy window.

Frontend Frameworks
  • Next.js
  • Nuxt
  • Remix
  • Astro
  • SvelteKit
  • React
  • Vue
  • SolidJS
  • Ember
  • Angular
Edge Runtimes
  • Cloudflare Workers
  • Vercel Edge Functions
  • Fastly Compute@Edge
  • Deno Deploy
  • Netlify Edge
  • AWS Lambda@Edge
  • Bun Runtime
  • Hono Middleware
  • itty-router
  • Lagon
CDNs · WAFs
  • Cloudflare
  • Fastly
  • Akamai
  • AWS CloudFront
  • Azure Front Door
  • Google Cloud CDN
  • KeyCDN
  • BunnyCDN
  • StackPath
  • Section
Telemetry Standards
  • OpenTelemetry 1.27+
  • W3C Trace Context
  • eBPF (CO-RE)
  • Web Vitals v3
  • Performance Observer
  • Server-Timing
  • Beacon API
  • Logpush / DataStream
  • Prometheus Remote Write
  • StatsD
Backend Runtimes
  • Node.js
  • Go
  • Rust
  • Java / JVM
  • Python
  • Ruby
  • PHP / FrankenPHP
  • .NET 8
  • Elixir / BEAM
  • Kotlin
Alerting · Collab
  • PagerDuty
  • Opsgenie
  • Slack
  • Microsoft Teams
  • Jira
  • Linear
  • GitHub Issues
  • Webhook (custom)
  • Email digests
  • SMS via Twilio

Don’t see your stack? Our SDK is open-core and the collector speaks OTLP out of the box.

Ask about a custom integration
The Real Experience Score

A reproducible composite metric, with the math published.

The Real Experience Score (RXS) is a 0–100 weighted aggregate of four signal families: load timing (LCP and TTFB), interactivity (INP and long-task duration), visual stability (CLS), and business criticality (per-route conversion impact, supplied by your analytics export). The default weights were derived from a regression against 2.1 billion anonymized sessions across 41 referenceable customers in 2023, and are re-fit quarterly.

What makes RXS different from a single Web Vital is the criticality term. A 200 ms LCP regression on your checkout route hurts RXS far more than the same regression on a marketing landing page — the score reflects what your users actually convert on, not just what they happen to load. Every weight in the model is exposed in the whitepaper, alongside the bootstrap procedure and the false-positive rate we measured against the 2024 WebPerf Audit ground truth.

For the serious reader, the appendix covers the rolling-window decay function (we use a 28-day half-life, not a naive mean), the confidence interval we publish per segment, and the exact formula we use to attribute a regression to a specific deploy. We publish the methodology because we want the score to be defensible — it is the only metric on the dashboard your CTO will be asked about by the board.

RXS =100 · σ(wL·L + wI·I + wV·V + wC·C)
Load timing Interactivity Visual stability Business criticality
Request the Whitepaper Read the Methodology
Book a 20-minute demo

See your own routes, on your own map, scored live.

On the call we’ll spin up a sandbox tenant against your production hostname, replay your last seven days of traffic through the RXS engine, and drill from a 312-PoP world map down to a single Core Web Vital on a single route. You’ll leave with a CSV of regressions and the median time-to-first-insight we measured on your stack.

  • 01 Sandbox tenant, your hostname, your data
  • 02 7-day replay through the RXS engine
  • 03 PoP-level drill-down on any regression
  • 04 Walk-out with a CSV and a measured p50
Get a Live Demo Review Pricing

No slide deck. No sales engineer monologue. A console, your routes, and 20 focused minutes.