Matomo vs Plausible: when to choose each
Your situation is usually one of two. You are replacing Google Analytics and need years of history, ecommerce reporting and a broad set of reports for marketing and product teams, or you are running analytics in-house under a privacy or compliance brief and want the smallest system that answers a short list of questions. Matomo fits the first situation and Plausible Community Edition fits the second. Matomo's On-Premise edition is free under GPL-3.0 with unlimited users and hits, and it covers the full report set, ecommerce and goals. If you need the Google Analytics history, the Google Analytics Importer plugin is free for On-Premise, but it imports aggregated reports only, so the Visitor Log, Ecommerce Log, Custom Reports and Segmentation do not work for imported data and some reports such as Funnels are not imported. Premium plugins such as Heatmap and Session Recording are paid and sold under the InnoCraft EULA, so choose Matomo if your team accepts that a second license sits next to the GPL core.
Plausible Community Edition fits a smaller set of pages and goals, a preference for a lightweight stack (Docker, Docker Compose and ClickHouse, with at least 2 GB of RAM), and an operator who will apply each release. Plausible's own page says Community Edition is released twice a year, is community supported only, and gets security fixes only when you apply the release. The Community Edition also leaves out marketing funnels, user journeys, ecommerce revenue goals, single sign-on, the Sites API, the Looker Studio connector and advanced bot filtering. Plausible's Google Analytics import brings in daily aggregates, cannot import ecommerce revenue, and supports up to 5 GA properties per site, so confirm that these limits do not cover your reporting needs before you commit.
The decision turns on five questions. First, how deep must reporting go, and do you need ecommerce or funnel analysis? Second, do you need a consent-exempt setup under the rules of your supervisory authority, and does any planned feature such as User ID, heatmaps or session recordings change that answer? Third, who owns upgrades, backups and security patches, and is that person named in your runbook? Fourth, which paid features will you miss in the community edition and is that acceptable for the next three years? Fifth, which version and PHP or ClickHouse requirements apply on the day you install, which you should confirm against the current Matomo requirements FAQ and the Plausible Community Edition repository before you size hardware.
Which platform fits which scenario
This table matches common buyer situations to the platform that fits them better and names the condition under which the other one still makes sense. Read each row as a decision rule, then check the feature gaps against your own requirements before committing.
| Scenario | Better fit | Reason and exception |
|---|---|---|
| Marketing team needs ecommerce revenue reporting | Matomo | Matomo's full suite covers ecommerce reporting, while Plausible Community Edition does not include ecommerce revenue goals. Exception: if revenue reporting is only a small part of the need, confirm whether a Plausible Cloud plan would be a better match for that gap. |
| Privacy-led site that wants no cookie banner | Plausible | Plausible's design uses no cookies, so no cookie banner is required under its own description. Matomo can be configured to be consent-exempt in some EU regimes, but adding User ID, heatmaps or session recordings removes that exemption. Confirm the rules with your regulator and counsel. |
| Team importing years of Google Analytics history | Matomo | Matomo's importer is a free GPL plugin for On-Premise that brings in report data, but Visitor Log, Ecommerce Log, Custom Reports and Segmentation do not work for imported data and some reports such as Funnels are not imported. Plausible imports GA4 history as daily aggregates, supports up to 5 GA properties per site, and cannot import ecommerce revenue, so it fits when page-level trend history is enough. |
| Small site run by one operator | Plausible | Plausible Community Edition needs Docker, Docker Compose and at least 2 GB of RAM, and its stack is narrower to run. Exception: Matomo's single-server sizing suits low traffic too, so pick Matomo if you need its wider reporting and already run PHP and MySQL. |
| Team needing single sign-on | Matomo | Plausible's self-hosted page lists single sign-on among features missing from Community Edition compared with Plausible Cloud. Confirm what Matomo's On-Premise edition supports for your identity provider before assuming parity. Exception: if SSO is not required, this row does not decide the choice. |
| Team that needs funnels or user journeys | Matomo | Plausible's self-hosted page lists marketing funnels and user journeys as missing from Community Edition. Confirm the exact Matomo features you need in its documentation before you decide. |
| Team that wants security fixes applied quickly | Matomo | Plausible Community Edition is a long-term release published twice per year, is community supported only, and gets security fixes only when the operator applies the release. Matomo's changelog shows frequent releases, but confirm your own patch process for either platform. Exception: a team with a tested monthly patch cycle can run either safely. |
| Team that wants a hosted option with fewer operations | Plausible | Plausible Cloud ships updates multiple times per week and Community Edition users can export and import data to and from it. Exception: if you need Matomo's full reporting in a hosted setup, Matomo Cloud also exists, so compare hit tiers and data location. |
How each platform is built and what that means for operations
Matomo and Plausible Community Edition both run on a single application stack that the operator owns, but they differ in language, database, and how much of the upkeep falls to the team. The cards below cover the stack, the server layout, the duties Plausible hands to the operator, and the update cadence, so the person on call knows what they will be paged for.
Matomo runs on PHP and MySQL
Matomo is a PHP application served through a web server such as Apache, Nginx, IIS or LiteSpeed, with MySQL or MariaDB as its database. For the 6.0.0 line, which is in beta, the requirement is PHP 8.1 or newer and MySQL 8.0 or newer or MariaDB 10.6 or newer. On call, the usual failures sit in PHP-FPM, the web server and the database, so the team needs people who already run that stack. Check the version floor before you plan a 6.x upgrade.
Plausible runs on Docker Compose and ClickHouse
Plausible Community Edition is deployed with Docker and Docker Compose and stores events in ClickHouse, a columnar database that the CPU must support through SSE 4.2 or NEON. The repository asks for at least 2 GB of RAM. On call, the team works with container restarts, volume health and ClickHouse storage rather than a traditional PHP stack, so Docker and ClickHouse knowledge matters more than PHP knowledge.
Single server or split app and database
Matomo's requirements FAQ sizes one server for up to 1 million pageviews a month and recommends separate app and database servers for up to 10 million. Splitting the tiers adds a network dependency and a second host to patch, back up and monitor. Ask whether your traffic will grow past the single-server band within the hardware life, because moving a live analytics database later is a planned outage, not a configuration change.
Operator duties Plausible hands over
Plausible states that Community Edition operators manage installation, upgrades, capacity, uptime, backups and security themselves. Nobody is paged on the vendor's behalf, so each of these six duties needs a named owner and a runbook before go-live. Confirm who restores from backup, who watches disk growth in ClickHouse, and who applies security releases within your own patch window.
Community Edition updates lag Cloud
Plausible describes Community Edition as a long-term release published twice per year, supported by the community only, and receiving security fixes only when the operator applies the release. Plausible Cloud ships updates multiple times per week. A security advisory on Community Edition therefore becomes your incident until the upgrade lands. Track the release feed, and test each upgrade in staging before the next advisory arrives.
Matomo upgrades follow your own schedule
Matomo On-Premise is a self-managed application, so the team decides when to move between releases and must check PHP and database floors at each step. Matomo's changelog lists 5.14.1 as the latest stable release, released on October 4, 2026, with 6.0.0 in beta. Plan the 5.x to 6.x move as a separate change with its own database and PHP prerequisites rather than folding it into routine patching.
How Matomo and Plausible differ on reports, ecommerce, goals and imports
This table compares Matomo and Plausible Community Edition on reporting depth, ecommerce, Google Analytics import, paid features, identity, API access, bot filtering, cookie consent and the self-hosting version each edition ships. Read each row against your own reporting needs, and treat any cell marked as a point to confirm as a question for the vendor before you commit. The main takeaway is that Matomo covers far more reporting ground on-premise, while Plausible keeps the self-hosted footprint small but leaves several capabilities to the paid Cloud.
| Capability | Matomo On-Premise | Plausible Community Edition |
|---|---|---|
| Reporting depth | Full analytics suite with visitor log, custom reports and segmentation on native data | Lightweight dashboard focused on core traffic metrics; marketing funnels and user journeys are Cloud-only |
| Ecommerce and goals | Ecommerce reporting and goals supported in the full suite; confirm current ecommerce features in your version | Ecommerce revenue goals are missing from Community Edition and available on Plausible Cloud |
| Google Analytics import | Imports aggregated report data only; Visitor Log, Ecommerce Log, Custom Reports and Segmentation do not work for imported data, and some reports such as Funnels are not imported | Imports historical GA4 stats as daily aggregates up to the first native visitor, up to 5 GA properties per site, but cannot import ecommerce revenue |
| Premium or paid features | Free On-Premise edition with unlimited users and hits; Heatmap and Session Recording is a paid plugin under the InnoCraft EULA | Community Edition is AGPLv3; marketing funnels, user journeys, ecommerce revenue goals and advanced bot filtering are missing compared with Cloud |
| Identity and single sign-on | Confirm SSO options and plugins for your deployment with the vendor before relying on them | Single sign-on is listed as missing from Community Edition; Google sign-in settings apply to the Search Console and GA4 import integration |
| Looker Studio or API access | Confirm API and export options for your reporting stack with the vendor | Looker Studio connector and Sites API are missing from Community Edition; confirm alternatives for your own reporting |
| Bot filtering | Confirm the bot-filtering settings available in your installed version | Advanced bot filtering is missing from Community Edition and listed as a Cloud feature |
| Cookie-consent position | Consent-exempt configuration possible under CNIL criteria; adding User ID, heatmaps or session recordings removes the exemption | Cookieless design, so no cookie banner is required according to Plausible's homepage; confirm the position with your data protection advisor |
| Self-hosting version shipped | Matomo 5.14.1 is the latest stable release (October 4, 2026); Matomo 6.0.0 is in beta | Community Edition v3.2.1 security release (May 15, 2026); Community Edition is published twice a year and gets fixes only when you apply them |
What each license allows and what the paid editions add
Matomo's repository is licensed under the GNU General Public License version 3 (GPLv3), and the free On-Premise edition carries no user or hit limits. Matomo Cloud is the paid hosted alternative, and its plans start at 29 per month (excluding tax) for tiers from 50,000 to 10 million hits a month, with data stored in Frankfurt, Germany. Premium capabilities are separate products, not a different edition of the core.
- On-Premise cost: The Community edition is free, with unlimited users and hits and forum support. Your costs are the servers, storage, backups and the staff time to run them.
- Matomo Cloud: Plans are hit-based and priced per tier, starting at 29 per month (excluding tax). Data sits in Frankfurt, which matters if your residency rules prefer EU hosting.
- Heatmap and Session Recording: This premium plugin is sold per number of users under the InnoCraft EULA, not the GPL, and includes a 30-day free trial.
- Google Analytics Importer: This plugin is free for On-Premise under GPL v3 or later, but it imports aggregated reports only.
Confirm with InnoCraft which premium plugins your use case needs, how per-user pricing scales for your staff, and whether the EULA terms permit your intended internal use before you build around them.
Plausible Community Edition is open source under the GNU Affero General Public License v3 (AGPLv3) or any later version. It is the self-hosted option, while Plausible Cloud adds features that the Community Edition does not include. Cloud plans start at 10k monthly pageviews, with the Starter, Growth and Business tiers listed at $9, $14 and $19 per month, plus custom Enterprise pricing.
- Missing from Community Edition: Marketing funnels, user journeys, ecommerce revenue goals, single sign-on, the Sites API, the Looker Studio connector and advanced bot filtering are Cloud features.
- Support model: Community Edition is community supported only. You get no vendor support channel for it.
- Update cadence: It is a long-term release published twice per year, and security fixes arrive only when you apply the release. Cloud ships updates multiple times per week.
- Data portability: Community Edition users can export and import data to and from Plausible Cloud, which helps if you later move to the hosted service.
- Operations: You own installation, upgrades, capacity, uptime, backups and security.
Confirm whether any Cloud-only feature is required by your reporting plans before you commit to the Community Edition, and confirm the current Cloud prices on the vendor's pricing page.
Both GPL-3.0 and AGPLv3 let you run, modify and redistribute the software, but they attach conditions to distribution and, in AGPL's case, to network use. In plain terms, if you distribute a modified copy, you must release the source under the same license. AGPL adds that if you modify the program and let users interact with it over a network, you must offer those users the modified source. Running an unmodified copy for internal staff generally triggers neither duty for the organization, but the answer depends on your facts.
- Internal use: Running either tool unmodified for your own analysts usually creates no source disclosure duty, though you should document that you did not modify the code.
- Modified and hosted for others: AGPL's network clause is the one to review if you change Plausible and expose it to customers, partners or the public.
- Plugins and themes: Check how custom code and premium plugins combine with the core, since their license terms may differ from the core license.
- Matomo premium plugins: These fall under the InnoCraft EULA, so GPL obligations for the core do not settle their terms.
- Trademarks and support: Licenses do not grant rights to vendor trademarks, so check branding terms before you rebrand a deployment.
Have your legal counsel review the license texts against your specific modifications, hosting model and any customer-facing use before you deploy.
What running each platform costs beyond the license fee
Both platforms are free to self-host, so the real cost is the infrastructure, the staff time to keep them running, and any paid add-ons. For Matomo On-Premise, the server cost follows traffic. Matomo's requirements FAQ sizes a single server at 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. Those figures are a starting point for sizing, not a quote: your own log volume, archiving schedule and retention period decide the disk footprint, so run a trial import of a representative month before buying hardware. Plausible Community Edition needs Docker, Docker Compose, a CPU with SSE 4.2 or NEON support for ClickHouse, and at least 2 GB of RAM. The stated minimum is not a traffic sizing, so ask Plausible to confirm the server size for your expected pageviews in writing before you budget.
Staff time is a recurring cost on both sides. The Plausible self-hosted page says Community Edition operators handle installation, upgrades, capacity, uptime, backups and security, and that security fixes arrive only when the operator applies a release. Matomo On-Premise has the same operator burden, plus database tuning and archiving jobs. Premium spend is the Matomo-specific line item: the Heatmap and Session Recording plugin is sold per number of users under the InnoCraft EULA, so it recurs with your team size. Plausible's paid features sit behind Plausible Cloud, and Cloud's Starter, Growth and Business plans start at $9, $14 and $19 per month, with custom Enterprise pricing. If you pick Cloud over self-hosting, you pay a subscription instead of servers and staff time.
One-time costs include the initial install, data migration, Google Analytics import work and any custom tagging or consent configuration. Recurring costs include servers or cloud subscriptions, staff hours for patching and backups, premium plugin renewals and any retainer for upgrades or monitoring. A written quote from DeployOpen or another provider should separate these lines and state the scope, including who applies security releases, how backups are tested, which Matomo or Plausible version is covered, what happens when traffic outgrows the server, and whether the Google Analytics import is included. Ask Plausible for its sizing guidance and any support terms for Community Edition, and ask InnoCraft for current plugin pricing for your user count.
Moving from Matomo to Plausible or back, step by step
This sequence moves measurement from one analytics tool to the other with a documented inventory, a clear view of which history comes across, and a parallel run that proves the new numbers match closely enough to retire the old tool. It produces a dated cutover record that your analytics owner and compliance lead can both sign.
Inventory goals, events, ecommerce and segments
The analytics owner lists every goal, custom event, ecommerce tracking call, saved segment, scheduled report and dashboard in the source tool, noting which team uses each one. Record the tracking code location on each site and any consent logic that gates it. Done means a single inventory document that maps each item to an owner and a decision: rebuild, replace or retire. Matomo's features such as Funnels and Custom Reports have no direct equivalent in Plausible Community Edition, so mark them now rather than discovering the gap at cutover.
Decide which history is worth keeping
Decide with the business owners how much historical data the new tool needs and whether that history is aggregated or raw. Matomo's Google Analytics Importer brings in aggregated report data only, so Visitor Log, Ecommerce Log, Custom Reports and Segmentation do not work for imported reports, and Funnels are not imported. Plausible's Google Analytics import brings in daily aggregates up to the first native visitor, cannot import ecommerce revenue, and approximates unique visitors by summing daily uniques. Done means a written retention decision for each report family, signed off by the business owner.
Rebuild tracking, goals and dashboards in the target
The implementation engineer installs the target tool, then recreates goals, custom events and dashboards in its own model. In Plausible Community Edition, ecommerce revenue goals are not available in the self-hosted build, so revenue tracking needs a decision before rebuild. Confirm the target's tracking script and consent behavior against your privacy review, since adding features such as User ID or session recordings can change how a tracker is treated under some EU rules. Done means a test site on the target receives events from a staging page and every rebuilt dashboard loads with the expected labels.
Run both tools in parallel and compare counts
Keep the source tool collecting while the target collects the same pages and events for a period your analytics owner agrees on. Compare pageviews, visits, goal completions and top pages side by side, and document where definitions differ, such as how each tool counts unique visitors and sessions. Expect differences, because the tools use different counting methods and blockers may affect each one differently. Done means a reconciliation sheet that lists each metric, the variance observed and the reason, approved by the business owner before cutover.
Export and migrate retained data
Where the target supports importing the history you chose to keep, run the import in a staging copy first and check totals against the source export. If you are moving between Plausible Community Edition and Plausible Cloud, use the documented export and import path, which the vendor describes as available in both directions. Confirm with the vendor which data types the path covers, because raw events and some settings may not transfer. Done means an import report with row or day counts matched against the source, and a list of data that did not transfer, kept with the archive.
Cut over and archive the source
Switch the production tracking script to the target, redirect any internal dashboards and scheduled reports, and notify report recipients of the new location. Keep the source instance read-only and backed up for the retention period your compliance lead requires, then decommission it. Note that Community Edition operators handle backups, upgrades and security patches themselves, so assign those tasks before the source is retired. Done means the production script is confirmed on live pages, the archive is verified, and the change record is signed by the analytics owner.
Matomo vs Plausible implementation: where projects run long
The longest part of a Matomo or Plausible project is rarely the install. Matomo On-Premise needs a web server such as Apache, Nginx, IIS or LiteSpeed, PHP 8 and MySQL or MariaDB, and the requirements differ by version: Matomo 6.0.0 needs PHP 8.1 or newer and MySQL 8.0 or newer or MariaDB 10.6 or newer, while Matomo 5 runs on older MySQL 5.5 or later. Plausible Community Edition is a Docker and Docker Compose deployment that also runs ClickHouse, which requires a CPU with SSE 4.2 or NEON and at least 2 GB of RAM. Each stack has its own patching and backup routine, and the upgrade path differs: Matomo is upgraded in place from its own release line, while Plausible Community Edition only receives security fixes when the operator applies a release. Matomo adds a plugin decision on top: the free Google Analytics Importer sits alongside paid premium plugins such as Heatmap and Session Recording, and each choice changes what the consent configuration must cover.
Consent work is where projects most often run long. Matomo's ePrivacy guidance states that features such as User ID, heatmaps or session recordings remove the CNIL consent exemption, so a plugin added after go-live can turn a consent-free setup into one that needs a banner. Plausible's cookieless design avoids that rework, but its Google integration is optional and set through GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET, and teams that enable it should confirm which tags and data flows their privacy notice describes. Tag manager containers, existing GA4 event names and any server-side tagging also need mapping before launch. Ecommerce is the other common gap: Plausible's import documentation says it cannot import ecommerce revenue, and Matomo's importer does not bring over the Ecommerce Log, so historical revenue reporting may need a separate export or a parallel report.
Sizing corrections and historical data mapping tend to surface after launch. Matomo's requirements FAQ sizes one server at 4 CPUs, 8 GB of RAM and 250 GB of SSD for up to 1 million pageviews a month, and recommends split app and database servers with 8 CPUs and 16 GB of RAM each for up to 10 million. Plausible's import brings historical GA4 data in as daily aggregates, supports up to 5 GA properties per site, and approximates unique visitors by summing daily uniques, so historical and native figures will not match exactly. Ask the vendor or check your own traffic before committing to a single-server layout. DeployOpen plans and implements either stack inside your own infrastructure, with consent configuration, import mapping, sizing and upgrade steps agreed in a fixed scope in writing before work begins.
Questions buyers ask before choosing Matomo or Plausible
Does Matomo or Plausible let us skip the cookie banner?
Plausible's design uses no cookies, so its own documentation says no cookie banner is required, but that statement describes the tool, not your site's legal position. Matomo can be configured to fall within the consent exemption some EU authorities recognize, and its ePrivacy FAQ names France, Italy, the Netherlands and Spain as authorities with such exemptions. The exemption depends on conditions: the tracker must stay limited to performance measurement, collect only anonymous statistics and exclude marketing measurement. Adding User ID, heatmaps or session recordings removes it. Confirm the current rules with your data protection officer and read the separate consent comparison before deciding.
How much effort does self-hosting Matomo or Plausible take?
Both are self-hosted tools, so your team owns installation, upgrades, capacity, uptime, backups and security. Plausible's self-hosted page says Community Edition operators manage all of these themselves, and its Community Edition gets security fixes only when the operator applies a release. Matomo On-Premise follows a similar split, but its stack is PHP and MySQL behind a web server, which most platform teams already run. Matomo's requirements FAQ sizes a single server for up to 1 million pageviews a month, and recommends separate app and database servers beyond that. Effort rises with traffic, the number of sites and how often you patch. Ask for the upgrade cadence and the maintenance window your team can commit to.
Can our internal team run the analytics platform without an outside partner?
Yes, if you have a named operator who can handle Docker and ClickHouse for Plausible, or PHP, MySQL and web server administration for Matomo, plus someone who watches security releases. Plausible Community Edition requires Docker and Docker Compose, a CPU with SSE 4.2 or NEON support for ClickHouse, and at least 2 GB of RAM. Matomo's support for On-Premise is forum-based, so vendor-backed help is limited unless you buy a support route. Teams without spare capacity often engage an implementation partner for the first install, hardening, backup testing and upgrades, then run the platform internally. DeployOpen works this way on fixed-scope engagements, and ongoing support is available as a retainer.
How long does a migration to Matomo or Plausible take?
The duration depends on the number of sites, the tag changes across your properties, the volume of history you want to keep, and how many reports your teams rely on. Start by listing which reports, goals and ecommerce data must survive, because each platform handles imports differently. Testing tracking on a staging site, validating dashboards against the old tool for a parallel period and updating consent settings all add time. No supplied timeline applies to your environment, so ask any vendor or partner for a written scope with named deliverables before committing to a date.
Can we keep our Google Analytics history, and what is lost?
Both tools import some history, but neither keeps everything. Matomo's Google Analytics Importer, a free plugin for On-Premise, imports aggregated report data into a new site. Its FAQ states that raw visit and action data is not imported, 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. Plausible imports historical GA4 stats as daily aggregates up to the first native Plausible visitor, supports up to 5 GA properties per site, cannot import ecommerce revenue, and approximates unique visitors by summing daily uniques. Export your GA data before you cut over, and confirm each report you need against the import documentation.
What does the migration need from our organization?
The work needs access, approvals and named people, more than it needs budget decisions at the start. Expect to provide the following:
- Administrative access to the hosting environment, the existing analytics account and the site tag management system.
- A data owner for each site who signs off on which reports and history must carry over.
- An approver for consent and privacy settings, usually legal or the data protection officer.
- A named operator who will own upgrades, backups and incident response after handover.
Without these, cutover dates slip. Agree the list in the written scope before work starts.
Which self-hosted option removes features we might need later?
Plausible Community Edition leaves out marketing funnels, user journeys, ecommerce revenue goals, single sign-on, the Sites API, the Looker Studio connector and advanced bot filtering, according to its self-hosted page. Matomo On-Premise is free with unlimited users and hits, but its premium plugins, such as Heatmap and Session Recording, are paid under the InnoCraft EULA and priced per number of users. If ecommerce revenue or single sign-on matter to you, confirm whether they are in scope before choosing. Also check the cost of Cloud for comparison, since moving data between editions is possible but adds work.
How DeployOpen helps teams choose, implement or migrate between them
DeployOpen is a Chainscore Labs company that plans, implements, hardens, backs up and documents self-hosted open-source platforms inside the client's own infrastructure. For Matomo vs Plausible, we start from the reporting, consent and hosting requirements your team has already written down, then work out which platform fits them.
How we scope
- We confirm which reports, ecommerce or goal tracking, and Google Analytics history your team needs before comparing editions.
- We record the hosting target, server sizing assumptions and monthly pageview range in the written scope.
- Engagements are fixed-scope, so scope, deliverables and timelines are agreed in writing before any work starts.
How we build
- We install the chosen platform in your cloud account, data center or air-gapped network, with separate app and database tiers where sizing requires it.
- We configure consent settings, tracking scripts and any Google Analytics import against the rules your regulators apply.
- We test tracking accuracy, backups and upgrade paths before the platform goes live for reporting.
How we hand over
- We document the installation, configuration keys, backup and restore steps, and the upgrade procedure your team will follow.
- We walk through the reports and limits of the self-hosted edition, including features that stay on the paid cloud or premium plugin side.
- If you later move between Matomo and Plausible, we document the export path and the data that will not carry across.
How we support
- Ongoing support, upgrades and continuous testing are available as retainers, so patch cycles do not depend on one internal engineer.
- We can apply Matomo or Plausible releases on your schedule and confirm each one against your written scope.
- Ask for the support scope, response expectations and upgrade responsibilities in writing before you sign.
