At a glance — how these 3 alternatives compare
Our read on each project's adoption, maintenance activity and commercial-use risk, derived from GitHub signals and SPDX license terms rather than star count alone. Sorted by stars. How we score.
| Project | Adoption | Maintenance | Commercial use |
|---|---|---|---|
| ★ 35,247 · Python | Flagship | Active | Unknown risk No clear SPDX id — treat as all-rights-reserved until verified |
| ★ 19,794 · TypeScript | Mainstream | Active | Low risk Embed in a proprietary product with no copyleft obligation |
| ★ 12,163 · TypeScript | Mainstream | Active | Unknown risk No clear SPDX id — treat as all-rights-reserved until verified |
The alternatives
posthog
🦔 PostHog is an all-in-one developer platform for building successful products. We offer product analytics, web analytics, session replay, error tracking, feature flags, experimentation, surveys, data warehouse, a CDP, and an AI product assistant to help debug your code, ship features faster, and keep all your usage and customer data in one stack.
PostHog/posthog Updated 2026-07-01 rrweb
record and replay the web
rrweb-io/rrweb Updated 2026-06-27 openreplay
Session replay, cobrowsing and product analytics you can self-host. Best for reproducing issues and iterating on your product.
openreplay/openreplay Updated 2026-06-30 Editor's take
Yusuke Morinaga · last revisited
Session replay you host yourself trades a subscription for a storage-and-retention problem nobody mentions up front.
When people compare Hotjar alternatives they line up heatmaps and recordings feature-by-feature. Useful, but it misses the thing that actually decides whether self-hosting works: a session recorder is a firehose that writes to disk forever, and Hotjar absorbs that cost for you. Move it in-house and storage planning becomes the project, not the install.
The sampling decision you make on day one and regret on day thirty. Recording 100% of sessions on a high-traffic site is expensive in disk and retention. So the first real choice with any OSS option is sampling rate and how long you keep recordings — set it deliberately, or the volume decides for you. This is also the cleanest reason a low-traffic product or internal tool is a better self-hosting fit than a busy consumer site.
PostHog — the one I’d default to. PostHog (35.1k stars) bundles session replay with product analytics, feature flags, and surveys. A licensing point worth getting right, since it’s widely misreported: the main repo is MIT (Expat), with an ee/ directory under a separate enterprise license — if you need a strictly FOSS build, use the posthog-foss mirror. What makes it the safe pick: the in-recording feedback widgets — polls and surveys, the Hotjar feature people actually miss — are more mature here than elsewhere, and analytics lives in the same stack. If you want one platform to replace Hotjar and your analytics, this is it.
OpenReplay — the pick when the use case is debugging, not marketing. OpenReplay (12.1k, source-available) records with DevTools-level detail and co-browsing. If your team watches sessions to reproduce bugs rather than study funnels, its depth is the draw — accepting that its survey/feedback side is weaker.
rrweb — only if you’re building. rrweb (19.7k, MIT) is the recording library under many of these tools, not a product. Reach for it only if you’re embedding replay into your own software.
So the decision reduces to one sum nobody runs early enough: a week of your real session volume, times your intended retention, priced as disk. Comfortable number — PostHog for an all-in-one stack, OpenReplay for debugging depth. Frightening number — you’ve just learned your sampling rate, and maybe that Hotjar’s hosted bill was buying something real. One thing the spreadsheet won’t flag: swapping recording providers changes how visitor data is handled, so the privacy policy is part of the migration, not an afterthought.
Comparison notes
PostHog rolls session recordings, heatmaps, and product analytics into one self-hostable package (source-available core, AGPL), while OpenReplay focuses on recording and co-browsing with DevTools-level detail; underneath many of these sits rrweb, the open-source library that actually captures the sessions. On feedback, Hotjar's in-recording polls and surveys exist in PostHog but are less developed in OpenReplay. Whichever you pick, plan ahead for the data: recording sessions on a high-traffic site eats storage, so retention policy is something to decide before you turn it on, not after.
Migration tips
- Download existing Hotjar recordings before migrating — recordings cannot be transferred but key clips can be saved
- Install PostHog or OpenReplay alongside Hotjar before full migration to collect parallel recordings for comparison
- Recreate Hotjar feedback widgets and surveys in your OSS tool's equivalent feature
- Configure session recording sampling rate in your OSS tool — recording 100% of sessions is storage-intensive for high-traffic sites
- Update your privacy policy to reflect the new session recording provider and any differences in data handling
Which alternative should you pick?
Replacing Hotjar isn't a single call — it's a trade between license terms, team size, and how much early-stage roughness you can absorb. The 3 projects above split along those lines:
- You want the most active community and the lowest risk of abandonment → posthog. 35,247★ — the largest user base in this list, which usually means more StackOverflow answers, more plugins, and more deployment runbooks online.
- You ship commercial software and need to ship modified code without releasing source → rrweb. MIT licensed — modify and embed without copyleft obligations.
License & commercial-use notes
With a Hotjar replacement the license usually decides more than the feature list — whether you can modify it, ship it inside a product, or host it as a service. The 3 projects here fall into:
- Permissive (rrweb) — MIT / Apache / BSD / ISC — modify and embed inside a commercial product with no copyleft obligation. The safest bucket for shipping in a proprietary codebase.
- Unverified license (posthog, openreplay) — GitHub returned no clear SPDX id. Treat as all-rights-reserved until you read the project's LICENSE file directly — do not assume commercial use is permitted.
License fields come from the GitHub API's SPDX classification and can lag a relicense. The repository linked on each card is authoritative — confirm its LICENSE file before any license-sensitive deployment.
Maintenance health of these 3 projects
Of the 3 projects listed, 3 shipped at least one commit in the last 12 months. See how we rank for the full criteria and our self-hosting cost reality check, which apply across every comparison on this site.
Frequently asked questions
How do these 3 alternatives compare on maintenance health?
3 of 3 have shipped a commit in the last 12 months. At least one project here has 5,000+ GitHub stars, which usually correlates with sustained maintainership. Always check the last-pushed date in the cards above and read the latest 5 closed issues — those two signals together catch 80% of abandoned-project cases.
How this page was compiled
- Repository facts (stars, license, language, last commit) come straight from the GitHub public API and are linked on each card as the primary source.
- Editorial analysis is drafted from Hotjar's use case and the alternatives' repository metadata, then reviewed by hand.
- Maintenance signal: 3 of 3 projects shipped a commit in the last 12 months as of the latest rebuild (most recent activity: ).
- Last editorial review: by Yusuke Morinaga.
- Spotted an error? Email [email protected] with the page URL (subject prefix
[correction]) — we ship corrections within 14 days.