Why leatmap?
leatmap is a hosted analytics platform for teams that want first-party data residency in the EU and a strict tracking-plan workflow, without running their own infrastructure. We run the collector and the Postgres database in EU-resident infrastructure; you run the SDK and own the data.
What leatmap optimises for
Section titled “What leatmap optimises for”EU-resident first-party data. Every event lands in EU infrastructure by default. We are the data processor named in your record of processing activities; no events are forwarded to US-based analytics vendors.
Privacy-positive baseline. Do Not Track is honoured by default, consent is gated server-side at the collector (not by the client), the IP is hashed before persistence, and the PII filter strips emails / cards from URLs and form events. Cookieless mode is a one-line config switch.
Bundle size. The browser core is under 5 kB gzip and every opt-in module (vitals, errors, clicks, scroll, engaged time, offline queue, retry) is its own subpath that tree-shakes if you don’t import it.
Strict tracking plan. YAML-defined event schemas, validated at the collector, with TypeScript codegen and a CI breaking-change detector. Bad events go to a dead-letter queue you can inspect and replay.
Latency. The Rust collector ingests at p99 < 5 ms (excluding network). Per-workspace rate limits and monthly quotas keep noisy tenants from starving the rest.
When leatmap is NOT the right fit
Section titled “When leatmap is NOT the right fit”You need session replay today. Replay lands in v1.7. If video evidence of bugs is critical now, pair leatmap with a dedicated replay tool.
You need analysis models out of the box. Funnels, retention, cohorts, and pathfinding land in v1.1+. The current product ships counts, sessions, per-user timelines, and the raw event surface — enough to back a basic dashboard, not yet a full product-analytics suite.
You need ad-spend attribution today. Multi-touch attribution and ad-spend import land in v1.8.
You need air-gap or in-VPC deployment. Available under an Enterprise agreement only — contact us.
Compared to hosted alternatives
Section titled “Compared to hosted alternatives”| Concern | leatmap | US-hosted SaaS analytics |
|---|---|---|
| Data residency | EU by default | US (vendor-controlled) |
| First-party requests | Yes (*.leatmap.com) | Vendor domain (subject to ad blockers) |
| Bundle size | < 5 kB gzip core | 30–80 kB gzip typical |
| Operational overhead | None (we run it) | None (they run it) |
| Pricing model | Per ingested event, Hobby tier free | Per MTU or per event |
What’s stable
Section titled “What’s stable”The public API contract — every SDK export, every HTTP endpoint, every wire field listed under the API reference — is bound by the semver policy. Anything not in that contract is explicitly internal and may change in any release.