# OpenReplay > OpenReplay is an open-source, self-hostable session replay, co-browsing and product analytics platform for debugging web and mobile apps with full data ownership. _This is the full-content companion to [/llms.txt](https://openreplay.com/llms.txt). It expands each area of the site with detailed, factual descriptions so AI systems can understand OpenReplay from a single document. For the concise link index, see llms.txt._ ## Product ### Session Replay OpenReplay Session Replay reconstructs user sessions through DOM-based, pixel-perfect playback rather than video, capturing page structure and changes, page views, and user interactions including clicks, scrolls, inputs, and mouse movement. Its Autocapture mode records 100% of user activity (views, clicks, movements, and form fills). Replays are paired with DevTools data—console output, network requests (including failed requests), and JavaScript errors—plus performance metrics such as frame rate, CPU, and memory. The recorder also handles Canvas and WebGL content, cross-domain iframe interactions, and tabbed browsing, stitching activity across multiple tabs into a single session. Analysis and navigation features include: - Omni Search: search and filter sessions by user interaction or event. - X-Ray view: a unified view of network issues, performance slowdowns, JavaScript errors, and user frustrations. - Highlights: isolate and save key parts of a session replay. For privacy, sessions run in a private mode by default that blocks text and DevTools data, and sanitization rules can be applied globally or at the field level to obscure sensitive inputs. Supported platforms include web, iOS, Android, and React Native. The page references an integrations API but does not detail specific integrations, and lists no retention periods or pricing figures. ### Product Analytics OpenReplay Product Analytics combines product usage metrics with session replay, so each analytics signal can be traced back to the actual user session that produced it. All user sessions are captured without sampling (100% of sessions), and the platform can be used as a cloud service or self-hosted for complete data control. Core capabilities include: - **Conversion funnels** — map multi-step flows and identify where users drop off, including by user segment. - **Heatmaps** — visualize click and interaction distribution across pages. - **Trends** — track usage patterns over time to surface sudden shifts in user behavior. - **Journey analysis** — visualize how users navigate through the product. - **Web analytics** — measure page views, traffic sources, demographics, and engagement. - **Custom events** — track specific user actions or business metrics. Captured data spans user interactions, page views, click patterns, navigation behavior, and custom events. Analytics records link directly to session replays, allowing investigation of drop-offs, feature adoption, onboarding flows, and user segments in the context of the underlying session. Analytics data can be exported to data warehouses, data lakes, and internal tools. For compliance, OpenReplay is SOC 2 Type II compliant, with GDPR, CCPA, and HIPAA compatibility available through self-hosted deployments. The page does not list specific pricing figures, data-retention numbers, or named SDK/framework compatibility for this feature. ### DevTools OpenReplay DevTools is a debugging layer built into the session replay product, presenting technical browser context alongside the visual recording of a user session so issues can be diagnosed without reproduction. The DevTools panel captures and surfaces: - **Console logs and JavaScript errors** with full stack traces and sourcemap support, shown directly within the replay. - **Network activity** — API calls including method, URL, status code, timing, and payload size; failing requests are flagged and response payloads are viewable, with sensitive data sanitized. - **Performance metrics** — CPU usage, memory heap, DOM node count, and frame rate (FPS). - **Application state** — state mutations from supported stores tracked across the session. An X-Ray view correlates technical signals (network failures, performance slowdowns, JavaScript errors) with points of user frustration in the same timeline, linking what the user experienced to the underlying cause. The feature integrates with external monitoring and data tooling including Sentry, Bugsnag, Datadog, and GraphQL. OpenReplay can be run self-hosted or in a managed cloud environment. The page does not list specific SDK or framework names, version numbers, or pricing figures. ### Heatmaps OpenReplay Heatmaps visualize aggregated user interaction data across pages, rendering click maps, scroll maps, and interaction heatmaps across all screen sizes and devices. Because the data derives from captured session activity, each heatmap point can be traced directly to the exact sessions that generated the interaction. Key capabilities include: - **Segmentation filters** — heatmap data can be segmented by user type, source, browser, screen size, or any captured property, allowing behavior comparison across user segments. - **Rage click detection** — identifies areas where users repeatedly click without a response, signaling bugs or unresponsive elements. - **Session replay integration** — clicking a heatmap hotspot opens the underlying user sessions to watch interactions before and after the click. - **Single-page app support** — heatmaps render per route or screen view and handle dynamic content in SPAs. Heatmaps are part of OpenReplay's open-source, self-hostable platform and are available across self-hosted deployments, OpenReplay Dedicated cloud instances, and enterprise self-hosted solutions. The page does not state specific pricing, user limits, data-retention periods, or performance figures. ### Conversion Funnels OpenReplay Funnels is a conversion-analysis feature that visualizes how users progress through multi-step workflows and pinpoints where they drop off. Funnels can be built from autocaptured URLs, clicks, or custom events. Core capabilities include: - **Drop-off analysis**: track how many users continue versus abandon at each step, and jump directly into the session replays for the steps with the most drop-offs. - **Time-to-conversion measurement**: track the time users take to move from one step to the next, with configurable aggregations (average, median, p95). - **Segmentation**: filter funnels by device, country, UTM, referrer, or any custom property. - **Comparison over time**: compare results across periods to assess whether changes are improving conversion. Because funnels are tied to OpenReplay's session data, each step links to the corresponding session replays, letting users see exactly what happened during abandonment rather than inspecting aggregate numbers alone. The feature is available through OpenReplay's deployment options: self-hosted on the user's own infrastructure or as a dedicated cloud instance, with session and analytics data remaining private and under the user's control. The feature page does not state specific pricing figures. ### Co-Browsing OpenReplay Co-Browsing lets support agents view and interact with a user's live session directly inside a web application, without screen-sharing software or additional setup. Agents watch a user's screen in real time to provide assistance during an active session. Capabilities present on the page: - Live session monitoring, including viewing up to four live sessions simultaneously, with tabbed-browsing support to follow users across multiple pages. - Remote control with user consent: agents can click, scroll, or type on the user's behalf. - On-screen annotations to draw on and highlight elements of the user's screen (with user consent). - An in-session video call launched inside the session, without separate Zoom links or phone calls. - "Time travel" to review what led up to the current state of the session. - Real-time console access during the live session to identify errors as they occur. - Optional session recording for training, audit, or review purposes. Privacy and deployment: remote control and annotation require user consent. OpenReplay can be self-hosted for full data control and regulatory compliance, in addition to a cloud offering, and is described as SOC 2 Type II compliant. The page does not specify supported browsers, frameworks, version requirements, or pricing figures. ### Journey Analysis Journey Analysis is an OpenReplay product analytics feature that visualizes the paths users actually take through a product, mapping movement across pages, clicks, and events and surfacing drop-offs, conversions, loops, and dead ends. Unlike funnels, which follow predefined linear steps, Journey Analysis maps all observed paths, including unexpected ones. The feature captures and analyzes: - Page visits, click actions, custom events, and input field interactions - Any page view, click, or custom event configurable as a journey's start or end point - Repeated clicks, loops, and dead ends via loop detection - Comparisons between the paths of successful users and those who drop off Journeys can be segmented and filtered by country, referrer, UTM tags, or custom properties to show how different user segments navigate the product. Every step in a journey is linked to its corresponding session replays, allowing direct inspection of the underlying sessions. Journey Analysis is part of the broader OpenReplay platform and can be deployed fully self-hosted (Enterprise Self-hosted) or on a managed dedicated instance (OpenReplay Dedicated). The page references availability of platform APIs and third-party integrations but does not list specific SDKs, frameworks, or pricing figures for this feature. ### Web Analytics OpenReplay Web Analytics is a built-in, privacy-conscious web analytics layer that runs on top of an existing OpenReplay deployment without requiring additional tags or code changes. It is designed to capture quantitative product and traffic data alongside OpenReplay's session replay, and works for single-page applications by tracking dynamic route changes and interactions. Captured and measured data includes: - Traffic metrics: top pages, referrers, and traffic volume - User navigation flows, journeys, and funnels, including where users drop off - Most engaged users, ranked by number of sessions and interactions - Device, browser, and OS breakdowns for identifying experience issues - Custom events such as button clicks, navigation, and form submissions, with custom properties - Traffic segmentation by referrer or UTM tag A defining capability is the link between quantitative metrics and qualitative replay: any metric can be opened directly into the underlying sessions that produced it, mapping events to their corresponding session replays. It is available as a self-hosted deployment or as a dedicated instance, supports cookie-free tracking, and the platform is noted as SOC 2 Type II compliant. The page does not list specific SDKs, supported framework names, pricing figures, or numerical limits. ### Mobile OpenReplay's mobile session replay records native app sessions on iOS, Android, and React Native, reproducing what users saw and did including screen transitions, taps, swipes, and gestures in pixel-perfect playback. Alongside visual replay, each session captures technical context for debugging: console logs, crash reports, API calls and network requests (with response codes and timing), and performance monitoring data. Sessions can be associated with a user ID to track individual journeys across multiple sessions. Sessions can be filtered by device type, OS version, app version, user ID, encountered errors, and custom events. Custom event tracking lets teams signal in-app moments such as cart additions, feature usage, and conversions. Privacy controls run on-device: input fields and screens containing personal information are automatically masked before any data leaves the device. Capture frequency and event types are configurable, and the SDKs are built for minimal impact on app performance, with optimized CPU, memory, and battery usage. OpenReplay can be self-hosted or run in the cloud, and is SOC 2 Type II compliant. Note: trends, funnels, and journeys analytics are not yet supported for mobile projects and are listed as actively in development. ### Digital Experience OpenReplay's Digital Experience product captures and replays user sessions to help teams understand behavior, surface UX problems, and debug production issues. It combines high-fidelity session replay with technical monitoring and user-behavior analysis in a single platform. Each session records clicks, scrolls, and interactions alongside console logs, network requests, JavaScript errors, performance metrics, and application state (including Redux/Vuex). This lets teams reproduce elusive production bugs that lack clear reproduction steps, while also detecting frustration signals such as rage clicks, hesitations, and confusing navigation. Analysis capabilities include: - Session Replay and DevTools - Co-browsing - Conversion Funnels and Journey Analysis - Heatmaps - Web Analytics and Product Analytics The platform supports single-page applications, progressive web apps, and traditional websites, plus native iOS and Android SDKs for mobile apps. It handles modern web architectures involving asynchronous operations and route transitions. OpenReplay can be self-hosted on-premises, in a private cloud (AWS, GCP, Azure), or run as a dedicated instance, giving teams full control over data storage and processing. Privacy features include input-field masking, automatic PII redaction, and configurable sanitization rules, with GDPR, HIPAA, and SOC 2 Type II compliance. It integrates with issue trackers, monitoring tools, and analytics platforms. The page lists Self-Host and Try Cloud deployment options but states no specific pricing figures. ## Platform ### Spot Spot is a free Chrome extension within the OpenReplay platform for capturing and sharing bug reports. Users record their current browser tab or entire desktop in one click, optionally adding audio narration to explain the issue, and produce a shareable video report. Alongside the video, Spot automatically captures the technical context developers need to reproduce a bug: console logs, network requests, user interactions, and user-agent details. Recordings can be shared via internal or public links, organized in a team workspace, and discussed through context-based comments. Reports can also be shared into Slack, Jira, or Linear. Spot works on Chrome and any Chromium-based browser, including Edge, Brave, and Arc; Firefox and Safari support is planned. Mobile is available as a separate platform feature. Reporters need a free OpenReplay account, while viewers can open public links without an account or extension. Key specifics stated on the page: - Spot is completely free as part of the OpenReplay platform. - Free and open-source; recordings can be self-hosted. - Public share links expire after two days. - Recordings expire after 30 days on the serverless plan; custom expiration on the dedicated plan; no retention limits when self-hosted. - OpenReplay is SOC 2 Type II compliant and has 12k stars on GitHub. ### Integrations & API OpenReplay connects session replays with backend monitoring, frontend state, and external workflow tools through a set of integrations and a REST API. Backend log integrations pull error and log data from Sentry, Datadog, and other monitoring tools directly into session replays, aligning backend events with the exact moment a user experienced an issue. State management plugins connect libraries such as Redux and Vuex to track how application state changes correlate with user experience. Issue reporting and collaboration integrations let users create tickets in Jira and GitHub directly from a session replay, and share specific moments with their team through Slack and other collaboration tools. The REST API exposes sessions, users, events, and live data, enabling integration with data pipelines, internal dashboards, or support workflows. A data warehouse export feature sends behavioral and technical events to an external data warehouse to enrich internal dashboards. - Backend logs: Sentry, Datadog, and other monitoring tools - State management: Redux, Vuex, and similar libraries - Issue tracking and collaboration: Jira, GitHub, Slack - REST API: fetch sessions, users, events, and live data - Data warehouse export: behavioral and technical events API and integration details are documented at docs.openreplay.com (API specs under /en/api/, integrations under /en/integrations/). The page does not state specific endpoints, platform or language requirements, or pricing figures. ## Pricing OpenReplay is offered across cloud and self-hosted options. The cloud has a free tier (1,000 sessions/month, 2 users) and a usage-based Serverless tier priced at $5.95 per 1,000 sessions. The Open-Source plan is free and self-hosted on the user's own infrastructure, with community support via GitHub and Slack; it includes Session Replay, Developer Tools (DevTools), Product Analytics, Co-Browsing, Spot, and an MCP server, with storage, retention, RAM, and vCPUs self-managed and intended for low traffic. The Dedicated plan is fully managed by OpenReplay and starts from $199/mo, billed hourly at $0.276/hr, and can run in OpenReplay's cloud or the customer's (BYOC). It includes all core features with no limits on users, recordings, or retention, plus SSO, custom data retention, 50 regions for data residency, and a dedicated VM or BYOC. Dedicated scales up to 4TB storage, 32GB RAM, and 8 vCPUs, offers an SLA, and includes a 7-day free trial with no credit card required. The Enterprise plan uses custom pricing for self-hosted deployment at scale (TB of daily data, auto-scaling), adding SAML/SCIM, audit logging, custom retention, dedicated support, and AI Agents ("coming soon"). Core capabilities span session replay, developer tools (network, console, errors, performance), product analytics (funnels, heatmaps, journey analysis, web analytics), co-browsing for in-app support, Spot for bug reports, and mobile support. Stopped Dedicated instances incur small disk-based charges, BYOC is billed at a flat monthly rate independent of region, and plan migration is noted as coming soon. ## Comparisons ### OpenReplay vs FullStory OpenReplay is an open-source, self-hostable session replay and product analytics platform, positioned on this page as an alternative to FullStory under the framing "Self-Hosted Session Replay: The Open Source FullStory Alternative." It consolidates session replay, product analytics, and support operations in a single tool, with the option to deploy on a user's own servers to avoid third-party processors and retain control over data ownership, security, and privacy. The platform is SOC 2 Type II compliant and is positioned for regulated industries. Core capabilities documented on the page include: - Session replay with tabbed browsing, Tag & Watch Elements, Canvas/WebGL recording, multi-session view, and live sessions with video calling, remote control, and annotations. - Product analytics: funnels, journey analysis, heatmaps, tables and trends, and performance monitoring. - DevTools for network issue tracking, resource consumption analysis, slowdown detection, and JavaScript error management. - Support operations including co-browsing with real-time guidance. Supported platforms listed are Web (with tabbed browsing), iOS, Android, and React Native. Deployment is available via self-hosting (open source) or cloud plans (shared or dedicated), with pricing described as all-in-one and without hidden costs. The vs-FullStory comparison table positions OpenReplay as offering advanced co-browsing and full DevTools where FullStory is marked "Limited," plus open-source self-hosting that FullStory does not provide. ### OpenReplay vs LogRocket This page positions OpenReplay as an open-source alternative to LogRocket, available either cloud-hosted or self-hosted. Both products combine session replay, product analytics, and performance monitoring; the page compares them feature by feature. OpenReplay's listed capabilities include session replay, DevTools, co-browsing, funnels, heatmaps, journey analysis, web analytics, product analytics, error tracking, alerting, performance monitoring, and data export. An AI feature, "Kai," provides session summaries and pattern detection. Session replay supports web and mobile, including iOS, Android, React Native, tabbed browsing, and Canvas/WebGL capture. Co-browsing features cover live sessions, video calling, remote control, annotations, and multi-session view, plus "Tag & Watch" element targeting. The comparison highlights areas where OpenReplay offers capabilities the page marks as absent or limited in LogRocket: native mobile support (iOS, Android, React Native), co-browsing, self-hosting, an open-source codebase (cited at roughly 12k GitHub stars, available for auditing and contribution), and the Kai AI features. OpenReplay runs in an isolated environment versus LogRocket's shared environment, and OpenReplay is noted as SOC 2 Type II compliant. On pricing, the page lists OpenReplay Dedicated from $199/mo against LogRocket Professional from $350/mo at comparable mid-tier plans. ### OpenReplay vs PostHog OpenReplay positions itself as a self-hosted product analytics alternative to PostHog, combining session replay, product analytics, co-browsing, and digital experience monitoring in a single platform. It can be self-hosted on AWS, Azure, GCP, and Kubernetes, or used via Pay-as-you-Go and Dedicated cloud plans. The page emphasizes simple, predictable pricing with unlimited sessions at a single price, contrasted against PostHog's volume-based per-feature pricing. Capabilities listed on the page include: - Session replay with unified tabbed browsing that follows a user journey across browser tabs - Full-fledged DevTools: network issue tracking, resource analysis, and JavaScript error management - Product analytics: Funnels, Heatmaps, Journey Analysis, Web Analytics, and Tag & Watch Elements - Live collaboration: Live sessions, Video Calling, Remote Control, Annotations, and Multi-Session View - Canvas / WebGL capture, Alerts, Data Export, Feature Flags, and A/B Testing - Coming soon: Retention, Stickiness, Features audit, and Surveys & Feedback Supported platforms include web (with tabbed browsing), iOS, Android, and React Native, plus Integrations & API. On self-hosting, the page claims full access to all core features and responsive community support via Slack, versus PostHog's Docker Compose–only deployment, limited self-host feature access, and no support. Other stated specifics: roughly 12k GitHub stars and SOC 2 Type II compliance. ### OpenReplay vs Hotjar This comparison page positions OpenReplay against Hotjar across session replay, product analytics, and deployment model. OpenReplay captures session replay for web and mobile (iOS, Android, React Native), plus tabbed browsing, tag-and-watch elements, and Canvas/WebGL rendering; Hotjar's session replay is limited to web recordings only. OpenReplay bundles DevTools for inspecting network requests, resource analysis, and JavaScript errors, which Hotjar does not offer. On product analytics, both tools provide funnels, clickmaps, and surveys/feedback. OpenReplay additionally offers path analysis, tables & trends, performance monitoring, alerting, and OmniSearch; Hotjar does not provide these. OpenReplay also includes cobrowsing with live sessions, video calling, remote control, annotations, and multi-session view, whereas Hotjar offers live sessions only. User interviews are marked "Coming Soon" for OpenReplay and absent for Hotjar. Key differentiators: - Deployment: OpenReplay supports self-hosting (open-source) and offers both shared and dedicated cloud plans; Hotjar is cloud-only on a shared environment. - Security: OpenReplay includes single sign-on; Hotjar does not. - Platform coverage: OpenReplay combines web and mobile; Hotjar covers web sessions only. On mid-tier pricing, OpenReplay Dedicated starts at $199/mo (isolated environment) versus Hotjar Scale at $213/mo (shared environment). ## Solutions ### Engineering OpenReplay for engineering teams pairs session replay with developer-focused debugging tooling, letting engineers reproduce bugs from real user sessions without back-and-forth with customers. Each replay is captured with pixel-perfect DOM detail and synchronized with the technical context needed to diagnose issues. Captured and surfaced alongside every session: - Network payloads and failed API calls, shown in the context of the user actions that triggered them - Console logs and JavaScript errors - Application state (including state-manager data) - Performance metrics, crashes, and slowdowns - User interactions and DOM events across browsers The platform provides front-end SDKs for React, Vue, Angular, and other frameworks, and connects to backend logs and state managers. Issue and support workflows integrate with Jira, GitHub, and Zendesk, so engineers can attach session context to tickets. For deployment and data handling, OpenReplay can be self-hosted, supports data masking for sensitive information, allows configurable custom retention rules, and is SOC 2 Type II compliant. The project's GitHub repository is referenced at roughly 12k stars. The page does not list pricing figures or specific performance benchmarks. ### Product Management OpenReplay's product management solution applies its open-source, self-hostable session replay and product analytics platform to feature adoption, onboarding, and conversion workflows. Product teams use captured session data to observe how users navigate a product, identify friction points, and validate the impact of feature changes through before/after comparisons. The page describes the following capabilities: - **Session Replay** — pixel-perfect playback of user sessions to see navigation paths and points of friction. - **Product Analytics** — analysis of the full user journey across the product. - **Funnels** — conversion funnel analysis to locate drop-off points in flows such as signup, checkout, and upgrade. - **Heatmaps** — visualization of interaction patterns on pages. - **Journey Analysis** — tracking of user flows across paths. - **Web Analytics** — event trends and interaction data. - **Co-browsing** — in-app support that allows stepping through a live session alongside the user. - **DevTools** — built-in developer tooling for debugging issues surfaced during replays. Documented use cases include reducing onboarding friction, improving conversion in signup/checkout/upgrade flows, validating feature updates after launch, and supporting collaboration across engineering, design, and support teams. The platform is available as a self-hosted deployment or a cloud version, with mobile support referenced. Integrations and an API are referenced as platform components, but the page does not list specific third-party integrations, metrics, or pricing figures. ### Customer Support OpenReplay's customer support solution applies its open-source, self-hostable session replay platform to help support teams diagnose and resolve user issues. Support agents can watch session replays of user interactions, either live or after the fact, to see exactly what a user experienced rather than relying on written ticket descriptions. The platform surfaces the surrounding session context and the full user journey leading up to a problem. Capabilities highlighted for support workflows include: - **Session replay** of user interactions, available in real time or as recorded playback. - **Co-browsing** to visually guide users through the product, with annotation and secure remote control, requiring no screen sharing or separate downloads. - **Integrated video calling** within the application. - **Developer/debugging tools** for reproducing reported issues. The platform captures user interactions and behavior patterns, errors and slowdowns, rage clicks, and drop-offs during flows such as signup and checkout, helping teams detect unreported issues and resolve complex tickets. It supports web applications and mobile. OpenReplay is SOC 2 Type II compliant. The page positions the product against FullStory, LogRocket, PostHog, and Hotjar. No retention periods, performance specifications, or pricing figures are stated on this page. ### Research & Design OpenReplay's Research & Design solution applies its session replay and behavioral analytics platform to UX research and design validation workflows. It lets design and research teams observe how users actually interact with web and mobile applications, identifying friction points, confusion, and drop-offs without scheduling moderated interviews. Core capabilities include: - **Session Replay** — reconstructed recordings of real user sessions to study interaction patterns and friction. - **Heatmaps** — visual aggregation of where users click and interact on a page. - **Rage click detection** — flags repeated rapid clicks that signal user frustration. - **Hesitation tracking** — surfaces pauses and indecision before drop-offs. - **Journey analysis** — maps the paths users take through product flows. The solution is positioned for usability testing at scale, validating design changes by comparing user behavior before and after, analyzing where users abandon flows, and surfacing accessibility issues through behavioral signals. Captured and measured data covers navigation paths, interface friction points, hesitation and confusion indicators, task-completion behavior, feature engagement, and abandonment events. It supports both web and mobile applications and connects to OpenReplay's broader feature set, including DevTools, co-browsing, product analytics, conversion funnels, and web analytics, plus API access. OpenReplay is open-source (around 12k GitHub stars) and can be used either cloud-hosted or self-hosted. No specific pricing figures or technical specifications are listed on this page. ### Dedicated OpenReplay Dedicated is a fully-managed, single-tenant cloud deployment with complete data isolation — OpenReplay runs the infrastructure, setup, updates, scaling, and maintenance, giving teams the control of self-hosting without operating it themselves. Each customer runs in dedicated infrastructure with a dedicated VPC and full data separation. Pricing tiers (billed hourly at $0.276/hr): - O1 — up to 50,000 sessions/month, from $199/month - O2 — up to 200,000 sessions/month, from $399/month - O3 — up to 500,000 sessions/month, from $799/month Deployment supports AWS, GCP, and Azure, with a bring-your-own-cloud (BYOC) option and regional deployment for data residency. Enterprise security features include SSO, encryption, and custom data-retention policies, and a 7-day free trial is available with no credit card required. Typical use cases include agencies needing multi-client isolation, high-traffic applications, and security-conscious organizations handling sensitive data. ### Enterprise OpenReplay for Enterprise is the self-hosted deployment of OpenReplay's session replay, product analytics, and co-browsing platform, designed to run entirely inside the customer's own infrastructure (VPC). Session data remains on customer-controlled infrastructure, with zero bytes sent to third parties and PII sanitized in the browser before anything is transmitted. The platform is first-party by design and described as ad-blocker resistant. Core capabilities include: - Session Replay synced with network requests, console logs, and errors, plus DevTools integration - Product Analytics: funnels, user journeys, heatmaps, and trends - Co-browsing with live session viewing, screen annotation, and remote control - Web and mobile support Deployment is self-hosted (with a cloud option available separately), installed via Helm (`helm install openreplay -n app`); the current version referenced is v1.27. The backend uses object storage for replays alongside PostgreSQL and ClickHouse databases, and the system is stated to scale to millions of replays. Security and compliance features include SOC 2 Type II (independently audited), GDPR and CCPA compliance, encryption in transit and at rest, SSO/SAML, role-based access controls, multi-tenancy with isolated environments, audit trail logging, and service accounts for automated workflows. Enterprise support adds a dedicated customer success manager, a private Slack/Teams channel, and developer pairing sessions. Pricing is not published on the page. Listed customers include Amazon, NVIDIA, Uber, Mercedes, Deel, and Zscaler. ## Resources ### Session Replay Guide OpenReplay's Session Replay Guide explains how session replay technology works and what it captures. Session replay reconstructs user sessions by recording event data (rather than video) to reduce bandwidth, letting teams watch how users navigate a web application and inspect what happened underneath. The guide enumerates the data session replay captures: - User interactions: clicks, mouse movements, scrolls, and hesitations - DOM mutations during page rendering - JavaScript errors, console logs, and application state - Network activity, including calls to internal and external APIs and their payloads - Performance metrics: Core Web Vitals, load times, and CPU and memory utilization - Frustration signals such as rage clicks, excessive scrolling, and dead clicks - Custom application events, metadata (user IDs, browser versions, country, segments), and cached assets (images, fonts, stylesheets) for historical accuracy For privacy and security, the guide covers data masking (text replaced with asterisks, images replaced with placeholders), selective field tracking to avoid sending sensitive data to servers, GDPR and CCPA compliance support, and self-hosting for full data ownership. It also lists integration categories: error tracking (Sentry), analytics (Google Analytics, Mixpanel, Amplitude), customer support (Intercom, Zendesk), CRM (Salesforce), and bug tracking (JIRA). Mobile and responsive design support is noted as a requirement. The guide reviews four common pricing models: session-based, user-based, team-based, and self-hosted/open-source, without citing specific figures. ## Self-Hosting & Deployment OpenReplay's core platform is open-source and can be self-hosted for full control over data security and privacy. - **Open-Source Edition**: free, self-hosted version with all core features — session replay, DevTools, product analytics, co-browsing, and Spot — backed by 12K+ GitHub stars and community support. - **Enterprise Self-Hosted**: adds SSO/SAML, role-based access control (RBAC), audit trails, SCIM provisioning, dashboards and reports, Model Context Protocol, and dedicated support. Custom pricing via sales. - **Deployment targets**: AWS, Azure, Google Cloud, DigitalOcean, Kubernetes, and Docker (installed via Helm). Step-by-step guides: https://docs.openreplay.com/en/deployment/ ## Key Facts - Founded: 2019 - Legal entity: Asayer, Inc. - Open-source: Yes, core platform on GitHub (openreplay/openreplay), 12K+ stars - Self-hosted: Deployable on AWS, Azure, Google Cloud, DigitalOcean, Kubernetes, or Docker - Compliance: SOC 2 Type II certified; GDPR/CCPA/HIPAA via self-hosting - Notable customers: Amazon, NVIDIA, Uber, Mercedes, ASUS, Deel, Zscaler, LG - Pricing: free open-source self-hosted edition; managed Dedicated cloud from $199/mo ($0.276/hr); Enterprise self-hosted at custom pricing. See https://openreplay.com/pricing for current plans. - Differentiator: open-source session replay, co-browsing and product analytics that is fully self-hostable for total control over data security and privacy - Target customers: companies operating in regulated industries ## Contact - Website: https://openreplay.com - Documentation: https://docs.openreplay.com - GitHub: https://github.com/openreplay/openreplay - Slack: https://slack.openreplay.com - Sales: sales@openreplay.com