Matomo operating cost calculator

Estimate Matomo costs from recorded events, archiving, segmentation, raw-data retention, premium features, migration and operational support.

Last updated

In short

  • Recorded actions, report complexity and archiving matter more than pageviews alone.
  • Raw event data and processed reports have separate retention decisions.
  • Required premium plugins and residual analytics work belong in the budget.
On this page (6)

Costs and savings · Part of Matomo

Interactive worksheet · no sign-up

Estimate Matomo analytics costs

Use the same currency and scope for both options. Inputs stay in this page; they are not included in analytics or sent with an enquiry.

1. Your current bill
2. The replacement

Business management: CHF 1,590/month for up to 3 apps; onboarding from CHF 9,900. Infrastructure and paid licences are extra.

Additional metered archiving runtime

Historical reprocessing and segment complexity can dominate compute; enter only costs outside infrastructure.

Additional billable backup storage

Include copies and retention. Enter only costs outside the infrastructure quote and Pilae plan.

Matomo Cloud hits and self-hosted processing costs are different measures. Consent duties and lawful retention do not disappear with self-hosting.

3. Transition and overlap
Optional: value internal operating time

Time released is capacity, not automatically payroll or cash saved. Keep time already billed by Pilae or another supplier out of these fields.

How the calculation works
  1. Current monthly invoices = billed units × unit price + additional current spend.
  2. Replacement monthly invoices = Pilae management + additional infrastructure + target licences + workload usage + retained services.
  3. Transition = plan onboarding + new hardware + extra migration + training + parallel months × max(0, current invoices − retained services). Parallel months are capped at the comparison horizon.
  4. Total invoices = monthly invoices × horizon, plus transition for the replacement. Payback uses the full transition commitment divided by positive monthly invoice saving, including all entered overlap months even beyond the selected horizon.
  5. Economic saving adds the change in valued internal operating time. It does not assume headcount reduction.

Business includes up to 3 apps, then a published per-app fee (CHF 390 in CHF). Starter’s published CHF price is CHF 449/month. All Pilae figures come from the same price data as the pricing page. Workload inputs are your estimates, not supplier quotes. Taxes, price growth, discount rates, opportunity costs and differences in functionality are outside this arithmetic.

Matomo costs are shaped by the data collected and the reports people ask it to produce. Owning the analytics service changes where the data and responsibilities sit; it does not remove the work of tracking design, report maintenance or privacy configuration. Use this calculator to budget the installation around a real measurement plan.

Describe the tracking workload

Input Why it changes cost
Recorded actions Events, downloads and pageviews can generate different volumes
Sites and segments More report combinations can increase processing
Historical import Backfill can create a temporary ingestion and archiving peak
Raw retention Detailed investigation versus storage and privacy needs
Report retention Long-term trends may have different requirements
Premium features Plugin subscriptions and their additional workload
Collection design Consent and blocking affect what is observed

Do not equate server requests, visitors and tracked actions. A blocked analytics request is absent from this system even if the page was served. Budget from an observed tracking sample and document the known gaps.

Account for archiving work

Matomo’s requirements provide starting recommendations, while automatic archiving guidance explains background report processing. The application serving the dashboard and the jobs calculating its reports compete for resources unless the architecture addresses that.

A site with a moderate traffic count can still produce expensive reporting work through complex segments or broad historical queries. Capture the reports people use and when they run. Test the busy reporting period and a historical rebuild; a quick dashboard after cached results exist is not the whole workload.

Separate raw logs and reports

The retention documentation distinguishes deleting historical data and processed reporting. Decide what must be retained for the actual purpose and who approves deletion. Once detailed records are gone, some future analyses may be impossible even if summary reports remain.

For illustration, shortening raw retention from twelve months to three changes the period kept, but does not prove a 75% reduction in the whole installation. Reports, indexes, temporary operations, backups and other data remain. Deletion may also not immediately return allocated database storage to the provider.

Include the parts outside the server

Tracking implementation, event definitions, consent configuration and data-quality checks need owners. Premium plugins, upstream support and integrations should be separate quote lines where required. Confirm the selected versions and licences before carrying a feature assumption into a budget.

Migration from another analytics system may preserve only some history or metrics. Sessions, attribution and user definitions can differ. Plan a comparison period and explain discontinuities rather than presenting charts from two systems as an uninterrupted series.

Use the model for two decisions

The first decision is full replacement: current subscriptions and labour versus a new stack with migration, hosting, operation and retained tools. The second is incremental operation when an existing estate already has capacity. Keep those views separate and do not count an employee’s released time as cash unless spending actually changes.

The live calculator uses Pilae pricing for the service basis. Its output needs a capacity estimate and confirmed feature requirements. Do not assume a particular traffic volume fits an entry plan without reviewing action count, reports and growth.

Acceptance and recovery

Verify events against a controlled journey, check duplicate collection and test access to reports with appropriate roles. Back up the database and configuration, then restore into an isolated environment. Validate scheduled archiving and alert when jobs stop, because a responding website can still display stale analytics.

The Google Analytics migration guide covers a specific transition. Bring the measurement plan, traffic sample and required reports to estimate the operating scope. The useful outcome is dependable measurement at an understood cost, not a larger number in a dashboard.

Sources and further reading

Use the linked documentation to confirm the version, edition and contract that apply to your project.

Plan our analytics deployment

Bring your current bill, required capabilities and workload assumptions. We will separate recurring operation from migration and retained services.