Session replay for debugging: it records the DOM, network calls, console output and application state, then plays back the exact sequence that produced an error.
Do not build this — and note that the reason is partly that somebody else's masking defaults are a professional responsibility rather than your afternoon. Replay with the network calls, the console and the application state alongside is what turns a recording into a debugging tool. Doing it faithfully across single-page applications, shadow DOM and lazy content is years of edge cases. WHEN TO KEEP PAYING - You use it to debug real errors, and the state capture is what makes a report reproducible - You would rather the masking rules were maintained by people whose job that is WHEN TO BUILD - Self-host OpenReplay, or build on rrweb. The full shape is under OpenReplay and Hotjar elsewhere in this catalogue WHATEVER YOU CHOOSE, THESE COME FIRST - **Mask by default, reveal by exception.** The opposite ordering guarantees something sensitive is captured on the first day - Password fields never captured under any configuration. Delete the code path rather than making it a setting - **Application state is the sharpest risk here.** A state snapshot routinely contains the whole user object, an access token and whatever a form was holding. Redact by key name and by value match before the snapshot leaves the browser, and read a real captured session by hand to check - Network bodies off by default; headers with authorisation and cookies stripped - Retention in days with a sweeper that deletes, and deletion by user identifier in one command - Log every viewing: who watched whose session. That control is what keeps the tool honest inside your own company THE CHEAPER THING THAT ANSWERS MOST QUESTIONS Error monitoring with breadcrumbs — the recent log lines, requests and clicks before the exception — reproduces most bugs without recording anybody's screen. That is under GlitchTip elsewhere in this catalogue, it is a weekend, and it is a fraction of the privacy exposure. THE ONE-LINE VERSION Try breadcrumbs before replay. If you record, mask by default, redact state, and audit who watches.
What you lose
- Session replay that reconstructs the DOM rather than recording pixels, so it stays small and searchable
- Network requests, console output and Redux state captured alongside the replay
- Automatic privacy masking of inputs, without which the replay becomes a liability
- Error grouping tied to the exact session that produced it
- Storage and retrieval of millions of sessions
If you would rather not build
- PostHog — open-source, replay bundled with analytics
- FullStory — paid, the enterprise alternative
What it costs
as published on their pricing page
| Plan | Billed monthly | Billed yearly | Last read |
|---|---|---|---|
| — | $69/mo | — | — |
Their pricing page is where these came from. Seeing a different price? Tell us.
The escape hatch
open source · no votes, no paid placement
OpenReplay
$0Session replay and DOM recording, self-hosted so the video never leaves your servers.
openreplay/openreplayfree · open source
rrweb
$0The recording and playback library the others are built on, if you want only that part.
rrweb-io/rrwebfree · open source
Why this verdict
our own opinion · changed only by a person
26/100
Verdict no at 26: rrweb does the hard part and the prompt assembles a workable replay, but the risk is not technical. A replay tool captures whatever is on screen, and getting masking wrong once means you have quietly built a database of other people’s personal data.
History
tracked since 9 Aug 2026 · nothing is ever overwritten
Questions about LogRocket
answered from the record above
Is LogRocket free?
No — the plan we track is $69 a month. Team at $69/month billed annually for 10,000 sessions; the price is per session and rises quickly with traffic.
Can you replace LogRocket by building your own?
KEEP IT. The value is the network, the data or the infrastructure. Keep paying. Replacement score 26 out of 100, build time longer than it saves. Read what you lose before you decide.
How much does LogRocket cost?
$69 a month on Team — $828 a year. Recorded 9 Aug 2026.
What do you lose by replacing LogRocket?
Session replay that reconstructs the DOM rather than recording pixels, so it stays small and searchable; Network requests, console output and Redux state captured alongside the replay; Automatic privacy masking of inputs, without which the replay becomes a liability; Error grouping tied to the exact session that produced it; Storage and retrieval of millions of sessions. If any of those carry weight for you, keep paying.
Is there an open-source alternative to LogRocket?
Yes: OpenReplay, rrweb. The prompt on this page is for when you want it your way instead.
Related entries
same category first, most replaced first
Every week, something stops being worth paying for.
New verdicts, prices that moved, entries added. One email a week. Unsubscribe in one click. Nothing is being sent yet — your address is kept here, and the first issue is the first thing it is used for.
free forever · no tracking pixel · stored here, never passed to anyone

