Relyv.ai vs Hotjar
Looking for a Hotjar alternative or replacement? Relyv.ai is the AI-native session replay platform engineering teams pick when Hotjar's marketing-first heatmaps stop short of the technical context developers need.
They capture pixels. Relyv captures every layer of the same session.
| Feature |  | Hotjar |
|---|---|---|
| Replay ArchitecturePixel-accurate at any zoom; survives CSS changes; searchable text. | DOM serialization | Video / image |
| AI Session SummaryCloud inference for SDK customers; on-device (Chrome Gemini Nano) when the Relyv extension is installed. | Every session, AI-powered | Manual / not included |
| Auto Bug Reports → TicketsLinear, Jira, GitHub, GitLab, Asana, ClickUp, Trello, Notion, Slack, Teams, Discord, HubSpot, Salesforce, email — pre-filled with AI repro + evidence. | One-click to 14 trackers | Slack export only |
| Playwright Test GenerationReplay → spec file in one click. Stable testId > role > text > css selectors. | Yes | No |
| Console Logs CaptureEvery console call + uncaught + unhandledrejection synced to timeline. | log/info/warn/error/debug + traces | No |
| Network Capture5 protocols vs zero. Full request/response timeline alongside replay. | Fetch + XHR + WebSocket + SSE + Beacon | No |
| Mobile Touch + Pinch + Virtual KeyboardPinch-zoom state, pen pressure, visualViewport keyboard tracking. High-fidelity mobile-web capture; native iOS/Android SDKs in alpha. | PointerEvent w/ pressure + tilt | Generic touch events |
| Video / Audio Playback Trackingplay/pause/seek/ended/PiP/fullscreen — content engagement visible in replay. | 12 subtypes per element | No |
| Offline + Service Worker + Batteryonline/offline transitions, SW state, battery level — explains mobile session drops. | Full PWA lifecycle | No |
| Frustration DetectionFrustration-score MLP (12→16→4) weighted across 4 signal types. | Rage + dead + scroll-thrash + error-burst, scored | Click density only |
| Cross-Session HeatmapsBacked by relyv_workspace_heatmap_events Mongo collection + canvas additive blending. | Workspace-aggregated click + scroll | Per-page click only |
| Global Cmd-K SearchMongo $text index + reciprocal-rank fusion across every saved session. | Hybrid lexical + semantic | Page-level only |
| Marketing Tag ValidatorValidates pixel payloads + Consent Mode v2 state in real time. | GA4 / Meta / Segment / GTM / Mixpanel / Amplitude live QA + Adobe Launch tag + Zapier app | No |
| Stage vs Prod Side-by-SideCatch regressions before they ship — the only tool that diffs. | Visual + DOM + network diff | No |
| Self-Contained .html ExportOpen in any browser, no account, no internet — every export is a viral install. | Single offline file w/ embedded viewer | No |
| Surveys + Feedback WidgetSurveys microservice + collab comments + AI summary of responses. | In-session + shadow-DOM | In-session only |
| Flows + FunnelsStep picker (URL / click / custom-event / state) + ComputeFunnel with drop-off session sample. Plus scheduled flow runs. | Funnel builder + Headless-Chrome scheduled flows | Basic funnels |
| CRM IntegrationsTicket-creating CRM bridges — full OAuth, native API surface. | HubSpot + Salesforce + 12 others | HubSpot only |
| MCP-Native (Claude / Cursor / Continue)Agents call get_session_intelligence — unique. No competitor offers this. | Yes | No |
| PII MaskingSDK redacts 12 PII categories + Luhn-validated card numbers in the browser; the Relyv browser extension adds an ONNX/WebGPU GLiNER deep-scan in an offscreen document. | On-device Luhn + 12-category regex (SDK); + ONNX/WebGPU GLiNER with the Relyv extension | Server-side |
| Identify APIsdk/src/index.ts: identify(UserIdentity) with 1/sec rate limit. | Rate-limited, traits + email + id | Basic identify |
| Capture Event TypesWire-event manifest covers DOM, network, console, media, env, engagement, security, a11y. | 38 distinct events | ~6 (click/scroll/page-view/error/etc.) |
| Browser SDK SizeEquivalent footprint, dramatically richer capture surface. | ~119 kB ESM / 47 kB gzipped | ~110 kB |
| Self-Host / Data ResidencyGDPR + HIPAA without contract gymnastics. | EU + US regions; on-prem available | US only |
| Pricing ModelScales with data, not headcount. | Usage-based + free 1,000 sessions/mo | Per-seat + 35 daily sessions free |
Comparison based on publicly available product documentation, pricing pages, and feature lists from hotjar.com as of 19 May 2026. Relyv capabilities cited above are implemented in the public Relyv SDK + Angular viewer + Go microservices stack and verifiable via the open-source viewer at github.com/relyv-ai/relyv. Feature sets may change over time. Visit Hotjar
The Relyv Advantage
Engineering-grade replay, not just a heatmap
Hotjar shows you where users click. Relyv shows you why something broke — full DOM + network + console + 38 distinct event types per session, including stack traces, request bodies, and console errors timestamped to the exact frame.
AI that already wrote the bug report
Intent classification, frustration scoring (rage + dead + scroll-thrash + error-burst MLP), session summaries, and one-click Linear / Jira / GitHub tickets pre-filled with AI repro steps. Cloud inference on Relyv's own infrastructure for SDK customers (no per-token billing surfaced); on-device via ONNX/WebGPU when the Relyv extension is installed.
Mobile and PWA fidelity Hotjar gives up on
PointerEvent capture with pressure + tilt for pen input. Pinch-zoom state machine. Virtual-keyboard show/hide via visualViewport. Service Worker lifecycle + battery + offline transitions. High-fidelity mobile-web replay today; native iOS/Android SDKs in alpha for teams who need them.
Privacy that compiles into the bundle
PII redaction runs on-device — 12-category regex + Luhn in the SDK; ONNX/WebGPU GLiNER deep-scan when the Relyv extension is installed — before bytes leave the browser. AES-256-GCM session sealing. EU + US data residency. Compliance is an architecture, not a setting.
MCP-native — your AI agent can query sessions
Claude, Cursor, and Continue can call get_session_intelligence as a tool, ask "what frustrated the user in session X around timestamp Y", and get structured intent / frustration / outcome data back. No other replay tool does this.
Self-contained .html export — the K-factor moat
Every session can export as a single offline HTML file with the viewer embedded inline. Open it in any browser without an account, without internet. Every shared file is a viral install — competitors lock recordings behind cloud accounts.
A Closer Look
DOM replay vs. video recording
Hotjar captures pixels as a video stream. That breaks when your site's layout changes, can't be searched, and balloons in size. Relyv serializes the live DOM + every mutation, replaying it pixel-accurate at any zoom level, with searchable text content and a working DOM inspector inside the viewer.
Why technical context matters
A marketing manager needs to know a user didn't click. An engineer needs to know why — a 401 Unauthorized? A failed bundle load? A JS exception in a third-party script? Relyv shows both, and the AI bug report cites the exact log line that caused the friction.
Mobile is 60% of your traffic
Hotjar's mobile recording quietly drops gesture state — pinch-zoom looks like an unexplained jump, virtual-keyboard pushes content off-screen with no marker, pen pressure on stylus apps is invisible. Relyv's Wave-7 capture surface (PointerEvent + visualViewport + pinch-recorder) ships high-fidelity mobile-web capture today, with native iOS / Android SDKs in alpha for teams that need a native install path. Every interaction is queryable, in any case.
Workspace-aggregated heatmaps that aren't a separate product
Hotjar charges separately for heatmaps. Relyv's heatmaps run on the same data plane as replay — click into any hotspot to watch the actual session, with AI-labelled frustration cause and full network context attached.
Integration depth — 14 trackers, not 1
Relyv ships native OAuth flows for Linear, Jira, GitHub, GitLab, Asana, ClickUp, Trello, Notion, Slack, Teams, Discord, HubSpot, Salesforce, and email — every ticket is pre-filled with the AI-written repro steps, the network failures, the environment, and a deep link back to the exact replay frame. Hotjar's integrations are mostly Slack-and-Zapier hops with no semantic payload.
On-device AI vs. cloud-only AI
Hotjar AI features run cloud-side, billing you per analysis and shipping your session data to a third-party LLM. With the Relyv browser extension installed, the intent classifier (bge-small) and PII deep-scan (GLiNER) run on-device in an offscreen document via onnxruntime-web with WebGPU acceleration — zero cloud GPU cost, zero data leaving the browser for AI inference. SDK-only customers get the Tier-1 regex + Luhn PII shield in the browser plus cloud inference (Relyv's own infrastructure, not a third-party LLM) for AI session summaries — still EU + US data residency, no per-token billing surfaced to the customer.
Common Questions
Is Relyv.ai a true Hotjar alternative for engineering teams?
Yes. Hotjar was designed for marketers — it surfaces *where* users click. Relyv.ai is designed for engineers — it surfaces *why* something broke, with synced network requests, console errors, source-mapped stack traces, and an AI-written root-cause summary attached to every session.
Is Relyv as easy to install as Hotjar?
Yes. A single <script> tag or `npm install @relyv/sdk` gets you started. Zero configuration captures sessions, heatmaps, console + network state, and AI insights from the first replay.
Can I import my historical Hotjar data?
Hotjar stores recordings as compressed video, which can't be re-rendered as a structured DOM replay. Our SDK runs side-by-side with Hotjar's during a migration window so you build a full Relyv.ai history without losing Hotjar coverage. Most teams sunset Hotjar after 30 days.
How does Relyv.ai's pricing compare to Hotjar?
Hotjar charges by daily session quota and seat count. Relyv.ai is usage-based on captured sessions and AI calls, with a free tier of 1,000 sessions/month and no per-seat surcharge — so adding 50 engineers costs nothing extra.
Does Relyv.ai capture frustration signals like rage clicks?
Yes — and goes further. Rage clicks, dead clicks, scroll-back loops, and form-abandonment are auto-detected, then labelled with an AI-written cause ("clicked a button with stale onClick handler from a prior render"), not just plotted on a heatmap.
Is Relyv.ai GDPR + CCPA compliant?
Yes. PII is masked in-browser via 12-category regex + Luhn validation in the SDK (plus ONNX/WebGPU GLiNER deep-scan when the Relyv extension is installed) before any data leaves the browser — credit cards, emails, SSNs, and custom regexes never reach our servers. EU + US data residency available; SOC 2 Type II in progress; full DPA on request.
Does Relyv.ai integrate with my bug tracker the way Hotjar does?
Yes, and bi-directionally. One click pushes a Relyv.ai replay into Linear, Jira, GitHub, GitLab, Asana, ClickUp, Trello, or Notion with the AI-written repro, console + network evidence, and a Playwright test attached. Status changes flow back into Relyv.ai. Hotjar offers one-way link export only.
Does Relyv.ai work with my CRM?
Yes. Native HubSpot and Salesforce integrations create tickets / Cases directly from a session replay, with the AI-drafted bug report, the failing network calls, the AI-summarised user intent, and a deep link back to the replay frame. Hotjar has a HubSpot connector but no Salesforce, and neither pre-fills with technical evidence.
Does Relyv.ai work as well on mobile as Hotjar?
Better. Hotjar's mobile recording captures generic touch events. Relyv captures the full Pointer Events API (pressure + tilt + pointerType), a dedicated pinch-zoom state machine, virtual-keyboard show/hide via the visualViewport API, plus battery state, Service Worker lifecycle, and online/offline transitions. Mobile sessions replay with the same fidelity as desktop.
How does Relyv compare to Hotjar on video + audio playback in sessions?
Hotjar can't capture media-playback state — your replay shows a paused video that the user was actually scrubbing. Relyv's media-recorder emits 12 subtypes per `<video>` and `<audio>` element (play, pause, seek, ended, rate-change, volume, picture-in-picture, fullscreen, error), so content-team replays match what the user actually experienced.
Can my AI agent (Claude, Cursor) query Relyv sessions like it can't query Hotjar?
Yes. Relyv is MCP-native: agents can call get_session_intelligence as a tool, ask "what frustrated the user in session X around timestamp Y", and receive structured intent / frustration / outcome data back. No other replay tool — including Hotjar — exposes session intelligence over MCP.
Can I send a Relyv recording to someone without making them sign up?
Yes. Every recording can export as a single self-contained .html file with the viewer embedded inline. The recipient opens it in any browser — offline, no account, no internet — and replays the full session including DOM, network, console, AI summary. Hotjar requires the recipient to have a Hotjar account to view anything.
Related from Relyv.ai
Ready to upgrade your visibility?
Root-cause errors in seconds, not hours — with the replay platform built AI-first.