True open source
d8a.tech: MIT: permissive, embed and modify without copyleft obligations.
Matomo: GPLv3 core; several advanced features are paid premium plugins.
Resources / Comparisons
Matomo is a proven privacy-first analytics platform with a rich UI and strong compliance story. d8a.tech is for teams that like Matomo tracking but want reporting-ready, warehouse-native data without MySQL archiving, schema joins, or raw-data export pain.
Which one should you choose?
Choose Matomo when you need a mature all-in-one analytics UI with heatmaps, session recordings, A/B testing, and a broad plugin ecosystem. Choose d8a.tech when your Matomo data needs to become clean, flat, warehouse-ready clickstream that can scale without turning analytics infrastructure into a dedicated engineering project.
Jump to the feature tabled8a.tech: MIT: permissive, embed and modify without copyleft obligations.
Matomo: GPLv3 core; several advanced features are paid premium plugins.
d8a.tech: No archiving cron. Session tables land in your warehouse as sessions close.
Matomo: Reports depend on archiving jobs that get heavy at high volume.
d8a.tech: Go pipeline with BigQuery, ClickHouse or Parquet storage.
Matomo: PHP application on a MySQL database.
d8a.tech: Point your existing Matomo tracker at d8a.tech, or run both side by side.
Matomo: Moving away from Matomo usually means re-tagging.
Matomo is one of the strongest privacy-first alternatives to Google Analytics. It has a mature tracker, a deep UI, consent and privacy tooling, and years of trust from organizations that want data ownership.
d8a.tech is strongest when Matomo tracking is good enough, but Matomo storage is not. It speaks the Matomo protocol, can receive the same tracking events, and stores them in a flat warehouse-ready schema with session and ecommerce fields already resolved.
Tick Discuss next to anything you want to cover on a call. We'll start the conversation there.
d8a.tech stores tracked fields, session context, ecommerce data, campaign data, and custom values in a reporting-ready shape.
Matomo spreads data across log_visit, log_link_visit_action, log_action, conversion, item, and archive tables.
d8a.tech writes queryable event rows the moment each session closes. In Matomo, raw event access often requires direct database queries, MySQL/MariaDB replication, plugins, or time-consuming exports.
Matomo's API is mostly a reporting API, not a raw event stream for warehouse analytics.
Session source, landing page, duration, counters, and ecommerce session context can be queried directly with event data.
In Matomo, session-level context requires joining log tables and resolving action IDs.
d8a.tech keeps order fields and item details in a readable event schema. Matomo stores ecommerce items through conversion tables and action lookup IDs.
d8a.tech relies on analytical storage at query time. Matomo reporting depends heavily on archive tables generated by cron jobs.
d8a.tech writes each session to your warehouse the moment it closes, after 30 minutes of inactivity by default (configurable). Matomo reporting requires pre-aggregation, so at high event volume dashboards can lag by many hours, one day, or more if archive jobs fall behind.
Fresh raw-event workflows usually require database replication or exports outside the standard Matomo reporting path.
Above 100M events per month, Matomo can require expensive hardware, careful MySQL tuning, archive-job monitoring, and dedicated engineering time, with no guarantee that dashboards stay stable under load.
d8a.tech can receive Matomo protocol requests and map them into a warehouse-ready schema. Use Matomo's own addTracker API to send the same events to d8a.tech while Matomo keeps running.
d8a.tech also supports a GA4-style event model if you later outgrow Matomo's event format.
Matomo custom events require category and action fields. d8a.tech can preserve Matomo events and also supports a more flexible native event model where event parameters do not need to be pre-configured in the UI before they are collected.
Matomo custom dimensions need to be predefined before they are used. d8a.tech preserves Matomo custom dimensions and can also collect flexible event parameters without UI pre-configuration.
d8a.tech can write directly to your analytics storage. Matomo Cloud has a data warehouse connector, but this is an export workflow from Matomo rather than the core storage model.
d8a.tech exposes flat data to BI tools. Matomo's BI workflows typically depend on its reporting API, Data Studio connector, or warehouse export setup.
d8a.tech writes each session to your warehouse the moment it closes, after 30 minutes of inactivity by default (configurable). Matomo freshness depends on archiving mode, cron scheduling, and reporting context.
Realtime widgets exist, but many Matomo reports depend on archive processing and can lag based on infrastructure and cron setup.
AI agents work better with flat, readable event tables than with reporting APIs and normalized lookup-heavy schemas.
Matomo Cloud stores data in AWS Frankfurt with backups in Dublin. d8a.tech also offers EU hosting and warehouse-native deployment paths.
AWS remains a non-EU subprocessor. For teams avoiding non-EU subprocessors, Matomo is fully clean only when self-hosted.
Both products can be self-hosted, but d8a.tech also supports warehouse-native deployment paths where the storage location follows your own data platform.
Matomo self-hosting means PHP, MySQL/MariaDB, archive cron monitoring, plugin updates, GeoIP updates, and database tuning. Each part is manageable alone, but together they create a larger operational surface to monitor and maintain.
d8a.tech was built with modern technologies for minimal required maintenance and strong scalability.
Matomo Cloud pricing scales by traffic, and some advanced capabilities may depend on paid plugins or higher plans.
It can be, but the easiest path is often to run d8a.tech alongside Matomo first. Matomo can remain the familiar UI while d8a.tech receives the same events and writes them into a flat, reporting-ready warehouse schema.
Yes. Matomo's own addTracker API can send the same tracking events to a d8a.tech endpoint. That means you can keep Matomo dashboards and add a warehouse-native event pipeline without rewriting your tracking implementation.
Matomo is an all-in-one analytics application. d8a.tech is a warehouse-native collection and analytics layer. The biggest difference is the data model: d8a.tech gives you flat, queryable event rows with session and ecommerce context, while Matomo stores data across many MySQL tables and pre-aggregated archive tables.
For dashboard usage, Matomo's schema is mostly hidden. For analysts, BI tools, or AI agents, it becomes painful because useful answers often require joining log_visit, log_link_visit_action, log_action, conversion, item, and archive tables. d8a.tech avoids that by storing reporting-ready fields directly on event rows.
Choose Matomo if you need its mature UI features today: heatmaps, session recordings, A/B testing, form analytics, WordPress integration, plugin ecosystem, or a proven all-in-one privacy analytics suite. Choose d8a.tech when warehouse-ready data, raw event access, simpler schema, and lower operational complexity matter more.
Tell us what matters to you and we'll walk you through it on your own stack. Or start with free Cloud and see for yourself.