Adobe Analytics cost vs self-hosted Matomo

Adobe Analytics cost vs self-hosted Matomo: where the money goes

A renewal, a retention deadline or a residency requirement is usually what forces a finance or platform leader to compare costs, and the first point to settle is that Matomo's software costs nothing to license. Matomo is licensed under GPLv3, and its On-Premise Community edition is free with unlimited users and hits, with forum support. The comparison therefore turns on infrastructure, implementation, data migration, upgrades and the internal skills needed to run the platform. Adobe's side is set by the contract and by the retention terms you negotiate, and Adobe's prices are not on this page, so take them from your own agreement and any renewal quote.

On the Matomo side, the recurring cost is mostly servers. Matomo's requirements FAQ sizes a single server with at least 4 CPUs, 8 GB of RAM and 250 GB of SSD for up to 1 million pageviews a month, and recommends separate application and database servers with 8 CPUs and 16 GB of RAM each for up to 10 million pageviews a month. Your real pageview volume, retention period and backup needs decide which tier applies, so ask your cloud or data center team to price those instances in your own environment. For a reference point, Matomo Cloud plans start at 29 (excluding tax) per month for the smallest tiers, which shows what a hosted option costs before you pay for any infrastructure of your own.

Premium features are a separate cost. Matomo's Heatmap and Session Recording plugin is sold per number of users under the InnoCraft EULA rather than the GPL, and it includes a 30-day free trial, so confirm the per-user price with the vendor before you assume it is covered. One-time costs include implementation, tag migration and historical data import, which may be delivered by your staff or a partner under a written, fixed scope. Recurring costs include server hosting, upgrades, security patching and analyst time. Ask any implementation partner for a quote that separates these items so you can compare them directly with the Adobe renewal.

Which cost components each option carries, and whether they recur

This table sets each cost component of Adobe Analytics against the same component in a self-hosted Matomo deployment, and marks whether it is one-time or recurring. Matomo's On-Premise Community edition is listed as free with unlimited users and hits, so the recurring cost on that side is mainly infrastructure, plugins if you buy them, and the people who run the system. Use the rows to build a quote request and to see which costs you can estimate yourself.

Cost component	Adobe Analytics side	Self-hosted Matomo side	One-time or recurring
Software or subscription	Annual Adobe contract for Analytics, priced by Adobe on your own terms. Confirm the contract term and any renewal uplift in writing.	Matomo On-Premise Community edition is listed as free forever with unlimited users and hits and forum support. No license fee applies to the core product.	Adobe: recurring. Matomo Community: none.
Retention or data extension	Extended data retention is sold by Adobe. Ask for the retention period included in your contract and the cost of any extension.	You set retention in your own storage and database. Storage growth, backup size and deletion policy are your decisions, which also support CNIL-style limits on tracker lifetime.	Adobe: recurring while extended. Matomo: recurring storage cost.
Infrastructure	None on your side for the analytics platform itself, although you may run cloud storage for raw data feeds before retention ends.	Application and database servers sized by pageviews. Matomo's requirements FAQ lists a single server with 4 CPUs, 8 GB RAM and 250 GB SSD for up to 1 million pageviews a month, and separate servers with 8 CPUs and 16 GB RAM each for up to 10 million.	Matomo: recurring (cloud or data center hosting). Scales with traffic.
Premium plugins	Adobe-side modules and add-ons are sold separately. Confirm which features are in your contract and which are optional.	Heatmap and Session Recording is a paid premium plugin sold per number of users under the InnoCraft EULA, with a 30-day free trial. The Google Analytics Importer is free under GPL v3 or later.	Premium plugin: recurring if licensed per user. Importer: none.
Implementation	Adobe or partner services for tagging, Analysis Workspace setup and report design. Ask for the scope and the hours in writing.	Installing, configuring, setting up sites, goals, custom dimensions and the tag manager switch. Often a one-time project, delivered by your team or a partner under a fixed scope.	One-time.
Data migration	Raw data feeds and Data Warehouse exports are often delivered by Adobe to your cloud storage. Export work and replay scripts are your cost.	Replaying raw history through the bulk Tracking API needs engineering time. The Google Analytics Importer only brings aggregated reports, so Visitor Log and segmentation do not cover imported history.	One-time.
Upgrades and maintenance	Handled by Adobe as part of the service, with changes outside your control.	You plan and test Matomo upgrades, PHP and database version changes, plugin updates and security patches. Matomo 6.0.0 needs PHP 8.1 or newer and MySQL 8.0 or newer or MariaDB 10.6 or newer.	Recurring.
Backups and monitoring	Covered by Adobe's service terms. Confirm restore procedures and export formats for your own records.	Your own database and file backups, restore tests, uptime monitoring and capacity planning. Retention of backups affects storage cost.	Recurring.
Support	Included in the Adobe contract at the support tier you bought. Confirm response times in writing.	Matomo Community includes forum support only. Paid support or a DeployOpen retainer is a separate recurring contract, priced from a written scope.	Recurring if you buy it.
Internal analyst and engineering time	Analysts work in Analysis Workspace. Engineers maintain tags and data feeds.	Platform owner for hosting and upgrades, analysts retraining on Matomo reports, and engineers for custom reports and integrations. Plan this for both the migration and the ongoing run.	Migration: one-time. Ongoing operation: recurring.

