Replace session-limited hosted recordings with replay and user feedback that stay on your infrastructure.
“Unlimited” means TraceUX does not meter sessions. Your server capacity, storage, and retention settings still apply.
Mouseflow centers on heatmaps, recordings, funnels, and form analytics. TraceUX is a better match when replay data ownership and an integrated feedback-and-support workflow matter more than aggregate heatmap reports.
Web teams that use Mouseflow mainly for recordings and feedback, and can trade heatmaps and form analytics for self-hosting.
A practical comparison of the jobs teams commonly move to TraceUX.
| In Mouseflow | In TraceUX |
|---|---|
| Session recordings | DOM-event replays stored and retained on your own server |
| Feedback campaigns | Good/Bad, stars, NPS-style scales, and written feedback |
| Visitor details | Identity, page navigation, activity markers, and related support tickets |
| Alerts and integrations | Slack Webhooks for tickets, logs, custom events, and system health |
| Monthly recording allowance | No vendor-defined recording allowance or automatic overage invoice |
TraceUX does not require a hosted account, charge per seat, or stop recording at a monthly vendor quota. You provide the Linux host and storage, and you decide how long to retain sessions. That makes the tradeoff explicit: predictable infrastructure you operate instead of a usage-based SaaS bill.
Run both trackers briefly, verify your data, then retire the old one.
Install the single Go binary on a Linux host. SQLite is embedded, so there is no separate database service to provision.
NPM (Recommended): install @trace-ux/tracker and connect your site key and server URL. Script tags and Google Tag Manager are alternatives for sites without a bundler. Keep the old tracker temporarily while you validate new recordings.
Mask sensitive fields, choose your retention window, and confirm that sessions, feedback, and logs arrive as expected.
Once TraceUX is working in production, remove the previous vendor snippet so each visit is recorded only once.
TraceUX has no required SaaS subscription, per-seat charge, or vendor-enforced session quota when you self-host it. Your practical capacity depends on the server, storage, retention, and recording settings you choose, so infrastructure is not literally cost-free.
On the TraceUX server and storage you operate. You choose the collection endpoint, retention policy, and masking rules instead of sending recordings to a hosted analytics vendor.
No. If your decisions depend on heatmaps or field-by-field form reports, keep Mouseflow or pair TraceUX with a dedicated tool. TraceUX focuses on individual sessions and direct user communication.
TraceUX does not meter sessions or create overage invoices. Traffic spikes still consume CPU, memory, and storage on your server, so monitor system health and choose retention settings that fit the host.