Verify before you commit
Use this page to sanity-check Openreplay quickly. We surface the evidence tier, freshness, and failure posture here, then put the official links where you can actually act on them, especially on mobile.
Evidence
Assessed
Docs reviewed · Mar 29, 2026
Freshness
Updated 2026-03-29T14:20:26.607+00:00
Mar 29, 2026
Failures
Clear
No active failures listed
| Dimension | Score | Bar |
|---|---|---|
| Execution Score Measures reliability, idempotency, error ergonomics, latency distribution, and schema stability. | 8.2 | |
| Access Readiness Score Measures how easily an agent can onboard, authenticate, and start using this service autonomously. | 8.2 | |
| Aggregate AN Score Composite score: 70% execution + 30% access readiness. | 8.2 | |
No active failure modes reported.
Published review summaries with trust provenance attached to each card.
Docs-backed Built from public docs and product materials.
Test-backed Backed by guided testing or evaluator-run checks.
Runtime-verified Verified from authenticated runtime evidence.
Open-source session replay platform recording DOM mutations, network requests, Redux/Vuex state, console errors, and user interactions. Co-browsing (Assist) for live support. Rage-click and dead-click detection. Feature flags and A/B experiments. Self-hosted on Kubernetes via Helm or managed on OpenReplay Cloud. Confidence is docs-derived.
JavaScript SDK: new OpenReplay({ projectKey }) with .start() for session capture; tracker plugins: @openreplay/tracker-redux (state), @openreplay/tracker-fetch (network), @openreplay/tracker-graphql; server-side setUserID/setMetadata for session enrichment; REST API for session export and metadata query; webhooks for session-started and error-detected events.
Project key per site for tracker initialization (public — included in page JS); backend admin uses email/password auth; REST API uses API key from project settings; data stored on self-hosted infrastructure under operator control; GDPR compliance via openreplay.sanitize() and input masking configuration; no third-party telemetry from self-hosted.
Session recording is async and uses a ring buffer to minimize memory footprint; network request capture sanitizes Authorization headers by default; Assist co-browsing uses WebRTC for low-latency screen share; self-hosted Kubernetes deployment uses S3-compatible object storage for session data; REST API returns paginated session list with filtering by user, error, and custom metadata.
Documentation covers SDK quickstart, plugin integration guides (Redux, Vuex, GraphQL, Fetch), Kubernetes deployment guide, co-browsing setup, and REST API reference. Self-hosted Helm chart for production deployments. Active Discord community. Confidence is docs-derived.
Trust shortcuts
This score is documentation-derived. Treat it as a docs-based evaluation of API design, auth, error handling, and documentation quality.
Read how the score works, how disputes are handled, and how Rhumb scored itself before launch.
Overall tier
8.2 / 10.0
No alternatives captured yet.