What moves the comparison up or down

The cost gap between Adobe Analytics and self-hosted Matomo is set less by the license line and more by a few operating variables. Measure these before you compare quotes, because each one changes server tier, staffing or the features you can keep.

Pageview volume sets server tier

Matomo's requirements guidance sizes a single server for up to 1 million pageviews a month, and separate app and database servers for up to 10 million. Above that range, the hardware line grows with traffic, and it recurs every year in cloud or data center costs. Measure your monthly pageviews across all sites, peak-hour load and growth over the next two years. Ask whether your traffic peaks sit inside the single-server range or need split servers from day one.

Users who need premium features

Matomo's core reporting is free under GPLv3, but the Heatmap and Session Recording plugin is a paid premium plugin priced per user under the InnoCraft EULA. The cost rises with the number of people who need heatmaps or recordings, so it can exceed the server cost. Count the analysts, product managers and marketers who will open these features, and separate them from people who only read dashboards. Also check whether adding such features affects your consent position in the EU, as noted in Matomo's ePrivacy guidance.

Retention length and export path

Adobe's retention terms and extensions set how long history stays in the platform, and a longer window is often bought as an add-on. In a self-hosted setup, retention is whatever your database can hold, so storage grows with every year of raw hits you keep. Measure how many years of history your reports and audits need, and the size of your existing data feeds. Confirm with Adobe the exact export window and format before the deadline, because data not exported is lost.

Availability and backup requirements

A self-hosted Matomo instance becomes your responsibility: you must provide redundancy, patching, backups and tested restores for both the application and the database. Adobe carries the hosting uptime of its service, while your team carries it here. Define the uptime and recovery targets your business needs for dashboards that feed campaigns or executive reporting, then price the standby capacity, backup storage and monitoring that meet them. Ask any implementation partner to state how restores are tested and how often.

Sites and tag implementations

Adobe licenses and tag work often scale with the number of report suites, properties and tag implementations across brands. In Matomo, each site is a separate configuration, and migration effort grows with the count of tags, custom dimensions and goals you must rebuild. Inventory every site, tag manager container, data layer and custom variable, then estimate the rework per site. Sites that share a template usually cost less to migrate than one-off implementations.

In-house PHP, MySQL and web server skills

Matomo runs on PHP with MySQL or MariaDB behind Apache, Nginx, IIS or LiteSpeed, so the cost depends on whether your team already operates that stack. Teams without these skills either hire, train or pay for managed support, and each path recurs. Check current PHP and database versions against the Matomo 6.0.0 requirements, which need PHP 8.1 or newer and MySQL 8.0 or newer or MariaDB 10.6 or newer. Name the person who will own upgrades and patch cycles before you sign any contract.

How pageview volume sets Matomo server sizing

A single server suits sites that stay at or below about 1 million pageviews a month. Matomo's requirements FAQ gives a minimum of 4 CPUs, 8 GB of RAM and 250 GB of SSD for this volume, with the web server, PHP and database running on one machine. Teams moving off a free or small analytics plan often start here, and for this tier the main recurring cost is one instance or one server plus its operator time.

CPU and memory floor: at least 4 CPUs and 8 GB of RAM, the minimum the FAQ lists for this volume.
Storage: 250 GB of SSD as the starting figure. Raw hits and archives grow over time, so plan retention before you fix the disk size.
Shared resources: the web server, PHP and MySQL or MariaDB compete for the same memory and CPU, so archiving during peak hours can slow reports.
Backups: one node concentrates risk, so budget for database and configuration backups kept in your own storage.

Check the single-server figure against your monthly pageviews, including peak months, before you choose an instance type.

