Which self-hosted analytics tool fits your team's situation
If you are replacing Google Analytics with a self-hosted tool, choose Matomo when you need full reporting, ecommerce tracking and premium plugins, and accept that consent exemptions are conditional. Choose Plausible Community Edition when you want lightweight, cookieless analytics on Docker and ClickHouse and can absorb the update burden yourself. Choose Umami when you want a small MIT-licensed install on Node.js and PostgreSQL and do not need deep reporting. Each advantage depends on a condition, so confirm that condition before you commit.
Matomo fits teams that need the widest report set, ecommerce analysis and optional premium plugins such as Heatmap and Session Recording, which are sold under the InnoCraft EULA rather than the GPL. Its On-Premise Community edition is free with unlimited users and hits, but the consent position is conditional: Matomo's ePrivacy FAQ says features such as User ID, heatmaps or session recordings remove the CNIL exemption, so a site that adds them will likely need a consent banner. Confirm the configuration with your privacy counsel before you enable any premium plugin.
Plausible Community Edition fits teams that want cookieless measurement with no banner requirement from the vendor's design, provided the operator manages upgrades, capacity, backups and security. The self-hosted page says Community Edition gets security fixes only when you apply the release, and it lacks features such as single sign-on, the Sites API and ecommerce revenue goals. Umami fits teams that want a small install and an MIT license, but its reporting is lighter than Matomo's and its paid Umami Cloud adds email reports and a streaming API that the self-hosted version lacks. Ask each vendor to confirm the features you need before you build a plan around them.
Which tool fits which scenario
This table matches common team situations to the analytics tool that fits them best, with the reason drawn from licensing, feature limits and operating effort. Read each row against your own traffic, consent position and patching capacity, then check the conditions in the reason column before shortlisting.
| Scenario | Best fit | Reason |
|---|---|---|
| Marketing team needing ecommerce revenue and funnels | Matomo | Matomo On-Premise is free with unlimited users and hits, and its full reporting suite covers ecommerce and goals. Plausible Community Edition leaves out marketing funnels and ecommerce revenue goals, and Umami's self-hosted feature set should be confirmed against your needs. |
| Privacy-led site wanting no cookie banner | Plausible or Umami | Both are described as cookieless. Matomo can avoid consent only in a narrow configuration, and adding User ID, heatmaps or session recordings removes the CNIL exemption, so confirm with your authority. |
| Small site with modest traffic and one operator | Umami | Umami runs on Node.js and PostgreSQL with a prebuilt Docker image and Compose file that bundles PostgreSQL. Confirm current hardware needs against the installation documentation before sizing. |
| Small site that wants a lightweight EU-made tool | Plausible | Plausible Community Edition needs Docker, Docker Compose and at least 2 GB of RAM, and it is AGPLv3 licensed. Its self-hosted operators must apply releases themselves, so budget time for upgrades. |
| Team migrating from Google Analytics history | Matomo or Plausible | Matomo's importer copies aggregated reports but not the Visitor Log, Custom Reports or Segmentation, and skips some reports such as Funnels. Plausible imports GA4 history as daily aggregates, supports up to 5 GA properties and cannot import ecommerce revenue. |
| Team needing depth of segmentation and raw visit logs | Matomo | Matomo's visitor log and segmentation are core features, although they do not apply to imported Google Analytics reports. Plausible and Umami offer lighter reporting, so confirm against your reporting requirements. |
| Team with no appetite for patching | Neither self-hosted option without staffing; consider the paid cloud | Plausible Community Edition ships long-term releases twice a year and gets security fixes only when you apply them. Umami Cloud and Matomo Cloud remove patching, but Matomo Cloud and Umami Cloud are separate paid plans, so compare their hit or event limits. |
| Team requiring single sign-on or Sites API | Confirm before choosing Plausible Community Edition | Plausible's self-hosted page lists single sign-on and the Sites API as features missing from Community Edition. Confirm whether Matomo or Umami covers these needs in your edition. |
How Matomo, Plausible and Umami are built differently
The three tools differ most in the stack each one asks your team to run. Matomo is a PHP application backed by MySQL or MariaDB and served through a web server such as Apache, Nginx, IIS or LiteSpeed. 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 PHP 8 with MySQL 5.5 or later or MariaDB. Plausible Community Edition is a Docker Compose deployment built around ClickHouse, which needs a CPU with SSE 4.2 or NEON and at least 2 GB of RAM. Umami runs on Node.js and PostgreSQL, and it ships a prebuilt Docker image plus a Compose file that starts a bundled PostgreSQL database. Source installs require Node.js 18.18 or newer, and PostgreSQL is supported from version 12.14.
Those choices shape day-to-day operations. Matomo gives a PHP and database administrator a familiar, mostly conventional stack to patch, with the web server, PHP runtime and database versioned separately. Plausible and Umami are container-first, so your platform team needs Docker, Compose and volume backup habits, and a ClickHouse or PostgreSQL operator if you move beyond the bundled defaults. Plausible's self-hosted page places installation, upgrades, capacity, uptime, backups and security on the operator, and it notes that Community Edition gets security fixes only when you apply a release. Confirm with each vendor how often you must apply updates, which components a Compose upgrade touches, and whether a database migration needs a manual step before you schedule downtime.
Before choosing, map the skills you already have. A team strong in PHP and MySQL can run Matomo with the least new tooling. A team that already operates Docker hosts and understands columnar databases can take on Plausible, but should test ClickHouse backup and restore. A Node.js shop with PostgreSQL experience will find Umami closest to its existing practice. Ask each candidate for a written upgrade runbook, a tested restore procedure and the name of the component owner for each layer, then have your own engineers rehearse one upgrade in a non-production environment before committing.
Side-by-side capabilities from supplied facts
This table compares the three self-hosted analytics tools on license, latest stable release, stack, server sizing, cookieless design, Google Analytics import, cloud-only features and support model. Read each row as a constraint to check against your own traffic, hosting rules and team skills, then confirm the items marked for vendor confirmation before you decide.
| Capability | Matomo | Plausible | Umami |
|---|---|---|---|
| License | GPL-3.0 (GPLv3) for the repository; On-Premise Community edition is free | AGPLv3 or any later version for Community Edition | MIT license |
| Latest stable version and date | Matomo 5.14.1, released October 4, 2026; Matomo 6.0.0 in beta since September 9, 2026 | Community Edition v3.2.1, a security release published May 15, 2026 | Umami v3.4.0, published September 17, 2026 |
| Stack | PHP with MySQL or MariaDB, behind Apache, Nginx, IIS or LiteSpeed | Docker and Docker Compose with ClickHouse | Node.js with PostgreSQL; prebuilt Docker image and Compose file with bundled PostgreSQL |
| Minimum requirements | Matomo 6.0.0 needs PHP 8.1+ and MySQL 8.0+ or MariaDB 10.6+ | CPU with SSE 4.2 or NEON, at least 2 GB RAM, Docker and Docker Compose | Node.js 18.18 or newer for source install; PostgreSQL 12.14 or newer |
| Server sizing (published) | Single server: 4 CPUs, 8 GB RAM, 250 GB SSD for up to 1 million pageviews a month; split app and database at 8 CPUs and 16 GB RAM each for up to 10 million | Not supplied; confirm sizing for your pageview volume with the Plausible team | Not supplied; confirm sizing for your event volume with the Umami team |
| Cookieless design | Cookie-free setup can be consent-exempt under some EU authority rules, but User ID, heatmaps or session recordings remove the exemption | Uses no cookies, so no cookie banner is required according to Plausible | Works without cookies, cross-site tracking or automatic collection of personal data |
| Google Analytics import | Free Google Analytics Importer plugin for On-Premise; imports aggregated reports only, so Visitor Log, Ecommerce Log, Custom Reports and Segmentation do not work on imported data | Imports historical GA4 as daily aggregates up to the first native visitor; up to 5 GA properties per site; no ecommerce revenue import | Not supplied; confirm import tooling and limits with Umami |
| Features held back for paid cloud or premium | Heatmap and Session Recording is a paid premium plugin under the InnoCraft EULA; Matomo Cloud plans start at 29 per month excluding tax | Community Edition lacks marketing funnels, user journeys, ecommerce revenue goals, SSO, Sites API, Looker Studio connector and advanced bot filtering | Umami Cloud adds email reports and a streaming API; Cloud Hobby is $0 per month, Pro $20 per month, Business $200 per month |
| Support model | Forum support for On-Premise; Cloud plans include hosted operation | Community supported only; operator handles installation, upgrades, backups and security patches | Self-hosted operation is yours; confirm any vendor support options for self-hosted installs |
What each license and edition allows and what is paid
Matomo's repository is licensed under GPLv3, and the On-Premise Community edition is free with unlimited users and hits, with forum support only. Your team owns the operation of that edition, so the license cost is zero but the running cost is yours. Paid items are separate: premium plugins are sold under the InnoCraft EULA rather than the GPL, and Matomo Cloud is a hosted subscription that starts at 29 per month excluding tax.
- Free core: The GPLv3 codebase and the On-Premise edition carry no license fee, with unlimited users and hits.
- Premium plugins: Heatmap and Session Recording is sold per number of users under the InnoCraft EULA, with a 30-day free trial.
- Free importer: The Google Analytics Importer is a GPL v3+ plugin for On-Premise, so it does not add a license fee.
- Cloud tiers: Matomo Cloud plans start at 29 per month excluding tax, scaled by hits from 50,000 to 10 million a month, with data stored in Frankfurt, Germany.
- Support gap: Forum support is the only support listed for On-Premise, so budget for paid help or internal expertise.
Before you commit, confirm with InnoCraft which premium plugins your reports depend on and how their per-user pricing scales with your team.
Plausible Community Edition is open source under AGPLv3 or any later version, and it is self-hosted with Docker and Docker Compose. Plausible Cloud adds paid capabilities that the Community Edition does not include. The Community Edition is community supported only, so the operator carries installation, upgrades, capacity, uptime, backups and security. The AGPL network clause also applies to any modified version you run for users, so review that before you change the code.
- Missing features: Marketing funnels, user journeys, ecommerce revenue goals, single sign-on, the Sites API, the Looker Studio connector and advanced bot filtering are not in the Community Edition.
- Release cadence: The Community Edition is a long-term release published twice per year, while Cloud ships updates multiple times per week.
- Security fixes: Fixes arrive only when your team applies the release, such as v3.2.1, published May 15, 2026.
- Cloud plans: Starter, Growth and Business start at 9, 14 and 19 per month, with 10k monthly pageviews on the entry plan and custom Enterprise pricing.
- Migration path: Community Edition users can export and import data to and from Plausible Cloud.
Check which of the missing features your reporting needs, because adding them later means either a Cloud subscription or custom development you would own.
Umami is licensed under MIT, which permits modification and redistribution with few conditions. The software is free to self-host, and Umami Cloud is a separate paid service that adds features the self-hosted version lacks. Your team carries the infrastructure, upgrades and database operation for the free edition, and the Cloud plans shift those tasks to Umami while charging by event volume.
- Permissive license: MIT allows your team to modify the code for internal use without the copyleft obligations of GPL or AGPL.
- Missing from self-hosted: Email reports and a streaming API are part of Umami Cloud rather than the open-source install.
- Cloud tiers: Hobby is 0 per month for up to 100K events with 6 months of retention, Pro is 20 per month for 1 million events with 2 years of retention, and Business is 200 per month for 10 million events with 5 years of retention.
- Overage: Pro charges 0.00003 per extra event and Business charges 0.00002 per extra event, with custom Enterprise terms.
- Deployment guides: Umami documents guides for managed hosting platforms alongside self-hosting on your own infrastructure.
Confirm whether your required reports and alerts exist in the self-hosted build, since the feature gap is the main reason teams move to Cloud.
What drives the running cost of each tool
Running any of these three tools costs more than its license line. The cards below cover the components that recur: the server and database you size, the hours spent on upgrades and backups, premium add-ons, cloud fees and the cost of leaving later. DeployOpen does not publish prices, and any cost estimate follows a written scope agreed before work starts.
Server sizing by pageviews
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. It recommends separate app and database servers with 8 CPUs and 16 GB of RAM each for up to 10 million pageviews a month. Plausible Community Edition needs Docker, Docker Compose and at least 2 GB of RAM, and Umami runs on Node.js with PostgreSQL. Check your monthly pageview volume first, then size each tool against it, because the same traffic can land on very different hardware.
Database and storage load
Matomo stores raw and aggregated data in MySQL or MariaDB, so storage grows with traffic and retention settings and needs SSD capacity planning. Plausible Community Edition relies on ClickHouse, which brings its own CPU requirement of SSE 4.2 or NEON. Umami uses PostgreSQL, with versions from 12.14 supported. Ask each vendor how storage grows per month of traffic, and who owns the database backup and restore procedure.
Staff time for upgrades and backups
Self-hosting moves upgrades, backups, uptime and security patching onto your team. Plausible states that Community Edition operators manage installation, upgrades, capacity, uptime, backups and security themselves, and that Community Edition is a long-term release published twice per year with security fixes only when you apply them. Matomo 6.0.0 needs PHP 8.1 or newer and MySQL 8.0 or MariaDB 10.6 or newer, so plan the PHP and database move as part of each upgrade cycle.
Premium plugin spend on Matomo
Matomo On-Premise is free with unlimited users and hits, but some features are paid. The Heatmap and Session Recording plugin is sold per number of users under the InnoCraft EULA, not the GPL, and it carries a 30-day free trial. Add it to the budget as a recurring line, and ask for the per-user rate in writing before you assume it will fit a team that grows. The free Google Analytics Importer is not a paid item.
Cloud fees versus self-hosting
Plausible Cloud starts at $9 per month for 10k monthly pageviews, and Umami Cloud Pro costs $20 per month for 1 million events. Both fees recur and scale with traffic, and Umami adds overage at $0.00003 per extra event on Pro. Self-hosting removes the subscription but moves hosting, patching and staff time onto your side. Compare the full self-hosted monthly cost, including your team's hours, with the cloud fee at your actual event volume, and ask whether cloud-only features matter to you.
Cost of switching later
Leaving a self-hosted tool has its own cost. Plausible states that Community Edition users can export and import data to and from Plausible Cloud, but Plausible's Google Analytics import brings in only daily aggregates and cannot import ecommerce revenue. Matomo's Google Analytics importer brings in aggregated reports only, so the Visitor Log, Ecommerce Log, Custom Reports and Segmentation do not work for imported data. Before you commit, test the export path you would actually use, and confirm with each vendor what history you can keep.
What a self-hosted rollout of each tool involves
The sequence below takes a team from a sized server to a tracked, consent-checked site with imported history, backups and a named owner for upgrades. Each step closes with a check you can run before moving on.
Size the server against monthly pageviews
The team lead and the infrastructure owner estimate monthly pageviews across every site that will report to the tool, then pick a server profile. 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. Plausible Community Edition needs Docker, Docker Compose, a CPU with SSE 4.2 or NEON for ClickHouse, and at least 2 GB of RAM. Umami runs on Node.js with PostgreSQL. Done when the sizing sheet is signed off and the hosting team has a named server or cluster for the tool.
Choose the runtime stack and version
The platform owner confirms the stack the team can support. Matomo 5 runs on PHP 8 with MySQL 5.5 or later or MariaDB behind Apache, Nginx, IIS or LiteSpeed. Matomo 6.0.0 is in beta since September 9, 2026 and needs PHP 8.1 or newer with MySQL 8.0 or newer or MariaDB 10.6 or newer, so a production team should confirm whether it will run the stable 5.x line or wait for the stable 6.x release. Umami needs Node.js 18.18 or newer for a source install and supports PostgreSQL from version 12.14. Done when the chosen version, PHP or Node.js runtime, and database version are written into the build record.
Deploy with Docker or from source
The platform engineer deploys the tool in the client's own cloud account, data center or air-gapped network. Umami publishes a prebuilt Docker image and a Docker Compose file that starts it with a bundled PostgreSQL database, which suits a single-team install. Plausible's community-edition repository is built around Docker Compose. Matomo is typically installed as a web application on the server stack chosen in the previous step. Confirm that the database is not exposed to the public network and that the admin account uses the client's identity controls. Done when the admin login works, the site loads over TLS, and a test page view appears in the reports.
Configure tracking and the consent position
The privacy lead and the web team decide whether the site needs a cookie banner. Plausible and Umami are designed to run without cookies. Matomo's ePrivacy FAQ says that France's CNIL treats some analytics as exempt from consent only when they stay within narrow purposes, and that adding User ID, heatmaps or session recordings removes the exemption. The team should write down which features are enabled, confirm the configuration against the authority rules that apply to each market, and record the decision with legal review. Done when the tracking snippet is deployed, the consent position is documented, and the features that would break an exemption are switched off or accepted in writing.
Import historical data from Google Analytics
The analytics owner decides how much history the new tool needs and runs the import. Matomo's Google Analytics Importer imports aggregated report data into a new Matomo site, and Visitor Log, Ecommerce Log, Custom Reports and Segmentation do not work for imported reports. Plausible imports historical GA4 stats as daily aggregates up to the first native Plausible visitor, supports up to 5 GA properties per site, and cannot import ecommerce revenue. Umami's public documentation does not describe a Google Analytics import in the supplied facts, so the team should confirm that with the vendor before planning. Done when the imported totals are compared against the source property for a sample of dates and the known gaps are recorded.
Set backups, retention and the upgrade cadence
The operations owner writes the backup schedule for the database and any file storage, tests a restore, and sets the upgrade calendar. Plausible's self-hosted page says Community Edition is a long-term release published twice per year, is supported by the community only, and gets security fixes only when the operator applies the release. Its v3.2.1 security release was published on May 15, 2026. Matomo and Umami also need a named owner for each release. Done when a restore has been tested on a copy, the upgrade calendar is in the change system, and each release source is on a watch list.
Hand over operations and ownership
The platform owner transfers the running system to the team that will operate it, with runbooks for upgrades, restores, user management and the consent configuration. Plausible's self-hosted page notes that Community Edition operators manage installation, upgrades, capacity, uptime, backups and security themselves. The handover should name who applies each security release and who answers when tracking breaks after a site change. Done when the runbook is reviewed, an on-call rota exists, and a test upgrade has been run by the receiving team.
Questions buyers ask before choosing or hiring help
How much effort does each self-hosted install take to run?
Matomo On-Premise, Plausible Community Edition and Umami all leave installation, upgrades, backups and security with your team, so the effort is mostly ongoing operations rather than the first deployment. Matomo is the heaviest of the three to keep current: it runs on PHP with MySQL or MariaDB behind a web server, and Matomo 6.0.0 raises the floor to PHP 8.1 and MySQL 8.0 or MariaDB 10.6. Plausible Community Edition is a long-term release published twice per year, is community supported only, and gets security fixes only when you apply the release, so someone must watch its release cadence. Umami is the lightest stack to deploy, with a Docker image and a Compose file that bundles PostgreSQL. In every case, budget for a named owner who applies upgrades, monitors uptime and tests restores. Ask any vendor or partner to state that owner's time commitment in writing before you sign.
Can a non-specialist run Umami or Plausible in production?
A generalist with container experience can usually stand up either tool, but running it safely in production needs someone who can handle databases, TLS, backups and upgrades. Umami's installation path is the simplest: the Docker Compose file starts Umami with a bundled PostgreSQL database, and a source install needs Node.js 18.18 or newer. Plausible Community Edition requires Docker and Docker Compose, a CPU with SSE 4.2 or NEON for ClickHouse, and at least 2 GB of RAM, so the ClickHouse data store is the component most likely to need specialist attention. Check three things before deciding to run it yourself: who restores the database after a failure, who reviews each Plausible or Umami release, and whether anyone can answer a security question about the stack. If none of these has a clear owner, a managed or partner-run install may suit you better.
How does server size change as pageviews grow?
Server size grows with monthly pageviews, and the step up for Matomo is large enough that it should be planned early. 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. Plausible Community Edition sets a floor of 2 GB of RAM, which covers small sites, but its published requirements do not give a pageview tier, so ask Plausible to confirm sizing for your traffic. Umami publishes no sizing tiers in the supplied material either. Test with your own event volume and retention period, because storage grows with retained data as well as traffic.
Do I need Matomo premium plugins to get heatmaps?
Yes, heatmaps and session recordings in Matomo come from a paid premium plugin, not from the free On-Premise edition. The 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. Its price depends on the number of users who need access, so ask Matomo for the current per-user terms before you size the budget. Also note that Matomo's ePrivacy FAQ says adding heatmaps or session recordings removes the consent exemption that some French and other EU authorities allow for privacy-focused analytics. That means a Matomo deployment that uses heatmaps may need a cookie banner, even if the base configuration does not. Plausible and Umami do not offer heatmaps in the supplied material, so heatmap needs should be settled before choosing either.
Can I move Google Analytics history into Matomo, Plausible or Umami?
Matomo and Plausible both offer a Google Analytics import, but each keeps a different slice of history, and neither gives you raw visit data. The free Matomo Google Analytics Importer brings aggregated report data into a new Matomo site. Matomo's FAQ says 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, and cannot import ecommerce revenue. Its unique visitor counts are approximations because they sum daily uniques. Umami's supplied material does not describe a Google Analytics import, so confirm that with Umami before you plan a migration. Whatever tool you pick, export your GA reports now and keep them as a record of the baseline.
When should we hire an implementation partner for analytics?
Hire a partner when your team lacks the capacity to own the install, or when the analytics stack has to meet audit or regulatory evidence needs. DeployOpen plans, implements, customizes, integrates, hardens, backs up, upgrades, documents and supports self-hosted open-source platforms inside your own infrastructure, and most engagements are fixed-scope with scope, deliverables and timelines agreed in writing before work starts. Ongoing support, upgrades and continuous testing are available as retainers. DeployOpen does not publish a price list, so a quote follows from the written scope. Good scope items include the hosting target, the sites and events to track, the Google Analytics import plan, consent configuration, backup and restore tests, and the upgrade schedule. DeployOpen prepares systems and evidence for compliance assessments but does not issue audit reports or certifications.
What should a quote for a self-hosted analytics install include?
A useful quote separates one-time work from recurring work and names who performs each task. One-time items include infrastructure provisioning, installation, configuration, the Google Analytics import, consent setup and initial testing. Recurring items include upgrades, security patches, monitoring, backups and restore tests, and support for new sites. Ask whether the price covers the database and web tiers, who holds the cloud or data center accounts, and what happens if a release breaks the install. For Matomo, add the cost of any premium plugins and their per-user terms. For Plausible and Umami, ask whether the quote assumes Community Edition or a paid cloud tier, because the cloud adds features such as single sign-on and email reports that the self-hosted editions lack. Ask for the upgrade cadence in writing too.
How DeployOpen works on this
DeployOpen plans, implements, customizes and documents self-hosted open-source platforms inside your own infrastructure, so the analytics choice is tested against your traffic, consent position and hosting constraints before anything is installed. Engagements are fixed-scope, with scope and deliverables agreed in writing before work starts.
How we scope
- Written scope names which of the three tools fits your traffic, sites, and reporting needs
- Scope records your hosting target, database choice, and expected pageview or event volume
- Scope lists whether Google Analytics history must be imported, and which reports must come across
- Consent and cookie position is documented with your legal or privacy team before design starts
How we build
- Installation of the chosen tool in your cloud account, data center, or air-gapped network
- Configuration of tracking scripts, sites, goals, and any Google Analytics import you agreed to
- Testing of tracking accuracy, retention settings, and backup and restore on your infrastructure
- Hardening of the server, database, and reverse proxy, with upgrade steps tested before go-live
How we hand over
- Runbook covering installation, upgrades, capacity checks, backups, and restore procedures
- Documented consent configuration and evidence of how the tracker is set up for your jurisdictions
- Record of which features are self-hosted and which sit behind a paid cloud or premium plugin
- Handover session with your platform, security, and marketing owners, with written sign-off
How we support
- Ongoing support, upgrades, and continuous testing are available as a retainer after handover
- Retainer scope is agreed in writing, covering upgrade windows for your chosen release line
- Your team keeps ownership of the data and the server, so exit or migration options stay open
- Quotes follow from the written scope, so ask for a breakdown of one-time and recurring effort
