Who Tracabit is for.
Four kinds of teams get the most out of it today, and a short list of needs we can't meet yet.
SaaS product teams
You want to know where signups stall and which errors cost you customers, without stitching three tools together.
- Funnels built from the pageviews you already send
- Crash reports next to the traffic that triggered them
- A daily digest so nobody has to remember to check
Developers and solo founders
You want numbers for a side project or a first launch without a sales call, a consent banner rebuild, or a big bill.
- Free for 3,000 events a month, $8 for 50,000
- One script tag, or the tracabit package on npm
- A JSON API for your own scripts and dashboards
Teams building with coding agents
Your agent writes the code; you want it to check the numbers too, instead of you pasting screenshots into chat.
- A built-in MCP server with six tools
- Works with Claude Code, Cursor and any MCP client
- A secret key per project, so agents only see what you allow
Sites cutting down on tracking
You want useful traffic numbers while collecting less about each visitor.
- No cookies, and no IP addresses stored
- Country-level location only
- Retention you set per project
Not a fit yet if you need
Better to know now than after you've installed it. If one of these is close to a deal-breaker, tell us.
- Health data
- We don't sign BAAs, so Tracabit isn't for protected health information.
- Audit reports
- There's no SOC 2 or ISO 27001 report yet.
- Self-hosting
- Tracabit only runs on our infrastructure for now.
- Team seats and SSO
- Each account belongs to one person.
- Session replay and heatmaps
- Tracabit records events, not screen recordings.
- A cookie-banner guarantee
- The tracker stores a session ID and a device hash. Whether you need consent depends on your visitors' location.
Try it on your own site. Free for 3,000 events a month.
Start free