Where premium plugins and consent rules change the model

The self-hosted Matomo cost is not only the server line. Two Matomo add-ons change the model: the Heatmap and Session Recording plugin is a paid premium plugin sold per number of users under the InnoCraft EULA rather than the GPL, and it carries a 30-day free trial. Treat it as a recurring line item, not a one-time cost, if your analysts or product teams need heatmaps or replays. Confirm the current per-user price on the Matomo plugin marketplace and ask whether the license renews annually and how seats are counted, since adding users later raises the bill.

Consent is the second change. Matomo's ePrivacy FAQ states that CNIL recognizes some audience measurement trackers as exempt from consent only when they stay within narrow purposes and collect anonymous statistics. Adding User ID, heatmaps or session recordings removes that exemption. If you enable any of them, you need a consent management layer on the self-hosted side as well as on the Adobe side, with its own licensing, configuration and testing effort. Ask your legal and privacy team to confirm which regimes apply to your visitors, since the FAQ also names Italy, the Netherlands and Spain as authorities with their own criteria.

The Google Analytics Importer is free under GPL v3+, so it adds no license cost, but it is not a full history migration. It imports only aggregated report data, so the Visitor Log, Ecommerce Log, Custom Reports and Segmentation do not work on imported reports, and some reports such as Funnels are not imported. Reporting continuity therefore becomes a cost of its own: someone must decide which year-over-year views the business needs, rebuild any segment-based analysis on new data, and document the gap for stakeholders. Budget that analyst time explicitly, and check the Matomo limitations FAQ against your report inventory before you commit.

How to build the comparison with your own numbers

This sequence turns vague renewal estimates into a three-year total cost comparison built from your own contract terms, traffic volumes and staffing hours. Each step produces a figure you can check, so the result shows which assumptions actually drive the outcome.

Collect the current Adobe contract and retention terms
Ask the Adobe account owner for the current order form, the annual or multi-year fee, every add-on (such as additional report suites, data feeds, Data Warehouse or premium features) and the contractual terms for data retention and any retention extension. Confirm in writing how long unexported data is kept and what the notice and exit terms are. Done when you have one sheet listing each line item, its price basis and its renewal date, with the source document named beside it.
Export twelve months of pageviews and users
Pull twelve consecutive months of monthly pageviews and unique users from Adobe Analytics, and note any month with unusual spikes such as campaigns or launches. Record the same figures from any other analytics tool still in use so the two sources can be reconciled. Done when you have a table of twelve rows with pageviews, users and the peak month, and you know whether the numbers are sampled, filtered or bot-excluded.
Size the Matomo servers from your volumes
Compare your peak monthly pageviews with the sizing tiers in Matomo's requirements FAQ. A single server is listed for up to 1 million pageviews a month, and separate app and database servers are recommended for up to 10 million. Above that range, ask a platform engineer or implementation partner to size the stack from your own load tests. Done when you have a server count, CPU, RAM and storage for each tier your traffic reaches, with the sizing source cited.
Price infrastructure for app, database, backup and staging
Price the compute, storage, network egress and backup capacity for the sized servers in the cloud account or data center you will use, plus a staging environment for upgrades and testing. Include the cost of backup storage retained off-server, because losing analytics history is the main risk of self-hosting. Done when each server has a monthly line item from your cloud or data center billing, and you can say which costs are fixed and which scale with traffic.
Add plugin licenses where your reports need them
List the features your analysts use in Adobe that Matomo does not include in the Community edition, such as heatmaps or session recordings, and check each one against the Matomo plugin marketplace. Premium plugins are licensed per number of users under a separate EULA, and marketplace listings show their trial terms. Note which features are not required, because each premium plugin adds a recurring cost. Done when every plugin has a yes or no decision and a licensed user count.
Request written quotes for migration and implementation
Ask each implementation partner, and your internal team for effort estimates, to quote the one-time work: tracking code replacement, mapping Adobe props, eVars and events to Matomo dimensions and goals, replaying historical data, testing and cutover. Ask for the scope, the deliverables and the assumptions behind each line in writing. Done when each quote lists its scope, what is excluded and the dates it depends on, so you can compare them on the same basis.
Add recurring upgrade, support and analyst hours
Estimate the hours per month your team will spend on Matomo upgrades, security patches, backups checks, monitoring and support tickets, and the analyst hours spent on reports that Adobe's Analysis Workspace produced before. Price those hours at your internal loaded rate, and add any paid support or retainer quote as a separate recurring line. Done when you have a monthly hours figure, the people it comes from, and an annual total for the three-year model.
Compare three-year totals and test the assumptions
Build a three-year model with one-time costs in year one and recurring costs in each year, including the Adobe renewal, the retention extension and any price increase stated in writing. Change the traffic growth, staffing hours and migration quote to see which inputs move the result most. Done when you have a total for each option, a list of the two or three assumptions that change the ranking, and a note of the figures you still need to confirm with Adobe or your vendors.

