Should you run self-hosted Matomo or pay for Matomo Cloud?
Matomo On-Premise is free to run with unlimited users and hits, but you supply the servers, patching and backups. Matomo Cloud replaces that work with hit-based plans starting at 29 (excluding tax) per month, with Cloud data stored in Frankfurt, Germany. Self-hosting tends to win when your monthly pageviews are high enough that Cloud tiers become costly, when policy requires analytics data to stay in infrastructure you control, or when you already have PHP and MySQL operations staff. Cloud tends to win when traffic is modest, when no one can patch a web server, or when Frankfurt hosting satisfies your data location rules.
Self-hosting cost is mostly labor and infrastructure, and it recurs every month. 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 app and database servers with 8 CPUs and 16 GB of RAM each for up to 10 million pageviews a month. Treat these as vendor minimums and ask your cloud provider to price instances, storage growth and backups against your own traffic. Cloud cost climbs with the hit tier, so compare the tier you would need in your peak month with server and staff hours. Premium plugins add a separate line on either path. Heatmap and Session Recording is licensed per number of users under the InnoCraft EULA, with a 30-day free trial, so confirm its terms and availability on each model before you budget.
Control and compliance often decide the question before cost does. A self-hosted install keeps analytics data on infrastructure you choose, but you then own upgrades. Matomo 5.14.1 is the latest stable version in the changelog, and Matomo 6.0.0 is in beta, requiring PHP 8.1 or newer and MySQL 8.0 or newer or MariaDB 10.6 or newer, so check your stack before planning. Consent also depends on features, not hosting: CNIL's exemption is lost once User ID, heatmaps or session recordings are added, so those sites need a consent banner on either model. Before deciding, ask your data protection officer whether Frankfurt storage meets your transfer rules, confirm who applies upgrades on Cloud, and pilot server sizing against your monthly pageviews.
Matomo On-Premise and Matomo Cloud compared factor by factor
This table compares Matomo On-Premise and Matomo Cloud across license, price, limits, hosting, server needs, version support, plugins, Google Analytics import and upgrades. Rows marked for confirmation depend on Cloud terms that can change, so check them with Matomo before you decide.
| Factor | Matomo On-Premise (self-hosted) | Matomo Cloud |
|---|---|---|
| License | GPLv3 source license; the Community edition is free to run on your own servers | Hosted service under Matomo's Cloud terms; confirm current terms with Matomo |
| Price model | Free Community edition; your costs are servers, storage, administration and any premium plugins | Plans from 29 (excluding tax) per month, per the Matomo pricing page; confirm current pricing with Matomo |
| User and hit limits | Unlimited users and hits on the Community edition | Tiers from 50,000 to 10 million hits a month; confirm current tier limits with Matomo |
| Hosting location | Wherever you deploy it, including your own data center or EU region | Cloud data stored in Frankfurt, Germany; confirm data residency and sub-processors with Matomo |
| Server requirements | You size the stack: a single server with 4 CPUs, 8 GB RAM and 250 GB SSD for up to 1 million pageviews a month, per Matomo's requirements FAQ | None on your side; Matomo runs the infrastructure |
| Matomo version support | You choose the version and timing; Matomo 6.0.0 needs PHP 8.1 or newer and MySQL 8.0 or MariaDB 10.6 or newer | Matomo manages the version; confirm which versions and upgrade windows apply to your plan |
| Premium plugin availability | Paid plugins such as Heatmap and Session Recording are sold per user under the InnoCraft EULA, with a 30-day free trial | Confirm with Matomo which premium plugins are available on each Cloud plan and how they are billed |
| Google Analytics import | Free Google Analytics Importer plugin under GPL v3+; imports aggregated reports only | Confirm with Matomo whether the importer is available and what it imports on Cloud |
| Upgrade responsibility | Your team or partner plans, tests and applies upgrades, backups and PHP and database changes | Matomo handles platform upgrades; confirm what you must still change on your side, such as tags and consent settings |
Which hosting model fits your traffic and team
When a site sends modest traffic and nobody on the team wants to patch PHP, manage MySQL backups or watch disk usage, Matomo Cloud usually removes the most work. The Cloud plans start at 29 (excluding tax) per month and are tiered by hits per month, from 50,000 up to 10 million, so the cost scales with the traffic you actually send. The On-Premise edition is free, but the server, its storage, its backups and your staff time are your cost. For a small site, those recurring costs can exceed the subscription.
- Predictable operations: Cloud handles hosting, updates and scaling within the plan you pick.
- Visible recurring cost: the subscription is the main line item, and it grows with hits.
- Free software, real labor: On-Premise has no license fee, but someone must run the server and apply upgrades.
- Tier boundaries: check how close your monthly hits sit to a tier limit before you commit.
Confirm current Cloud pricing, tier limits and tax treatment on the Matomo pricing page before you budget.
When traffic grows into the millions of pageviews a month and you already run a platform team, self-hosting can make economic and operational sense. 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. For up to 10 million pageviews a month, it recommends separate app and database servers with 8 CPUs and 16 GB of RAM each. Your team then controls scaling, retention and data pipelines, but also carries the hardware bill and the on-call load.
- Sizing tiers: the FAQ gives single-server and split-server guidance by monthly pageviews.
- Existing skills: the team needs MySQL or MariaDB administration, PHP upgrades and web server management.
- Premium plugins: InnoCraft plugins are licensed under the InnoCraft EULA on each model where they apply, so check their terms for your deployment.
- Upgrade cadence: Matomo 6.0.0 is in beta and needs PHP 8.1 or newer, so plan testing time.
Ask your Matomo partner or InnoCraft for a written view of which premium plugins are licensed for your self-hosted setup and how they are priced.
Matomo Cloud stores data in Frankfurt, Germany. If your rules require data to stay in a different country, or inside a network you control, Matomo Cloud does not meet that need on its own, and On-Premise becomes the default path. Self-hosting lets you choose the region, the cloud account or the data center, and keep logs and backups inside the same boundary. The trade-off is that you own access control, encryption, backup testing and the audit evidence for the hosting environment.
- Location control: On-Premise runs wherever your infrastructure is, including air-gapped networks where the stack allows it.
- Cloud limit: Cloud data is stored in Frankfurt, which may not suit every residency rule.
- Evidence ownership: you produce the access logs, change records and backup restore results.
- Third-party components: list every external service the tracking code or plugins call.
Confirm the residency requirement with your legal or privacy team in writing before choosing, and verify the Frankfurt storage location with Matomo directly.
Heatmaps and session recordings are not part of the free On-Premise core. 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 includes a 30-day free trial. Whether you run it on Cloud or On-Premise, the price depends on the license terms that apply to that model, so the hosting choice does not remove the cost. Recordings also change your privacy position, since the CNIL guidance says that adding heatmaps or session recordings removes the consent exemption for audience measurement.
- Per-user pricing: the plugin is priced by the number of users, so ask how users are counted.
- Trial period: the 30-day free trial lets you test the feature before buying.
- Consent impact: heatmaps or recordings may require a cookie banner even on a configuration that otherwise qualifies for an exemption.
- Model-specific terms: confirm whether the license differs between Cloud and self-hosted deployments.
Get the current plugin price and license scope in writing from InnoCraft, and have your privacy lead review the consent position before you enable recording.
How data location and control change your compliance position
Matomo Cloud and a self-hosted Matomo install put the same analytics data under different controls. The cards below cover where data sits, who can reach it, who runs backups and patches, how the consent exemption behaves, and which contract terms you must confirm before you collect anything.
Data location is a fixed choice
Matomo Cloud stores data in Frankfurt, Germany, and that location is not something you pick per tenant. A self-hosted Matomo runs in whatever region and facility your own cloud account, data center or network provides. If your policy requires a specific country or a non-EU location, self-hosting is the path that allows it. Confirm with Matomo where backups and support access sit, since those copies can live outside the primary region.
Administrative access and who holds keys
On Matomo Cloud, Matomo's operations staff control the servers, database and hosting configuration, and you control only the Matomo application settings and user accounts. On a self-hosted install, your administrators hold root access, database credentials and the encryption and backup keys. That gives you tighter control and a smaller third-party access footprint, but it also makes your team the only party who can recover a broken instance. Document who holds each credential and how access is logged.
Backups and patching move to your team
Matomo Cloud handles hosting, platform patching and infrastructure backups under the terms of your agreement. Self-hosting shifts those duties to you: nightly database and file backups, restore tests, OS and PHP patching, and a tested path to each Matomo release. Matomo's requirements FAQ also changes the stack over time, for example Matomo 6.0.0 needs PHP 8.1 or newer and MySQL 8.0 or newer or MariaDB 10.6 or newer. Ask who owns each patch window and how restores are verified.
Consent exemption limits
France's CNIL recognizes some audience measurement trackers as exempt from consent when they stay limited to performance measurement, collect only anonymous statistics and exclude marketing measurement. Matomo's ePrivacy FAQ says that adding User ID, heatmaps or session recordings removes that exemption. This applies to both deployment models, so the hosting choice does not change the consent rule. Configure the exemption on purpose, and review it whenever a team enables a heatmap or session recording plugin.
Confirm DPA and sub-processor terms
Before you send visitor data to Matomo Cloud, confirm the data processing agreement, the list of sub-processors, the transfer mechanisms that apply and the breach notification terms. A self-hosted install usually removes Matomo as a processor for analytics data, but you still need records of any hosting provider or backup vendor you use. Ask Matomo for the current documents in writing and check them against your own records of processing activities.
Evidence comes from you and your auditor
DeployOpen can plan the self-hosted configuration, document the controls and prepare evidence such as access records, backup logs and patch history for a compliance assessment. DeployOpen does not issue audit reports, attestations or certifications. Independent auditors and certification bodies make those determinations. Ask Matomo what third-party reports it holds for Matomo Cloud, and ask your assessor which evidence each side of the choice must produce.
How much server you need at each pageview level
Matomo's requirements FAQ gives two sizing bands for On-Premise. A single server with at least 4 CPUs, 8 GB of RAM and 250 GB of SSD is the published starting point for up to 1 million pageviews a month. Above that, Matomo recommends separate application and database servers, each with 8 CPUs and 16 GB of RAM, for up to 10 million pageviews a month. Use these bands as the floor for a planning conversation, not a finished bill of materials. Your monthly pageview count is the first input, but it is not the only one. Compare the figure against the Matomo Cloud tier you would otherwise buy, since the hit-based plans start at 50,000 hits a month and run to 10 million, and that comparison is where the server decision becomes a cost decision.
Pageviews set the starting point, but three other factors move the server size. Archiving, which is the job that turns raw visits into the reports your team reads, consumes CPU and database time on a schedule you control, so confirm how often it runs and whether it overlaps with peak traffic. Retention determines how fast the database grows, and the 250 GB SSD figure assumes a retention policy you have not yet set. Premium plugins such as Heatmap and Session Recording add load and storage of their own. Ask Matomo whether the plugin mix you intend to run changes the band you land in. If you plan to run Matomo 6.0.0, note that it is currently in beta and needs PHP 8.1 or newer and MySQL 8.0 or newer, or MariaDB 10.6 or newer, so check those versions against your operating system support policy before you size hardware around them.
For workloads outside these bands, including very high pageview counts, many sites on one instance, or heavy session recording, do not extrapolate from the two published tiers. Ask Matomo for a sizing estimate in writing and have your platform team test archiving duration on a copy of your own traffic. Record the results so the sizing decision can be revisited when traffic grows. Current Matomo version details are published in the Matomo changelog, and the sizing guidance itself sits in the Matomo requirements FAQ, which should be the reference for any quote you request.
What your team runs in each hosting model
This table shows who performs each operational task under Matomo On-Premise and Matomo Cloud. Read each row as a question of ownership: if your team would carry the task, the self-hosted column applies, and if the vendor carries it, the Cloud column applies. Confirm the exact responsibilities in writing before you sign.
| Task | Self-hosted Matomo On-Premise | Matomo Cloud |
|---|---|---|
| Web server and PHP runtime | Your team selects and runs Apache, Nginx, IIS or LiteSpeed on PHP 8 for Matomo 5, or PHP 8.1 or newer for Matomo 6.0.0 | Matomo hosts and operates the runtime in Frankfurt, Germany |
| MySQL or MariaDB | Your team installs and tunes MySQL 8.0 or newer, or MariaDB 10.6 or newer, for Matomo 6.0.0 | Matomo operates the database layer as part of the hosted service |
| Backups and restore testing | Your team designs, schedules and tests backups of both the application and database, and owns recovery time | Confirm with Matomo what backup frequency, retention and restore process apply to your plan |
| OS and security patching | Your team patches the operating system, web server, PHP and database on its own schedule | Matomo maintains the underlying platform; confirm the patch notification process in your contract |
| Matomo version upgrades | Your team plans, tests and applies upgrades, including checks against the requirements for each release | Matomo applies platform upgrades; confirm timing, notice and any change windows for your tier |
| Archiving jobs | Your team configures and monitors scheduled archiving so that reports stay current as traffic grows | Matomo runs archiving as part of the hosted service; confirm report freshness expectations for your plan |
| Monitoring and capacity planning | Your team monitors CPU, RAM, disk and database load, and resizes servers as pageviews grow | Matomo tracks capacity against your plan's hit tier; you move up a tier when your hits exceed it |
| Premium plugin licensing administration | Your team buys, installs, updates and renews premium plugin licenses, and tracks per-user terms where they apply | Confirm with Matomo how premium plugins are billed, enabled and renewed on your cloud plan |
| Support channel | Community forum support on a free edition, with no vendor support contract included | Vendor support through Matomo, with the channels and response terms set by your plan |
Moving between self-hosted Matomo and Matomo Cloud
This sequence moves analytics in either direction, keeping site configuration, consent settings and historical data intact. It ends with a tracked cutover, a documented variance check and a read-only archive of the instance you left.
Export or confirm site and user configuration
The current administrator lists every website and site ID, along with goals, ecommerce settings, custom dimensions, segments, scheduled reports, user accounts, roles and installed plugins. On self-hosted Matomo this comes from the admin screens and the database. On Matomo Cloud, the account owner confirms the inventory with Matomo. Confirm whether each premium plugin license covers the destination, because a plugin licensed for one setup may not transfer. Matomo Cloud plans start at 29 per month (excluding tax), with tiers set by monthly hits, so note the traffic tier you need. Done when the inventory is written down and every paid plugin is matched to a license decision.
Confirm what data export Matomo supports
Before committing, ask Matomo which export routes exist for raw visit data, aggregated reports and archives, and in what formats. Do not assume a full export is available without written confirmation. Also note the Google Analytics importer limit: it brings in aggregated report data only, so the Visitor Log, Ecommerce Log, Custom Reports and Segmentation do not work for imported reports, and some reports such as Funnels are not imported. Done when Matomo's written answer is filed with the migration plan and each report the business relies on is marked as kept, rebuilt or retired.
Plan the tracking code change
Each site uses a tracking snippet that points to one Matomo host and one site ID. Developers list every template, tag manager container and single-page app that loads the snippet, then set the new host and the site ID for the destination. Test the new snippet in staging before any production change. Note that Matomo Cloud data is stored in Frankfurt, Germany, which should be checked against your data residency requirements at this stage. Done when the change request names every page and tag container affected, and staging shows hits arriving in the new site.
Decide how to handle historical data
Choose whether to keep the old instance online as a read-only archive, bring aggregated history into the new site, or start fresh while retaining the old data elsewhere. The appropriate option depends on what Matomo confirmed in the export step. Record the retention decision with your data protection lead, because old visit records may hold personal data that falls under your retention rules. Done when a signed-off decision states where the archive lives, who can access it and how long it is kept.
Run both instances in parallel
Keep the old and new installations collecting for an overlap period you set, then compare visits, pageviews, goals and ecommerce totals for the same dates. Expect small gaps, since ad blockers, consent choices and tag timing differ between setups. On self-hosted Matomo, check capacity against Matomo's sizing guidance: a single server for up to 1 million pageviews a month needs at least 4 CPUs, 8 GB of RAM and 250 GB of SSD, and Matomo recommends separate app and database servers with 8 CPUs and 16 GB of RAM each for up to 10 million pageviews a month. Done when the variance is documented and falls within the tolerance the business agreed.
Verify reports and consent settings
Check that reports, segments, scheduled emails, user permissions and goals match the inventory from the first step. Review consent configuration on the new install. Matomo's ePrivacy guidance says that under CNIL rules some trackers are exempt from consent only when they are limited to performance measurement, collect anonymous statistics and exclude marketing measurement. Adding User ID, heatmaps or session recordings removes that exemption. Confirm the setting that applies to each authority covering your visitors. Done when the analytics owner and privacy lead sign a checklist covering each report, role and consent setting.
Cut over and freeze the old instance
Switch tracking to the new endpoint on an agreed date, remove the old snippet from every template and tag container, and stop collection on the old site. Keep the old instance reachable in read-only form for the retention period set earlier. Watch the first days of data for missing hits or duplicate counts. Done when the old tracking code is confirmed absent from production pages and someone other than the person who set up the archive has tested access to it.
Questions buyers ask before choosing a hosting model
How much does self-hosting Matomo cost compared with Matomo Cloud?
Self-hosted Matomo On-Premise Community carries no license fee, so your cost is the infrastructure, storage, backups, monitoring, staff time for upgrades and incident response, and any premium plugins. Matomo's pricing page lists Matomo Cloud plans starting at 29 (excluding tax) per month for the tier covering 50,000 hits a month, with higher tiers up to 10 million hits a month. In Cloud, the recurring cost is the subscription and plugin fees. In self-hosting, most recurring cost is people and hosting, and setup and hardening are one-time costs. When you request a quote from an implementation partner, ask for the written scope, the server specification, the hosting location, the backup and monitoring scope, the expected upgrade effort per year, and a separate line for each premium plugin, priced per user. Confirm your own infrastructure rates before comparing totals.
How much server capacity and skill does self-hosted Matomo need?
Capacity depends on monthly pageviews. Matomo's requirements FAQ sizes the following:
- Up to 1 million pageviews a month: one server with at least 4 CPUs, 8 GB of RAM and 250 GB of SSD storage.
- Up to 10 million pageviews a month: separate application and database servers, each with 8 CPUs and 16 GB of RAM.
The software stack also has minimum versions. Matomo 6.0.0 needs PHP 8.1 or newer and MySQL 8.0 or newer or MariaDB 10.6 or newer, and it is currently in beta, while the latest stable release is 5.14.1. Matomo 4.16 and 5 run behind Apache, Nginx, IIS or LiteSpeed. Your team needs skills in the web server, PHP tuning, database administration, TLS, backups and restores, and monitoring. Check the Matomo requirements FAQ against your target version before sizing.
Can an in-house team run self-hosted Matomo on its own?
An in-house team can run Matomo alone when it already operates PHP, MySQL or MariaDB, and web servers, and it has the time for patching, upgrades, restore tests and on-call coverage. The Community edition includes forum support only, according to Matomo's pricing page, so vendor-backed help is not included in the free edition. Check three things before you commit: whether two people can cover absences, whether you have tested a full restore, and whether someone owns the premium plugins, which are licensed per user under the InnoCraft EULA. If the team lacks one of these, a fixed-scope engagement can cover planning, implementation, hardening, backups, upgrades, documentation and support, and ongoing support can run as a retainer. DeployOpen does this inside your own cloud account, data center or air-gapped network, and the written scope defines what it covers.
How long does a migration from Matomo Cloud to self-hosted Matomo take?
No migration duration is set in the sources for this page, so confirm the timeline with Matomo and with the implementation partner against your own environment. The main drivers are the amount of historical data you need to keep, the number of sites and goals, custom reports and segments, which premium plugins you use, changes to the tracking code and tag deployment, DNS and TLS cutover, and how much parallel running you want before switching. Ask Matomo what export options exist for historical data and what they include, because that determines how much history survives the move. Ask the partner for a written scope with named deliverables, a test restore, a cutover plan and a rollback path. A fixed-scope agreement makes the timeline and deliverables explicit before work starts.
Does Matomo Cloud hosting in Frankfurt satisfy data residency rules?
Matomo's pricing page states that Matomo Cloud data is stored in Frankfurt, Germany. That tells you where the data sits, but whether this meets your residency, transfer, processor and sub-processor obligations is a legal determination for your counsel and data protection officer. Request Matomo's data processing agreement, its list of sub-processors, the locations of its backups and its incident notification terms, and compare them with your register of processing activities. Self-hosting in your own cloud account, data center or air-gapped network keeps location and access under your control, but it moves the security and operating obligations to you. Consent rules apply to both models: Matomo's ePrivacy FAQ says adding User ID, heatmaps or session recordings removes the CNIL consent exemption. DeployOpen prepares systems, controls and evidence for compliance assessments, but independent auditors and certification bodies issue the reports.
How do upgrades differ between Matomo Cloud and self-hosted Matomo?
On Matomo Cloud, the vendor runs the platform, so you should confirm the upgrade schedule, the advance notice, whether you can defer a version and how plugin compatibility is handled. In self-hosting, you choose the version and the timing, test plugins and custom code, check PHP and database minimums, take a backup, apply the upgrade and keep a rollback path. Matomo's changelog lists 5.14.1 as the latest stable release, released October 4, 2026, and Matomo 6.0.0 in beta since September 9, 2026. A major version can raise runtime and database minimums, so upgrades may also require operating system, PHP or database changes. Those tasks recur every release cycle and need someone accountable. DeployOpen offers upgrades as part of its platform services, and ongoing upgrades are available as a retainer under a written scope.
At what traffic level does self-hosting Matomo pay off?
No break-even figure is supplied for this comparison, so build your own model from your monthly hits and the quotes you receive. Matomo Cloud pricing rises in tiers from 50,000 to 10 million hits a month, while self-hosting costs are mostly a fixed infrastructure base plus staff time, so self-hosting becomes relatively cheaper as volume grows, provided you already have operations capacity. Matomo's sizing guidance gives two anchors: a single server for up to about 1 million pageviews a month, and separate application and database servers for up to about 10 million. Below the lowest Cloud tiers, the subscription is small and self-hosting rarely wins on cost alone. Other reasons to self-host include data control, unlimited hits on the free edition and the option to run custom code. Compare the two totals at your actual traffic, including plugins and upgrade labor.
When self-hosting Matomo starts to pay off
Self-hosting Matomo pays off when the cost of running it stays below the cost of the Cloud tier your traffic would need. On-Premise has no license fee, since Matomo's pricing page lists the Community edition as free forever with unlimited users and hits. The bill arrives elsewhere: servers, storage, backups, monitoring, and the staff time to apply upgrades to PHP, the database and Matomo itself. Matomo Cloud plans start at 29 per month (excluding tax), and the price steps up through tiers from 50,000 to 10 million hits a month. Cloud cost therefore rises in steps with traffic, while self-hosting cost rises in steps with the infrastructure you add. The break-even point is where those two curves cross for your own volume, not a figure you can take from a table.
Several factors tip the balance. The first is your traffic band. 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 app and database servers with 8 CPUs and 16 GB of RAM each for up to 10 million. If you already run hosting with that capacity, the marginal cost of Matomo is lower. Control requirements matter too: Cloud data is stored in Frankfurt, Germany, while On-Premise data stays wherever you place it. Premium plugins can change the result. The Heatmap and Session Recording plugin is sold per number of users under the InnoCraft EULA, so confirm its fee and terms for each deployment before you count it as a difference between them.
Model your own numbers before deciding. Measure monthly pageviews and confirm how Matomo Cloud counts hits against your tier. Then price each option against your scope, including plugin licenses, hosting and who performs upgrades. Matomo 6.0.0 has been in beta since September 9, 2026, while the latest stable release is 5.14.1, released October 4, 2026, and 6.0.0 requires PHP 8.1 or newer and MySQL 8.0 or newer or MariaDB 10.6 or newer. Ask the vendor for a quote covering each option. DeployOpen does not publish a price list, but its quotes follow a written, fixed scope that can cover hosting, hardening, backups and upgrades for a self-hosted Matomo.
How DeployOpen scopes and supports self-hosted Matomo
DeployOpen plans, implements, hardens, backs up, upgrades, documents and supports self-hosted open-source platforms inside the client's own infrastructure. For Matomo, that means working from your own traffic levels, premium plugin needs and consent obligations to define an install you can run, or a clear case for staying on Matomo Cloud.
How we scope
- Engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts.
- The written scope states expected monthly pageviews, server layout, database version and the premium plugins you intend to license.
- Scope also records which tracking features, such as heatmaps or session recordings, affect your consent position under the rules you follow.
How we build
- Build covers server sizing, PHP and MySQL or MariaDB configuration, and the web server stack in your own cloud account or data center.
- Premium plugin installation, licensing setup and any Google Analytics import are scoped as separate deliverables with their own testing.
- Testing includes tracking verification, backup and restore checks, and a documented upgrade path to the next Matomo release.
How we hand over
- Handover includes written runbooks for installation, upgrades, backups, plugin updates and the configuration used for consent decisions.
- Documentation records the hosting location of analytics data so your privacy and compliance team can review it directly.
- We prepare the configuration, settings and evidence your compliance assessors may ask for, without issuing any audit report or certification.
How we support
- Ongoing support, upgrades and continuous testing are available as retainers, scoped separately from the build.
- Retainers can cover Matomo core upgrades, plugin updates and periodic restore tests against your documented backups.
- Ask any quote to name who patches the server, who holds the license keys and who responds when a release changes requirements.
