Open-source alternatives guide
Plausible vs Matomo vs PostHog: Analytics 2026
Compare Plausible, Matomo, and PostHog by documented capabilities, support model, deployment ownership, release cadence, privacy configuration, and total cost.
TL;DR
Choose among Plausible, Matomo, and PostHog by documented capabilities, support model, deployment ownership, release cadence, privacy configuration, and total cost. None is a universal winner.
Plausible Community Edition is a free AGPL long-term release with a documented subset of Cloud features. Matomo provides on-premise analytics and a current installer. PostHog provides a broad product-analytics event model, while its self-host path is officially unsupported, unversioned, and operated at the deployer's risk.
Key Takeaways
- Plausible CE is free and AGPL-3.0-or-later; its deployment wrapper is a separate MIT-licensed repository surface.
- Matomo's repository reports GPL-3.0, and its latest approved release is 5.13.0, published 2026-08-16.
- PostHog's root repository has a mixed-license boundary; self-hosting is officially unsupported and has no tagged versions.
- Dated repository counters are identity receipts, not a popularity ranking.
- PostHog's current free tier includes 1M events, 5K session recordings, and one million feature-flag requests per month; product-analytics overage starts at 0.00005 dollars per event.
- Measure script and infrastructure impact in the target deployment. The approved sources provide no cross-product benchmark.
At-a-glance decision table
| Product | Documented center of gravity | Deployment and support boundary | Validate before choosing |
|---|---|---|---|
| Plausible | Focused web analytics with a site-specific tracking snippet | Cloud and a twice-yearly CE long-term release with fewer premium features | Required reports, CE/Cloud feature boundary, snippet configuration, migration, and support |
| Matomo | On-premise web analytics with an installer and MySQL database | Operator-managed on-premise installation or traffic-tiered Cloud | System and database requirements, optional features, privacy configuration, upgrades, and total cost |
| PostHog | Product analytics using events, persons, properties, dashboards, and API access | Cloud products or officially unsupported, unversioned self-hosting | Product scope, event model, retention, operator responsibility, current support, and cost |
Evidence cards
Pricing and plan boundaries
PostHog's pricing page, captured 2026-08-22, includes one million analytics events, five thousand session recordings, and one million feature-flag requests in the monthly free tier. Product-analytics overage starts at 0.00005 dollars per event.
Matomo Cloud is traffic-tiered; the captured 50,000-hit surface displayed 29. The package does not authorize an inferred currency, billing interval, or annual total. Plausible's self-host page supports that CE is free, but it does not support the former Cloud tiers in this guide. Refresh all three current pricing surfaces before publication.
Dated repository counters
At access time, canonical APIs reported:
- Plausible Community Edition deployment repository: 2,767 stars and 439 forks
- Matomo application repository: 21,797 stars and 2,892 forks
- PostHog application repository: 38,568 stars and 3,243 forks
The repositories differ in scope, so these dated counters are identity receipts, not a popularity ranking.
Release and support models
Plausible CE uses a twice-yearly long-term release model rather than Cloud's continuous schedule. Matomo 5.13.0 was published on 2026-08-16. PostHog says self-hosted deployments have no tagged versions and should follow the latest image; self-hosting is officially unsupported.
License & open-source status
Plausible Analytics and CE are AGPL-3.0-or-later. The separate plausible/community-edition deployment wrapper reports MIT for its wrapper files. Matomo reports GPL-3.0. PostHog's root license applies MIT Expat outside named exceptions, while ee and third-party content use separate licenses. Review those exact boundaries for the deployed revision.
Evidence boundaries
The dated pricing shorthand is PostHog 1M events, 5K session recordings, and 0.00005 dollars per event; Matomo traffic-tiered; Plausible CE free. Release status is Plausible CE twice-yearly long-term release, Matomo 5.13.0, and PostHog self-host has no tagged versions. The license summary is Plausible AGPL-3.0-or-later, with a deployment wrapper distinction; Matomo GPL-3.0; and a PostHog mixed-license boundary. Integration review must cover the site-specific Plausible snippet, Matomo system and database requirements, and PostHog event model and operator responsibility. Use conditional decision criteria centered on support and deployment ownership. Keep the Plausible CE feature boundary visible, and recheck PostHog's officially unsupported self-hosting status before publication.
Plausible
Plausible provides focused web analytics. Its current integration requires a site-specific Plausible snippet. For a self-hosted evaluation, the preserved example domain remains https://analytics.yourdomain.com, with a script URL such as https://analytics.yourdomain.com/js/script.js.
The approved self-hosting documentation distinguishes Community Edition from Cloud. CE is a free long-term release with fewer premium features and a twice-yearly release cadence. Treat this as a product boundary rather than a feature-parity claim.
The previous guide framed Plausible as answering “how many people visited?” That shorthand is useful only if the team's required reports fit the documented CE or Cloud surface. Verify events, goals, exports, retention, multi-site needs, and stakeholder reports before committing.
Repository: plausible/community-edition
Matomo
Matomo provides on-premise analytics with a current installer. Its installation guidance includes system checks and a MySQL database, and an official Docker image is available. Complete an installation wizard at http://your-server:8080/index.php?action=databaseSetup only in a secured test environment with the current official instructions.
The sources used here do not establish universal memory, storage, traffic, setup-time, or script-size numbers. Size the application and database for the target event volume, reports, retention, imports, and optional features. Test backup and restore before production use.
The existing guide uses privacy-setting labels such as “Use anonymized IP addresses” and “Disable cookies”. Those labels are preserved for continuity, but this evidence package does not authorize treating them as sufficient legal or technical compliance proof. Verify the current Matomo privacy documentation and obtain the appropriate review for the deployment.
PostHog
PostHog documents events, persons, properties, trends, funnels, retention, paths, stickiness, lifecycle insights, dashboards, and API access. Optional, premium, privacy, experimentation, session-replay, and importer claims still need their own current sources.
The prior guide described the question as “what did specific users do, why did they drop off, and which feature drove retention.” The current product surface supports that event-model framing, but answering the question still requires instrumentation and governance.
Cloud is a current supported product surface. Self-hosting remains available but is officially unsupported, unversioned, and operator-managed. A preserved example host is https://posthog.yourdomain.com. The old bootstrap URL https://raw.githubusercontent.com/posthog/posthog/HEAD/bin/deploy-hobby is retained here only as a superseded reference; do not execute it as current supported deployment guidance.
The previous guide used the phrase “up to 1M events/month”. The 2026-08-22 pricing snapshot is more precise: the monthly free tier includes one million analytics events, with separately stated allowances and overage terms that must be refreshed before publication.
Documented capability boundaries
Plausible
- Focused web analytics.
- Site-specific tracking snippet.
- Cloud and CE feature/release differences.
- CE as a free AGPL long-term release.
Matomo
- On-premise analytics and current installer.
- System checks and MySQL database requirements.
- Official Docker image.
- Traffic-tiered Cloud as a separate service surface.
PostHog
- Event, person, and property model.
- Trends, funnels, retention, paths, stickiness, lifecycle insights, dashboards, and API access.
- Cloud products and an operator-responsibility boundary for self-hosting.
Source optional and premium features separately before adding them to a comparison matrix.
Hosted vs self-hosted
Cloud and self-hosted products have different support, release, feature, and operating boundaries. Confirm those boundaries for the exact product and revision before migration.
Integration and deployment boundaries
| Product | Integration starting point | Self-host responsibility |
|---|---|---|
| Plausible | Install and validate the site-specific tracking snippet | CE deployment, twice-yearly releases, data, backups, and feature-boundary review |
| Matomo | Complete current system checks and database setup | Application, MySQL, storage, backups, upgrades, privacy configuration, and recovery |
| PostHog | Define an event taxonomy and validate SDK/API behavior | Entire deployment and scaling path; self-hosting is unsupported and unversioned |
Do not assume zero configuration, automatic consent compliance, feature parity, or automatic capture. Test the exact application and deployment.
Performance and infrastructure methodology
There is no controlled cross-product benchmark in the approved package. Do not compare tracking-script sizes, Core Web Vitals impact, memory, storage, pageview capacity, setup complexity, upgrade duration, or migration timelines without a reproducible receipt.
For the target deployment, record:
- Script and SDK version, configuration, and served bytes.
- Browser and page workload, including consent and tag-manager behavior.
- Ingestion volume, event shape, cardinality, retention, and query mix.
- Application and database resources, storage growth, and backup duration.
- Warmup, repetitions, raw output, error rate, and user-visible performance.
- Upgrade, rollback, restore, and incident-recovery timing measured on the target system.
Maintenance burden
Plausible CE, Matomo on-premise, and PostHog self-hosting transfer different amounts of work to the operator. Inventory upgrades, database care, storage, backups, restore tests, monitoring, security response, capacity, and support. PostHog's current self-host path is officially unsupported, so the operator owns that risk without a supported release channel.
Pricing comparison
| Surface | Frozen approved fact | Boundary |
|---|---|---|
| Plausible CE | Free | Does not establish current Cloud pricing or feature parity |
| Matomo Cloud | Traffic-tiered; captured 50,000-hit surface displayed 29 | Refresh currency, billing interval, traffic definition, and add-ons |
| PostHog Cloud | 1M analytics events, 5K session recordings, and 1M feature-flag requests in the monthly free tier | Refresh allowances, product scope, and overage before publication |
| PostHog product analytics overage | Starts at 0.00005 dollars per event | Usage and pricing are volatile |
No product is labeled the cheapest. Total cost includes the exact plan, optional features, infrastructure, data transfer, storage, backups, support, and staff time.
Migration readiness checklist
- Define required reports, events, properties, goals, users, retention, and privacy settings.
- Run the destination alongside the current system under a documented data-governance plan.
- Validate event counts and definitions; do not compare unlike metrics.
- Export and restore data where the product supports it.
- Test dashboards, API clients, alerts, scheduled reports, and stakeholder workflows.
- Document cookie, identity, retention, deletion, and access-control behavior.
- Treat “person deletion” as a feature that must be verified in the current deployment and API.
- Rehearse rollback before removing the previous analytics system.
The Google Analytics to Plausible migration guide covers the adjacent transition workflow. This packet does not authorize a fixed migration duration.
Privacy and compliance boundary
No tool is automatically compliant in every configuration or jurisdiction. Analytics data can include identifiers, URLs, properties, account data, and sensitive business events. Determine the lawful basis, retention, access, deletion, transfer, and consent requirements for the actual deployment.
Do not infer that a cookie setting or on-premise location completes that work. Validate product behavior and involve the appropriate privacy and legal owners.
Methodology
This comparison uses official Plausible self-hosting and script documentation, Matomo repository, release, and installation records, PostHog repository, license, self-hosting, and product documentation, and current pricing pages. It preserves the organic order Plausible, Matomo, then PostHog.
Unsupported benchmarks, universal recommendations, old plan values, one-label license rows, and supported Hobby-deployment claims have been removed. Recheck versions, counters, prices, allowances, releases, and provider status before publication.
FAQ
Which tool is best for simple web analytics?
Start with the required reports and operating model. Plausible is a candidate when its documented focused analytics surface meets those requirements. Confirm the CE/Cloud feature boundary before choosing a deployment.
Which tool is best for on-premise analytics?
Matomo and Plausible CE both have on-premise paths, but their capabilities, databases, releases, and operating requirements differ. Compare the exact current surfaces.
Which tool fits product analytics?
PostHog documents a broad event model and product-analytics capabilities. Decide whether Cloud meets the support and data requirements; self-hosting is officially unsupported, so the operator accepts the risk.
Can repository stars settle the choice?
No. They are dated counters from differently scoped repositories and not a popularity ranking or quality score.
Sources
The synchronized guide packet contains the approved source catalog, access dates, current and superseded assertions, and protected invariants for this refresh.
Related Guides
The SaaS-to-Self-Hosted Migration Guide (Free PDF)
Step-by-step: infrastructure setup, data migration, backups, and security for 15+ common SaaS replacements. Used by 300+ developers.
Join 300+ self-hosters. Unsubscribe in one click.