Costs teams forget on each side

The obvious comparison is the Adobe contract against the Matomo server bill, but the costs that surprise teams sit at the edges: getting data out of Adobe, rebuilding what Adobe anchored, and running Matomo as a service after launch. Each card below marks whether the cost is one-time or recurring so the total can be budgeted honestly.

Retention extensions and data feeds

Adobe's data retention terms set the clock for leaving, and any extension you buy keeps the contract running longer than the migration needs. Plan the export before that clock matters: hourly or daily raw data feeds have to be landed in your own storage and kept in a format you can replay. Storage for years of raw hits is a recurring cost, while the export job and its validation are one-time. Ask Adobe in writing which retention period applies to your report suite and what the historical export covers.

Rebuilding dashboards and reports

Analysis Workspace projects, calculated metrics, segments and scheduled reports built by analysts over the years do not move into Matomo automatically. Each one has to be redesigned as a Matomo report, custom dimension, goal or segment, and some Adobe constructs may have no direct equivalent. This is a one-time cost in analyst and developer time, but it recurs as stakeholders request reports that the old Adobe setup handled. Inventory the dashboards and rank them by who uses them before estimating the work.

Experience Cloud dependencies

Adobe Analytics often sits inside Adobe Experience Cloud, where Target, Audience Manager, Launch or Customer Journey Analytics read its data or share identifiers. Removing Analytics can break those integrations, and some may need a replacement rather than a rewire. Costs here are recurring if the other Adobe products stay licensed, and one-time if they are replaced. Confirm with your Adobe account team which products depend on the Analytics data layer and which contract terms apply to each.

Staging and backup testing

A self-hosted Matomo needs a staging copy of the application and database to test upgrades, plugin changes and tracker updates before production. Restore testing, meaning a periodic rebuild from backup to confirm the data is usable, is easy to skip and expensive to discover missing later. The staging environment and backup storage recur every month, while the first test plan and restore runbook are one-time work. Ask your infrastructure team how their existing backup tooling covers the Matomo database and file store.

Patching and PHP or database moves

Matomo is a PHP application on a relational database, so security patches, PHP releases and MySQL or MariaDB upgrades arrive on your schedule. Matomo 6.0.0 needs PHP 8.1 or newer and MySQL 8.0 or newer or MariaDB 10.6 or newer, so older hosts may need a platform upgrade before any Matomo upgrade. This work recurs for as long as you run Matomo, and the cost depends on how many environments and plugins you maintain. Check the requirements FAQ before each major release.

Tag management rebuild

Adobe Launch or another tag manager usually carries the Adobe Analytics tags, data elements and rules that fire on every page. Moving to Matomo means rewriting those tags for the Matomo tracking code, testing each event, and retiring the Adobe rules without losing coverage. This is a one-time cost, though it grows with the number of sites and single-page app flows. Ask for a tag inventory with owners before work starts.

Reconciling aggregated imported history

Matomo's importers bring over aggregated report data, not raw hits, so Visitor Log, segmentation and some reports such as Funnels do not work on the imported history. Reconciling totals between Adobe exports and Matomo reports, and documenting which periods are only available in aggregate, is an analyst task that takes time before stakeholders trust the numbers. This is one-time effort, but it also determines how long you keep the old Adobe reports for reference. Agree a reconciliation method and a sign-off owner before cutover.

Questions buyers ask about cost, effort and skills

How much does an Adobe Analytics contract cost?

Adobe Analytics pricing is set in your contract and quoted by your Adobe account team, so no public figure applies to your organization. The terms that move the total are the licensed scope (report suites or properties, server calls or hits, and users), the data retention period included in the agreement, any data retention extension you buy beyond the standard period, the Experience Cloud products bundled with it, and the renewal and escalation clauses. Ask for the price for each component separately, the overage rules for traffic above the licensed volume, and what happens to your historical data and raw data feeds at the end of the term. Compare that written quote with the cost components on the self-hosted side before you decide.

