FullStory
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.
Do not write a session recorder from scratch. Use rrweb, and be careful about what you capture. STACK - rrweb in the browser, your own endpoint, object storage for the event files RECORDING - Start rrweb with input masking on by default and an allow list of fields, never a deny list - Block any element carrying a data-private attribute - Cap a session at a fixed number of events and a fixed duration, then stop UPLOAD - Batch events and post on an interval and on page hide, with sendBeacon - Compress before sending; these payloads are large STORAGE - One object per session in cheap object storage, one database row of metadata - A retention job that actually deletes, and a documented number of days PLAYBACK - rrweb-player behind an authenticated page WHAT YOU MUST DECIDE BEFORE ANY OF THIS - Your lawful basis for recording, what consent you need, and how a person asks for their session to be deleted Include the recorder config, the endpoint, the retention job and a README on the privacy defaults.
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
$0Self-hosted session replay with the privacy controls already built.
openreplay/openreplayfree · open source
rrweb
$0The 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
Nothing recorded yet. This chart fills in once the page has visitors, votes or prompt copies — it will not draw a flat line to look busy.
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
Every week, something stops being worth paying for.
New verdicts, prices that moved, entries added. One email a week. Unsubscribe in one click.
free forever · no tracking pixel · every prompt stays free on the site