Self-host replay, browser logs, feedback, and backend performance without paying by sessions or seats.
“Unlimited” means TraceUX does not meter sessions. Your server capacity, storage, and retention settings still apply.
LogRocket pairs session replay with deep frontend observability. TraceUX covers the most useful replay-to-debug loop, then adds feedback, support, announcements, and backend performance in a smaller self-hosted package.
Developer-led web teams that want replay and diagnostic context without sending user sessions to a hosted observability platform.
A practical comparison of the jobs teams commonly move to TraceUX.
| In LogRocket | In TraceUX |
|---|---|
| Session replay | rrweb replay with session activity and multi-page navigation |
| Console logs | Browser and backend service logs in one searchable stream |
| Performance monitoring | Backend endpoint latency with p50, p95, and p99 percentiles |
| User context | Visitor identity, page paths, feedback, and ticket context attached to sessions |
| Usage-based SaaS plans | No vendor session cap; capacity follows your own server and retention choices |
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.
TraceUX can collect browser logs and custom events, but it does not mirror LogRocket’s full network request and application-state inspection. Compare the debugging detail you rely on before switching.
Yes. Services can send logs and endpoint timings to TraceUX. The dashboard reports backend p50, p95, and p99 latency alongside the frontend session context.