Does Matomo's free edition remove license cost completely?

For the software itself, yes. Matomo is licensed under the GPLv3, and the On-Premise Community edition is listed as free forever with unlimited users and hits. The costs that remain are the infrastructure that runs it, the people who operate and change it, and any paid premium plugins you choose. Infrastructure includes application and database servers sized by pageview volume, backups, storage and monitoring. People costs include the engineers who install, upgrade and secure the platform, and the analysts who rebuild reports, goals and custom dimensions. Premium plugins such as the Heatmap and Session Recording plugin are sold under a separate commercial license, so they carry their own cost. Ask for an estimate of each component in your own environment.

How long does a migration from Adobe Analytics take?

The timeline depends on the scope you agree in writing, not on a fixed figure. The main drivers are the number of sites and report suites, how many props, eVars and events you need to map to Matomo custom dimensions and goals, how much raw history you intend to export and replay, how many tags must change in your tag manager, and how many dashboards and scheduled reports your analysts depend on. Retention deadlines in your Adobe contract also set a hard limit on how long you have to export data, so confirm that date early. A fixed-scope written plan from DeployOpen lists deliverables and timelines before work starts, which lets you compare options on a like-for-like basis.

Can our team run Matomo without outside help?

Many teams can run Matomo in-house if they have the skills below, but the skills must exist on your team, not only on paper. Operations needs a Linux administrator who can manage PHP, a supported database (MySQL 8.0 or newer, or MariaDB 10.6 or newer for Matomo 6.0.0), a web server such as Apache or Nginx, backups, and monitoring. Analytics needs someone who can design the tracking plan, configure goals and custom dimensions, and maintain the tag manager setup. Privacy and legal teams need to review consent settings against CNIL rules where you operate in France or the EU. Check whether you have these roles covered for the expected traffic and during upgrades, and plan for staff absence.

What does a support contract change in practice?

A support arrangement changes who is accountable when something breaks and how quickly help is available, but it does not remove the need for internal ownership. The Matomo Community edition is supported through forums, so an in-house team usually carries incident response, upgrades and troubleshooting. A commercial support or retainer agreement, such as the ongoing support, upgrades and continuous testing offered by DeployOpen, adds defined responsibilities for maintenance, patching and periodic review. Ask any provider to state in writing what is covered, response expectations, how upgrades are tested before they reach production, and which items your team still owns, such as traffic changes and tag updates. Compare that recurring cost with the staff time it would otherwise take.

How do Matomo Cloud plans compare with self-hosting Matomo?

Matomo Cloud starts at 29 (excluding tax) per month for the smallest tier, which covers up to 50,000 hits a month, and tiers scale up to 10 million hits a month, according to Matomo's pricing page. Cloud data is stored in Frankfurt, Germany. Self-hosting removes the subscription but moves infrastructure, upgrades, backups and staffing onto your side. To compare them fairly, match the hit volume and retention you need, add the server and storage costs and the staff time for self-hosting, and check whether the data location meets your residency rules. Also confirm whether the premium plugins you need are priced separately under either option.

How DeployOpen scopes a fixed-price Matomo implementation

DeployOpen plans, implements, hardens, documents and supports self-hosted open-source platforms inside your own infrastructure. For a move from Adobe Analytics to Matomo, we start from a written scope that sets out what your Matomo servers, data and tracking will cover before any work begins.

How we scope

We confirm which Adobe Analytics report suites, sites and tracking points the Matomo scope must cover.
We size the Matomo application and database servers against your actual monthly pageview volume and hosting platform.
We record which premium plugins, if any, are in scope, and which features you will run without them.

How we build

We install and configure Matomo on your own cloud accounts, data centers or air-gapped networks.
We map your props, eVars and events to Matomo custom dimensions and goals, and document each mapping.
We test tracking, consent settings and retention configuration in a staging environment before any production switch.

How we hand over

We deliver runbooks for backups, upgrades, server patching and the bulk replay of exported history.
We document the configuration, access model and reporting setup so your analysts can run Matomo without us.
We agree the acceptance criteria in writing and walk your team through each deliverable before sign-off.

How we support

Ongoing support, upgrades and continuous testing are available as a retainer after the fixed-scope work ends.
We can prepare the systems, controls and evidence your compliance assessors will ask for, though auditors issue the actual opinions.
We recommend confirming the support scope, response expectations and upgrade cadence in the written quote before work starts.

Adobe Analytics cost vs self-hosted Matomo