Plausible alternative with revenue attribution
trckable vs Plausible: a self-hosted Plausible alternative in one container, with Stripe, Lemon Squeezy, Polar, Paddle and Dodo revenue attribution free. Sourced facts, and where Plausible is better.
Plausible is the best-known privacy-first analytics tool, and a good one. This page is for people who like its simplicity but want revenue attribution without the Business plan, or a self-hosted setup without ClickHouse.
Who each is for
- Plausible suits a team that wants a polished hosted service from an established EU company and is happy to pay for it, or a self-hoster with a 2 GB server who does not need revenue in the dashboard.
- trckable suits a founder who wants to see which source brought paying customers, on a small server, without an open-core split.
Side by side
| trckable | Plausible | |
|---|---|---|
| Self-host stack | 1 container, no external database | Plausible app + PostgreSQL + ClickHouse (CE README) |
| RAM | 52 MB idle, measured in CI | "2 GB RAM" recommended (CE README) |
| Script, gzipped | 1,596 B pageviews only; 2,045 B with goals, outbound links, downloads and checkout attribution | 1,283 B default script.js; 2,141 B with tagged events, outbound links, downloads and revenue (measured, method) |
| Revenue attribution | Stripe, Lemon Squeezy, Polar, Paddle, Dodo, self-hosted and free | Ecommerce revenue goals from the Business plan; not in Community Edition (Plausible CE vs cloud) |
| Cookieless | Yes, or your own bar, or read your banner | Yes (plausible.io) |
| Price (10k pageviews) | Free, self-hosted | Starter $9, Growth $14, Business $19/month; 30-day trial (plausible.io pricing) |
| Self-hosted features withheld | None | Funnels, user journeys, revenue goals, SSO, Sites API (source) |
Plausible's figures were checked on 27 September 2026; trckable's are CI's measurements of 30 Sep 2026 (By the numbers).
Where Plausible is better
- Track record. Plausible has been running since 2019 with a large user base; trckable is young. If you need a vendor with years of history, that counts.
- Its default script is smaller than ours for pageviews only (1,283 B against 1,596 B). With the same features ours is smaller.
- Advanced bot filtering on its cloud, which excludes data-centre IP ranges (source).
- Integrations and ecosystem: more plugins, guides and third-party tutorials exist for Plausible than for trckable.
How to switch
- Add trckable's script next to Plausible's and run both for a week.
- On Community Edition, export raw events from ClickHouse and import them: Migrate from Plausible.
- Connect your payment provider in Revenue; history comes from the provider.
- Remove Plausible's script.
How it compares
trckable next to the other free, self-hostable analytics tools: script size, what you have to run, revenue, and where it is not the right choice.
Umami alternative with revenue attribution
trckable vs Umami: self-hosted analytics without a separate database, with payment-provider revenue attribution instead of manual revenue events. Sourced facts, and where Umami is better.