Open Replay
Open-source session replay for debugging and UX insights.
Open the official app on openreplay.com
This tool is hosted by its maintainers. Click below to open openreplay.com in a new tab — it's their official demo.
Browse developer tools →What's next with Open Replay?
Choose how you want to get started.
Use it free
Open the official tool or demo — no account needed.
Self-host it
Run the open-source version on your own infrastructure.
What is Open Replay?
OpenReplay is an open-source tool designed for self-hosted session replay and product analytics, enabling teams to monitor user interactions with their applications. Its primary purpose is to capture and analyze how users navigate, click, hesitate, or struggle within digital products, helping identify friction points and troubleshoot issues efficiently. Product managers, developers, and customer support teams use OpenReplay to gain insights into user behavior, measure the impact of product changes, and optimize the user experience. By providing detailed session recordings, network activity, and performance metrics, it addresses the challenge of understanding real-world user experiences without relying on guesswork or limited analytics tools. The tool solves critical problems in product development, such as diagnosing usability issues, tracking conversion rates, and identifying technical errors that hinder user engagement. Its self-hosted model allows organizations to maintain control over data privacy and customization, while features like co-browsing and AI-driven analytics offer deeper context for decision-making. OpenReplay’s emphasis on transparency and flexibility makes it a trusted choice for teams seeking to refine their digital products through data-driven insights.
How it works
OpenReplay is a self-hosted session replay and product analytics platform that records user interactions with web applications. It captures detailed session data, including mouse movements, clicks, and navigation paths, to provide a comprehensive view of user behavior. The tool is designed for product teams, developers, and support staff to identify usability issues, troubleshoot technical problems, and measure the effectiveness of product changes. By replaying user sessions, teams can pinpoint where users struggle, drop off, or encounter errors, enabling targeted improvements. OpenReplay offers session replay to visualize user interactions, error tracking to identify crashes or slowdowns, and network activity analysis to monitor performance. It also includes AI-powered metrics, funnel analysis, heatmaps, and co-browsing features to enhance user understanding.
How to use it
- 1Deploy the OpenReplay server using Docker or a custom setup. 2. Integrate the client SDK into your web application to start recording user sessions. 3. Configure data storage and access permissions for the analytics dashboard. 4. Access recorded sessions and analyze user behavior through the web interface. Practical tips include using Docker for streamlined deployment, ensuring browser compatibility for session recording, and regularly reviewing analytics to prioritize improvements.
What it can do
- session replay
Use cases
Assumptions and limitations
Assumptions
- source: https://github.com/openreplay/openreplay
- license: Elastic-2.0 — free to use
- privacy: Self-hosted — you control your data
Limitations
- Requires technical expertise to set up and maintain a self-hosted server.
- Limited real-time analytics compared to cloud-based alternatives like Hotjar or Mixpanel.
- Network activity tracking may not capture all browser extensions or third-party scripts.
- Data privacy depends on proper configuration, which may demand additional effort.
- Learning curve for advanced features like AI metrics and co-browsing integration.
Understanding the result
Open-source session replay for debugging and UX insights.
Tool details
- Clearly flagged when a network request is needed.
- No account, no sign-up, and no tracking of your content.
- Powered by (MIT).
- Built with
- (openreplay/openreplay)
- License
- MIT
- Runs locally
- No — requires a network request
- Verification
- Not yet verified
- Input
- Query
- Output
- Text
Built with openreplay/openreplay. OpenToolVault provides the discovery and browser interface while crediting the original project maintainers.
- Built with
- License
- MIT
Open-source project
OpenToolVault is an independent directory. We are not affiliated with or endorsed by this project.
References
- / — GitHub Repository
Upstream project · GitHub
- Elastic-2.0 License
Upstream project
Frequently asked
What is OpenReplay used for?
OpenReplay is used for self-hosted session replay and product analytics, enabling teams to track user interactions, identify usability issues, and measure the impact of product changes. It helps organizations understand user behavior, troubleshoot technical problems, and optimize digital experiences through detailed session recordings and analytics.
How does OpenReplay capture user sessions?
OpenReplay uses a client SDK integrated into web applications to record user interactions, including mouse movements, clicks, and navigation paths. Sessions are stored on a self-hosted server, where they can be replayed and analyzed. Network activity and performance metrics are captured alongside user actions to provide contextual insights into user experiences.
How do I integrate OpenReplay into my application?
To integrate OpenReplay, first deploy its server using Docker or a custom setup. Then, add the client SDK to your web application's codebase. Configure the SDK with your server URL and authentication token, and ensure it is included in the pages you want to monitor. Finally, access the analytics dashboard to view and analyze recorded sessions.
How does OpenReplay compare to alternatives like Hotjar or Mixpanel?
OpenReplay differs from Hotjar and Mixpanel by offering self-hosted session replay with full control over data privacy and customization. While Hotjar focuses on heatmaps and user feedback, OpenReplay provides deeper session analytics, including network activity and AI-driven metrics. Mixpanel emphasizes event tracking and funnels, whereas OpenReplay combines session replay with product analytics for holistic insights.
What should I do if sessions are missing data?
Missing data in sessions may result from browser extensions blocking tracking scripts, incomplete SDK integration, or network issues during recording. Verify that the SDK is correctly implemented and that no ad blockers or privacy tools interfere with session capture. Check server logs for errors and ensure the client SDK is properly configured with the correct server URL and authentication token.