Ingest the user experience.
Connect it to service evidence.
Epok’s owned ingest brings browser Core Web Vitals, frontend errors and DOM-level session replay into the same pipeline as logs, metrics and traces, on the same meter. Shared trace context links the user experience to backend requests. Vitals changes, error patterns and trace-linked user impact become evidence items with receipts and coverage for your team and agents.
A backend error does not establish what the user experienced. A replay shows the interaction, browser signals show the vitals and failed requests, and shared trace context connects them to the backend evidence.
Epok makes those links and their limits visible. Trace-linked replay needs shared trace context; customer impact needs a customer identifier. Coverage records missing inputs and what was not seen, so absent user evidence does not become a claim that nobody was affected. Inspect an evidence item or request MCP agent gateway access.
Session replay, stitched to the trace
With shared trace context propagated from the browser to the backend, an errored trace on the investigation canvas links to its session replay. Open the replay at the moment of failure and inspect the lead-up alongside the request evidence.
Core Web Vitals, per page and per release
LCP, INP and CLS measured from real sessions, broken down by page and release. Changes become evidence for investigating a regression; a nearby release is context, not proof of its cause.
Frontend errors, correlated to the backend
JavaScript errors and failed requests captured from the browser and grouped by shape, then linked to backend spans and logs where trace context is shared. The evidence engine records patterns and observations with receipts for analysis to check.
One snippet — no per-seat tax
A lightweight browser snippet turns on RUM and replay. There is no per-seat RUM tier and no per-session replay charge — it rides the same flat meter as every other signal.
Inputs masked by default
Replay always masks input values, and the capture key is ingest-only. Non-input text is recorded by default; mask sensitive text by selector. Configure masking for your application and inspect the captured session against the privacy guide before shipping.
On the same investigation, not a separate tab
RUM and replay share the investigation canvas with logs, traces, metrics and infrastructure. Epok commits a cause only with supporting evidence; otherwise it says what is missing and what to check next. Recovery starts with change and blast radius while analysis continues. We recommend; you execute.
- ✓From a failing trace, one click to the session replay of the user who hit it — seeked to the error
- ✓Core Web Vitals and frontend errors compared across releases, with backend trace links where trace context is shared
- ✓RUM and session replay on one flat bill — no per-seat tier, no per-session charge, no cardinality tax
Browser RUM and replay use a web snippet. Use open shippers — no proprietary Epok agent for server-side telemetry. Your team inspects the evidence in the app; agents use the MCP agent gateway, with access on request. The demo uses synthetic data.
Inspect the incident evidence. No signup.
The live demo uses synthetic data. Follow the evidence and its receipts, or send your own telemetry in the 14-day trial.