What web analytics costs when you build, partner or subscribe
Teams comparing in-house self-hosting, a partner-led implementation and a SaaS subscription should start from one fact: the open-source editions carry no license fee. Matomo On-Premise Community, Plausible Community Edition and Umami can all be self-hosted for free, so the real comparison turns on infrastructure, setup, ongoing upkeep and the internal time your staff spend on each. SaaS prices are published by the vendors, for example Umami Cloud Hobby at $0 per month for up to 100K events, Pro at $20 per month for 1 million events and Business at $200 per month for 10 million events. A partner quote, by contrast, follows from a written scope and does not come from a list price.
The answer depends on five variables: traffic volume, the number of sites, the consent setup, the integrations you need and who will operate the platform. 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 for up to 10 million. Plausible Community Edition needs Docker, Docker Compose and at least 2 GB of RAM, and Plausible states that its operators manage installation, upgrades, capacity, uptime, backups and security themselves. Each of these items is a recurring cost, and each grows with traffic and the number of sites you track.
Before you compare totals, confirm four things with each candidate. Ask whether any feature you need, such as the GA4 import, Search Console data, ecommerce revenue or single sign-on, is available only in the paid edition, because Plausible's self-hosted page lists several features missing from Community Edition. Ask who applies security releases, since Plausible Community Edition gets security fixes only when the operator applies them. Ask whether a consent setup will require a paid plugin, since Matomo's heatmap and session recording plugin is sold per user. Finally, ask a partner for a fixed-scope quote that lists the hosting, setup, testing, documentation and support items separately, so you can compare it line by line against your own staff time.
Cost components by option: in-house, partner and SaaS
This table compares who pays for each cost line when you run web analytics yourself, hire an implementation partner, or buy a SaaS plan, and whether each line is one-time or recurring. Read each row as a question to answer in your own quote and staffing plan. The main takeaway is that free self-hosted software shifts the bill to infrastructure, staff time and ongoing operations rather than eliminating it.
| Cost component | In-house | Implementation partner | SaaS |
|---|---|---|---|
| Software license | Matomo On-Premise Community is free forever, and Umami and Plausible Community Edition are open source (Matomo pricing page; Umami pricing page). Paid add-ons such as Matomo's Heatmap and Session Recording plugin carry their own license fees. One-time or recurring: none for core software. | Usually no license cost for the open-source core. Any paid plugin or edition is billed to you under its own terms. Confirm which add-ons are in written scope. | Recurring subscription. Matomo Cloud starts at 29 per month excluding tax (Matomo pricing page). Plausible Cloud Starter, Growth and Business are 9, 14 and 19 dollars per month for 10k pageviews (Plausible homepage). Umami Cloud Hobby is free, Pro is 20 dollars per month and Business is 200 dollars per month (Umami pricing page). |
| Infrastructure (servers, storage, database) | You pay cloud or data center costs, recurring. Matomo's published sizing for up to 1 million monthly pageviews is 4 CPUs, 8 GB RAM and 250 GB SSD on one server (Matomo requirements FAQ). Plausible Community Edition needs at least 2 GB RAM with Docker. | Recurring infrastructure cost is usually billed to you directly, through your cloud account. Confirm whether the partner resells capacity or deploys into your accounts. | Included in the subscription. Cost scales with the plan tier, event or pageview volume, and retention. |
| Installation and configuration | One-time internal effort: staff time to install the platform, set up the database, web server and Docker or Node.js runtime, and configure sites and users. | One-time fee set by the written fixed scope. Ask for installation, hardening and handover deliverables listed separately. | Minimal. Account setup and tag installation are typically short, one-time internal tasks. |
| Consent and privacy setup | One-time and recurring internal effort: configuring IP anonymization, retention, cookie behavior and consent decisions. Legal review sits with your privacy team. | One-time fee for configuration and documentation of the setup. Legal conclusions remain your decision and your counsel's. | Mostly one-time configuration within the vendor's settings. Consent obligations still require your own review, since the setup decisions stay with you. |
| Migration from Google Analytics | One-time internal effort. Matomo's importer brings in aggregated report data only, so Visitor Log, Segmentation and Funnels are not carried over (Matomo import FAQ). Plausible imports GA4 daily aggregates without ecommerce revenue (Plausible docs). | One-time fee based on the migration scope, including which reports, sites and history must be kept. Ask what is excluded. | Often one-time internal effort, and the import depth depends on the vendor's importer limits. |
| Integrations | Recurring internal effort to build and maintain links to tag managers, consent tools, data warehouses and identity providers. | One-time fee for building agreed integrations, plus optional recurring support for changes. Price comes from written scope. | Depends on what the vendor provides. Some features, such as single sign-on or the Looker Studio connector, are listed as missing from Plausible Community Edition (Plausible self-hosted page). |
| Upgrades and security patching | Recurring internal effort. Plausible Community Edition gets security fixes only when you apply the release (Plausible self-hosted page). Matomo 6.0.0 requires PHP 8.1 or newer and MySQL 8.0 or newer or MariaDB 10.6 or newer, which may require planned work. | Optional recurring retainer for upgrades and patching, priced from the agreed scope. Confirm response expectations in writing. | Included. Plausible Cloud ships updates multiple times per week (Plausible self-hosted page). |
| Backups and monitoring | Recurring internal effort and storage cost for backups, restore tests and uptime monitoring. | One-time setup of backup and monitoring, and optional recurring operation under a retainer. Confirm restore testing is in scope. | Included in the subscription. Ask for retention and recovery terms in the contract. |
| Support and internal staff time | Recurring. Community support only for Plausible Community Edition, and forum support for Matomo On-Premise (Matomo pricing page; Plausible self-hosted page). Staff time for operations is the largest hidden cost. | Recurring retainer for support, priced from written scope. Ask for named response times and what is excluded. | Included at the vendor's support tier. Higher tiers and enterprise pricing are quoted separately. |
What the server bill looks like for Matomo, Plausible and Umami
Self-hosted analytics has no license fee for the three platforms in this topic, so the server bill is the recurring line that moves with traffic. Matomo's published sizing is the clearest starting point: a single server with at least 4 CPUs, 8 GB of RAM and 250 GB of SSD handles up to 1 million pageviews a month, while Matomo recommends separate application and database servers with 8 CPUs and 16 GB of RAM each once you reach up to 10 million pageviews a month. The jump between those two tiers is a架构 decision with its own cost, because it doubles the number of machines you patch, back up and monitor. Ask your team to confirm current figures against the requirements FAQ for the Matomo version you plan to run, since Matomo 6.0.0 raises the minimum PHP and database versions.
Plausible and Umami have lighter stated minimums, but the cost lines differ. Plausible's Community Edition needs Docker and Docker Compose, a CPU with SSE 4.2 or NEON support (required by ClickHouse) and at least 2 GB of RAM, so the bill is for a container host sized for its analytical database and not for a traditional web and database pair. Umami's source install requires Node.js 18.18 or newer and PostgreSQL from version 12.14, and its Docker Compose file can start a bundled PostgreSQL database. Each choice has a different operating footprint: Plausible pulls in more moving parts, while Umami keeps the stack smaller. Confirm the exact versions and container images with each vendor before you size anything. The server price itself depends on your own provider, region, reserved or on-demand terms and whether the machines sit in your data center or an air-gapped network. Ask your cloud or infrastructure team to price the sizing tiers above with their own rates, including backup storage, snapshots and a standby database if your uptime target requires one. Remember that a Plausible or Umami Cloud subscription is priced separately, so compare the infrastructure line against the vendor's published plans only after you have a quoted hosting figure from your own provider.
Which drivers move the cost up or down
Self-hosted web analytics costs shift less with the license and more with the choices made around it. The six drivers below each move a specific line, from infrastructure and staff time to the price of a paid feature or a SaaS overage, so a team can see which assumptions to test before comparing options.
Traffic volume and event count
Volume sets the size of the server, the database and the operating effort. Matomo 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 for up to 10 million. Umami Cloud prices by event count, so the same traffic growth moves the SaaS line in steps. Ask the partner to model both the infrastructure line and the hosted-tier line at your projected peak, not your current average.
Number of sites and tenants
Each additional domain, subdomain or business unit adds configuration, access reviews, tag deployment and reporting work, even when the platform cost stays flat. A multi-site rollup for a group of brands can change whether one shared instance or several isolated ones is cheaper to run. Ask for the setup effort per site and whether the quote covers onboarding each new property after go-live, since that recurs as the estate grows.
Consent and privacy configuration
Cookieless tracking can avoid a consent banner, which removes a recurring cost in design, legal review and consent management tooling. The exemption is narrower than it looks: under CNIL-style criteria, adding User ID, heatmaps or session recording removes it. The heatmap and session recording plugin is a separately licensed paid product under the InnoCraft EULA, priced per user, with a 30-day free trial. Confirm with counsel which features are in scope before the budget is set.
Historical data and Google Analytics migration
Migration effort depends on how much history you need to keep. Matomo's Google Analytics importer is free under GPL v3 or later, but it only imports aggregated reports, 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. Plausible imports GA4 history as daily aggregates, cannot import ecommerce revenue, and supports up to 5 GA properties per site. Budget for a mapping exercise and for explaining the gaps to report owners, not only for the import job.
Integrations and identity
Single sign-on, reporting connectors and data exports are where internal effort tends to accumulate. Plausible's Community Edition lists single sign-on, the Sites API and the Looker Studio connector among features missing compared with Plausible Cloud, so an organization that needs them must build or buy them. Confirm which identity provider, dashboard tool and warehouse you need, and ask the partner to state whether each integration is in the fixed scope or a later change request.
Hosting location and audit evidence
Hosting in your own cloud account or data center moves the infrastructure line and the evidence effort together. Each hosted region, backup target and log store must be documented for privacy and vendor risk reviews, and that documentation is work the organization pays for once and then keeps current. Plausible Cloud and Matomo Cloud host data in the EU or Frankfurt, which may reduce review work but moves cost into a subscription. Ask what evidence pack the quote includes and what is refreshed on each upgrade.
How to build your own estimate before you ask for quotes
This sequence turns unknowns into a comparable three-year view, so each SaaS, self-hosted and implementation option is priced against the same traffic, features and operating assumptions.
Count monthly pageviews and events
Start by measuring your real monthly pageviews and any custom events (form submits, downloads, purchases) across every site you plan to measure, using your current analytics tool or server logs. Compare that figure with the published tiers: Plausible Cloud lists plans for 10k monthly pageviews, Umami Cloud counts events against tiers such as 100K and 1 million, and Matomo Cloud lists tiers from 50,000 to 10 million hits a month. Note the month with the highest traffic, not only the average. Done when you have one peak monthly number per site and a note of which vendor tier each one falls into.
List required features and check edition fit
Write down the features your teams must have, such as ecommerce revenue goals, funnels, single sign-on, API access, campaign tracking or heatmaps. Check each one against the edition you are considering. For example, the Plausible Community Edition page lists missing features compared with Plausible Cloud, including marketing funnels, ecommerce revenue goals, single sign-on, the Sites API and the Looker Studio connector. Mark any feature that is paid, edition-specific or dependent on a plugin, because these change the cost line. Done when every must-have has a yes, no or confirm status for each candidate platform.
Price infrastructure for the sizing tier
Match your peak traffic to the hosting size the vendor publishes. 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 and at least 2 GB of RAM. Ask your cloud or data center team for the monthly cost of compute, storage, backups and outbound bandwidth in your own environment, and record the figure as recurring. Done when each self-hosted option has a monthly infrastructure line with its assumptions written beside it.
Add one-time setup and migration scope
Identify the one-time work: installation, hardening, tag or script deployment across sites, consent configuration, dashboards, user and identity setup, and any migration of historical data. For migrations from Google Analytics, note the limits: Matomo's importer brings in aggregated report data only, so the Visitor Log and Segmentation do not work for imported reports, and Plausible's import brings in historical GA4 stats as daily aggregates and cannot import ecommerce revenue. Ask each implementer to price these items separately from recurring support. Done when you have a one-time list with a named owner for each item, whether internal staff or an implementation partner.
Add recurring upkeep and staff time
List the work that repeats every year: applying releases, database and PHP or Node runtime upgrades, backups and restore tests, uptime monitoring, security patch review, and access reviews. Plausible states that Community Edition operators manage installation, upgrades, capacity, uptime, backups and security themselves, and that security fixes arrive only when the operator applies the release. Estimate the hours your team would spend, then decide whether an internal engineer, a managed retainer or a SaaS plan carries that load. Done when each option has a recurring line for staff time, retainer fees and infrastructure, and the assumptions behind each hour count are written down.
Compare three-year totals across options
Build one table with the same columns for every option: SaaS subscription at your peak tier, self-hosted infrastructure, one-time setup, recurring upkeep, staff time and any plugin or overage charges. Add the figures for three years so one-time costs and recurring costs are visible together. Include the cost of an overage scenario on SaaS tiers, because Umami Cloud charges per extra event above the plan limit. Test the table with a traffic growth assumption and a feature change, and record which inputs move the total most. Done when the table shows a three-year total per option and a short list of the assumptions that would change the ranking.
Request written scopes so quotes are comparable
Send the same written brief to each implementer: list the sites, pageview and event volumes, required features, hosting location, identity integration, data migration, support hours and upgrade expectations. Ask each one to return a fixed scope that states deliverables, exclusions, acceptance checks and who performs each task. Most DeployOpen engagements are fixed-scope and agreed in writing before work starts, so ask other providers for the same format. Compare quotes line by line against your three-year table, and confirm what is excluded before signing. Done when every quote maps to the same scope and the gaps between quotes are explained in writing.
When a partner costs less than building alone
A small team running one marketing site usually has one person who already owns the website, the tag manager and the hosting account. For that setup, the largest internal line is rarely the first install. It is the recurring work of watching upgrades, restoring backups and checking that the analytics server still responds after a host change. Matomo, Plausible and Umami all have Docker-based or documented install paths, so the initial deployment can be small. The ongoing operating load is what stays on the operator's calendar.
- Where internal time grows: monthly upgrades, backup restore tests, certificate renewals and answering questions from marketing about missing data.
- When a fixed-scope implementation helps: when the operator has no spare hours for the first month and needs a written install, backup and handover package before go-live.
- When a partner adds cost without saving: when the site is small, the operator is comfortable with Docker, and a managed Umami or Plausible Cloud plan would cover the need for the expected traffic.
- What to check: whether the operator can name the upgrade and restore procedure, and whether the written scope includes handover or only the initial install.
Ask the partner to separate one-time setup from any recurring support, and compare that against the hours the operator expects to spend each quarter.
An organization with several domains, departments or brands, or one subject to sector rules on data location and access, has more coordination work than any single install. Each site needs its own tracking configuration, consent setup, retention settings and role assignments. Auditors will ask who can export visitor data and how changes are recorded. Here the largest internal line is usually governance work that spreads across legal, security and web teams, not server time.
- Where internal time grows: site-by-site configuration, consent and retention reviews, access reviews and evidence collection for each release.
- When a fixed-scope implementation helps: when the scope covers a defined number of sites, documented configuration baselines and a repeatable change process that internal staff can follow.
- When a partner adds cost without saving: when the estate is still a single site with simple reporting, or when the governance decisions have not been made and a partner would have to wait for them.
- What to check: whether the partner's written scope lists the sites, the identity integration, the logging and the evidence the organization will receive.
Before comparing quotes, count the staff hours your teams spend on governance each quarter, then ask each partner to price the same list of sites and controls.
Matomo runs on PHP with MySQL or MariaDB behind a web server, and Plausible requires Docker, Docker Compose and a ClickHouse-capable CPU. Umami needs Node.js and PostgreSQL for a source install, although its Docker Compose file bundles a database. A team that has never operated these components will spend its first weeks learning them, and that learning time is often the largest internal cost. Mistakes in database configuration or storage sizing can also surface later as missing data.
- Where internal time grows: learning the stack, diagnosing database and container issues, and tuning storage and memory as traffic grows.
- When a fixed-scope implementation helps: when the partner delivers a documented, tested install with monitoring, backups and a runbook that the team can follow without outside help.
- When a partner adds cost without saving: when the team already runs Linux and databases for other systems and can absorb the analytics stack in its normal rota.
- What to check: which operating system, database and container versions the partner will support, and whether support covers those components after go-live.
Ask for the exact component list in the written scope, then decide whether your team or the partner will own each one after handover.
When a subscription still makes sense
A hosted subscription is the lower-cost and lower-risk path when three conditions hold at once: traffic fits a published plan, no data residency or consent rule forces the data onto your own servers, and nobody on your team can own upgrades, backups and uptime. If any one of those fails, the comparison changes. Umami Cloud Hobby is listed at $0 per month for up to 100K events with 6 months of retention, Pro at $20 per month for 1 million events with 2 years of retention, and Business at $200 per month for 10 million events with 5 years of retention. Plausible Cloud starts at $9 per month for 10k monthly pageviews. Confirm current prices on each vendor's pricing page, because subscription prices change.
Check the overage terms before you choose a tier. Umami Cloud charges $0.00003 per extra event on Pro and $0.00002 per extra event on Business, so a traffic spike in a busy month can move the bill more than the tier price suggests. Also confirm what happens to historical data when a plan's retention window ends. Umami Cloud adds email reports and a streaming API that the self-hosted edition does not include, so a team that depends on scheduled reports or a live data feed may need the hosted edition even if the traffic is modest. On Plausible, the self-hosted Community Edition receives security fixes only when the operator applies a release, while Plausible Cloud ships updates multiple times per week. That gap matters for any team without a patch routine.
Subscriptions also carry a cost that is easy to miss: the data still leaves your control. A hosted plan moves hosting, retention and access decisions to the vendor, so your vendor risk review, data processing terms and transfer documentation have to cover that provider. Ask where the hosted data is stored, which sub-processors receive it, how deletion requests are handled and whether you can export your data if you leave. Community Edition users can export and import data to and from Plausible Cloud, which keeps a later move possible. If your analysis shows that a subscription is cheapest today, record the traffic level and the exit path in the decision file so the choice can be reviewed when volume or policy changes.
Questions buyers ask about web analytics cost and effort
What is the licence cost of self-hosted Matomo, Plausible or Umami?
The software itself carries no licence fee on the self-hosted path for any of the three, but that does not make the total free. Matomo On-Premise Community is listed as free forever with unlimited users and hits, Plausible Community Edition is open source under AGPLv3, and Umami is MIT licensed and can be self-hosted for free. The costs that remain are the server or cloud infrastructure, storage, backups, the time to install and upgrade, and any paid add-ons. Matomo's Heatmap and Session Recording plugin is a paid premium plugin sold per number of users, so confirm whether you need it, because it changes the consent position as well as the budget. Ask each vendor to confirm the current edition terms before you model the spend.
How much internal effort does self-hosted analytics upkeep take each month?
The effort depends on traffic, edition and how much automation you build, so no single monthly figure applies. Plausible's self-hosted page states that Community Edition operators manage installation, upgrades, capacity, uptime, backups and security themselves, and that security fixes arrive only when the operator applies the release. Matomo's sizing guidance separates app and database servers once traffic reaches the 10 million pageviews a month tier, which adds patching and monitoring work for two systems. Upkeep recurs every month, while installation and initial configuration are one-time. Ask your team to estimate patch windows, backup restore tests and on-call coverage, and compare that against the SaaS plan you would otherwise buy.
Can our internal team install and run self-hosted web analytics without a partner?
Often yes for a single site with modest traffic, provided you have someone comfortable with Docker, a Linux server, a reverse proxy, TLS and database backups. Plausible's Community Edition requires Docker and Docker Compose, a CPU supporting SSE 4.2 or NEON, and at least 2 GB of RAM. Umami publishes a Docker Compose file that starts it with a bundled PostgreSQL database. The gaps usually appear later: consent configuration, identity integration with your single sign-on, multi-site setup, capacity planning, and restoring data after a failed upgrade. Decide early which of these your team owns, and write that split into the internal plan so nothing falls between teams.
How long does an implementation take, and what does it need from our side?
The timeline depends on the number of sites, the consent position you need, the hosting environment and how many systems the analytics must connect to. No duration figure has been supplied for this work, so ask any partner to state the timeline in the written scope rather than relying on a general estimate. Your side typically supplies a hosting target that meets your data residency rules, named owners for access and retention decisions, a list of pages to exclude from collection, and access to the sites where the tracking script goes. Where you plan to migrate historical data, confirm early what the import can carry, since Matomo's importer brings in aggregated report data only.
What drives a partner quote for self-hosted analytics up or down?
The written scope drives the quote more than any other factor. Expect the price to rise with the number of sites and domains, the traffic tier, whether you need separate database and application servers, the consent and privacy configuration, data migration from Google Analytics, integrations with identity providers and reporting tools, and the length of post-launch support. Expect it to fall when you standardize on one platform, reuse an existing hosting environment and limit the first phase to core reporting. DeployOpen does not publish a price list, and most engagements are fixed-scope, so a quote follows from the written scope. Ask for line items for installation, configuration, data migration, documentation, handover and any retainer for upgrades and support.
When does a SaaS analytics plan cost less than self-hosting?
A SaaS plan usually costs less when traffic is low, you have no spare platform capacity, and your team would otherwise carry the upkeep alone. Published prices give a reference point: Plausible Cloud lists plans from $9 per month for 10k monthly pageviews, Umami Cloud Pro lists $20 per month for 1 million events, and Matomo Cloud starts at 29 (excluding tax) per month. Self-hosting tends to win when data must stay in your own infrastructure, when traffic grows beyond the tiers you want to pay for, or when a regulator or internal policy rules out third-party hosting. Compare the SaaS subscription with the infrastructure, staff time and partner costs of self-hosting over the same period, and confirm current prices with each vendor.
What to ask for in a fixed-scope quote
A fixed-scope quote is only as comparable as the written scope behind it. DeployOpen agrees scope, deliverables and timelines in writing before work starts, and any quote follows from that document, so ask every bidder, including your internal team, to state the same items. Start with the sites and pageview tiers in scope, counted per site and per environment, and the edition and version of Matomo, Plausible or Umami to be deployed. Name the hosting environment explicitly, including the cloud account or data center, whether a separate database server is included, and whether the work covers an air-gapped network. A quote that does not fix these items cannot be compared with another.
Next, make the consent and privacy configuration a named deliverable. The scope should say which tracking features are enabled (for example, whether User ID, heatmaps or session recording are in or out), which retention and IP settings apply, and who signs off the configuration before go-live. A named approver on your side is the item most often missing from a quote. Also state the migration scope and data limits: whether historical data is imported, from which source, and whether only aggregated data is moved. Matomo's importer and Plausible's Google Analytics import both have documented limits on what carries over, so the quote should say what is excluded.
Finally, pin down the operating terms. The scope should define who applies upgrades and security patches, how often, and what happens when a release is missed, since Plausible's Community Edition gets security fixes only when the operator applies them. Require backup and restore tests as an acceptance criterion, not just a backup job, and state the support hours after go-live and the response path for incidents. Acceptance criteria should be measurable: tracking verified on each site, a successful restore into a test environment, and a signed handover of documentation. Ask for the quote to separate one-time implementation fees from recurring support or retainer fees, so you can compare the first year with the later years.
How DeployOpen scopes, delivers and supports a fixed-scope analytics implementation
DeployOpen plans, implements, hardens, documents and supports self-hosted analytics platforms inside your own infrastructure, so the build-versus-partner-versus-SaaS decision rests on a written scope rather than an estimate. Engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work begins.
How we scope
- Document the current analytics tags, sites, subdomains and traffic volume that the platform must measure.
- Define which edition, Matomo, Plausible Community Edition or Umami, fits the required features and hosting model.
- Agree in writing which cost lines the scope covers, including hosting, installation, migration and handover.
How we build
- Install the chosen platform in your cloud account, data center or air-gapped network, with the sizing your traffic requires.
- Configure data retention, IP handling and tracking settings, and test that collection matches the agreed design.
- Test the deployment, including backups and restore, and document the setup, capacity assumptions and operating steps.
How we hand over
- Hand over runbooks for upgrades, backups, capacity changes and access administration so your team can run the platform.
- Deliver a cost baseline showing which lines recur, such as hosting and your staff time, and which were one-time.
- Provide configuration and control documentation your auditors or compliance team can use as evidence, without us issuing any attestation.
How we support
- Support ongoing operations, upgrades and continuous testing through a retainer agreed separately from the initial scope.
- Review each new platform release and apply upgrades against the written scope and your change process.
- Confirm with your team which support responsibilities stay internal and which move to a retainer before go-live.
