FullStory

fullstory.comcontributed by Samuele Ongaro

KEEP IT

The value is the network, the data or the infrastructure. Keep paying.

Session replay and digital experience analytics: it reconstructs what a visitor saw and did, then lets you search across those sessions for rage clicks, dead clicks and errors.

Promptfree, for everyone, and the only version there is
Do not build this — and read the reason, because it is not only technical.

**Replay that reconstructs a page faithfully** — single-page applications, shadow DOM, lazy content, dynamic styles — is years of edge cases. But the sharper point is what a session recording is: a record of an individual person using your product, including what they typed. Deployed carelessly, it becomes a database of things people never meant to give you.

WHEN TO KEEP PAYING
- You genuinely need replay, and you would rather the masking defaults were somebody else's professional responsibility

WHEN TO BUILD
- Self-host OpenReplay or build on rrweb, which is covered under OpenReplay and Hotjar elsewhere in this catalogue

WHATEVER YOU DO, 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. Remove the code path rather than making it a setting
- Payment fields and anything marked sensitive replaced in the browser, before the data leaves. Masking on the server is too late
- Record a test page containing a password, a card number and an address, then read the stored stream by hand. Do that every release, not once
- Retention in days, enforced by a sweeper that actually deletes, and deletion by user identifier in one command
- **Log every viewing**: who watched whose session. That log is what keeps the tool honest inside your own company, and it is the control nobody builds
- Write all of it in your privacy notice, in plain words

THE CHEAPER ANSWER THAT USUALLY WORKS
Most questions people open a replay for are answered by two lists: rage clicks and dead clicks, with the element and the page. Those need no recording at all — a few kilobytes of script, an events table, and a ranked list. Build that first and see how many of your questions it answers before recording anybody.

THE ONE-LINE VERSION
Try the rage-click list before the replay. If you must record, mask by default and audit who watches.

What you lose

  • A DOM-mutation recorder that survives single-page apps, canvas, iframes, shadow DOM and lazy-loaded fonts
  • Automatic privacy masking of inputs and text, which is a legal requirement rather than a nicety
  • Search across sessions by behaviour, not by user id
  • The storage and playback infrastructure for millions of session recordings

If you would rather not build

  • PostHog, which bundles replay and is self-hostable

The escape hatch

open source · no votes, no paid placement

OpenReplay

$0

Self-hosted session replay with the privacy controls already built.

openreplay/openreplayfree · open source

rrweb

$0

The recording and playback library itself; everything else is plumbing.

rrweb-io/rrwebfree · open source

Why this verdict

our own opinion · changed only by a person

22/100

Verdict no at 22. rrweb makes the recording feasible; the storage, the search and above all the privacy obligations are what you are really paying for.

History

tracked since 10 Aug 2026 · nothing is ever overwritten

Interest · last 30 dayspeak 1/day
views0130 Aug4 Sept9 Sept14 Sept19 Sept24 Sept28 Sept
— views— prompt copies none yet— votes none yet

Questions about FullStory

answered from the record above

Is FullStory free?

Quoted per account on session volume; no monthly price is published, so none is recorded here.

Can you replace FullStory by building your own?

KEEP IT. The value is the network, the data or the infrastructure. Keep paying. Replacement score 22 out of 100, build time longer than it saves. Read what you lose before you decide.

How much does FullStory cost?

FullStory has no public headline price. The tier we track is the entry plan.

What do you lose by replacing FullStory?

A DOM-mutation recorder that survives single-page apps, canvas, iframes, shadow DOM and lazy-loaded fonts; Automatic privacy masking of inputs and text, which is a legal requirement rather than a nicety; Search across sessions by behaviour, not by user id; The storage and playback infrastructure for millions of session recordings. If any of those carry weight for you, keep paying.

Is there an open-source alternative to FullStory?

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

All 36 in Analytics

Not sending yet

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

Esc