Compare
Same lightness, a different question. Umami is the most widely deployed open-source analytics tool: MIT licensed, light, easy to install. Some of our tracker ideas come from it — the daily-salted cookie-free visitor hash, for one. Where we diverge is not the feature list; it is the question the product answers.
| Capability | Umami | Vitrus |
|---|---|---|
| Cookie-free, no consent banner | ✓ | ✓ |
| Self-hostable | MIT, needs Postgres | Apache-2.0, embedded DB |
| Ordered funnels | ✓ | ✓ |
| Retention / cohorts | ✓ | via identify() |
| Core Web Vitals | ✓ | ✓ |
| JavaScript error tracking | ✓ | ✓ |
| Session replay | ✓ | opt-in, all text masked by default |
| User journeys / path analysis | ✓ | ✓ |
| Named goals with targets | ✓ | ✓ |
| Heatmaps | ✓ | — |
| Revenue tracking | ✓ | per currency, never converted |
| Attribution reports | ✓ | — |
| Tracked links and pixels (email, off-site) | ✓ | — |
| Custom dashboards (boards) | ✓ | — |
| Public stats API with API keys | ✓ | read-only keys |
| Proactive digest (arrives unasked) | — | ✓ |
| AI referral ↔ AI crawler split | — | ✓ |
| Clickable query behind every number | — | ✓ |
| Unprovable AI sentences auto-dropped | — | ✓ |
| Local LLM / bring your own key | — | ✓ |
| Per-site strict privacy mode | — | ✓ |
Features we don't have are shown as “—”. A comparison that hides its own gaps would contradict the one thing this product claims.
If you want breadth — heatmaps, attribution, tracked links and pixels, custom boards — Umami is ahead of us and will stay ahead, because we deliberately do not build most of it (ad-platform attribution is permanently out of scope). Both of us now record sessions; ours is newer and deliberately narrower — off by default, every text node and input masked. They also have far more maturity and a much larger community.
When the correctness of the AI summary matters. Umami has AI too; the difference is that our output is bound to a deterministic evidence bundle, and any sentence we cannot verify is never published.
Not on feature count — heatmaps and revenue tracking are theirs, not ours, and their replay has been around longer. Our difference is narrow and specific: every sentence in the AI summary is bound to evidence, and AI traffic is separated from AI crawlers.
No. The tracker was written from scratch. What we took from Umami are ideas: the daily-salted cookie-free visitor hash and attribute-driven event definitions. The licences are compatible either way (MIT / Apache-2.0).
Other comparisons: