Replayowl vs OpenReplay
Both are open source session replay you can host yourself. OpenReplay is a larger platform with more features. Replayowl is smaller and built to deploy as a single Cloudflare Worker.
Facts about other products on this page were last checked against their own websites on . Prices and limits change; follow the source links before you decide.
| OpenReplay | Replayowl | |
|---|---|---|
| Scope | Session replay, DevTools, co-browsing, funnels, heatmaps, journeys, web analytics, mobile | Web session replay with console errors and search |
| Self-hosting | Free | Free |
| Hosted option | Dedicated from $199 per month, billed hourly at $0.276 per hour | None |
| License | AGPLv3 by default, some folders MIT, ee/ folder separately licensed |
AGPL-3.0 |
| Runs on | Your infrastructure | A Cloudflare Worker with R2 and D1, or Node with Postgres |
| Mobile apps | Yes | No |
| Heatmaps | Yes | No |
Sources: OpenReplay pricing, OpenReplay license.
Pick OpenReplay if
You need mobile replay, co-browsing, DevTools or product analytics alongside replay, and you have the capacity to run a larger platform.
Pick Replayowl if
You want the smallest thing that gives you high-quality web replays on your own infrastructure. A Replayowl deployment is one Worker, one bucket and one database, with no containers to keep running. The recorder is about 8 KB gzipped with no dependencies.
Compare replay quality in the live demo, and see what Replayowl does not do before deciding.