
OpenReplay
8.5#4 in heatmap and session replay toolsFree planFree planAndroidiOSWebAPI
Visit

| Fact | OpenReplay | Rejourney |
|---|---|---|
| Privacy controls | Private mode obscures text and DevTools data by default, and field-level sanitization can prevent sensitive data capture. | The privacy policy says the SDK automatically scrubs password fields, sensitive text inputs, camera views, credit card entry fields, and hashes user IDs; customers remain responsible for checking their configuration. |
| Security | OpenReplay states that its cloud service is SOC 2 Type II compliant and maintains administrative, physical and technical safeguards. | The DPA states that data is encrypted in transit using TLS 1.3 and at rest using AES-256, with multi-factor authentication and role-based access permissions. |
| Session replay | It reconstructs users’ visual experiences, including DOM structure, clicks, scrolls, inputs and page changes. | Web session replay connects browser behavior with funnels, events, network requests, console context, and route changes. |
| Support | The Open-Source plan provides community support through GitHub and Slack, while Enterprise includes dedicated support and onboarding architecture services. | The Growth plan lists priority support and dedicated hardware, while Enterprise lists a dedicated support team and custom SLA. |
OpenReplay suits product and engineering teams that need to review user sessions alongside analytics or technical context. It also fits teams seeking self-hosted deployment or a managed Dedicated instance.
Rejourney may suit teams seeking product analytics and session evidence across web and mobile, from indie teams through enterprise. It also has a self-hosted option for teams that want to deploy the stack on a server.