Self-Hosted Analytics on UK VPS: Plausible vs Matomo vs Umami (GDPR-Friendly) 2026

Running your own self-hosted analytics means the software that measures your website traffic lives on a server you control, so visitor data never leaves your infrastructure and never lands in Google’s data centres. For UK businesses tightening up on data protection, that single change fixes a surprising number of compliance headaches at once. This guide compares Plausible, Matomo and Umami, and shows how to run any of them on a UK VPS.

What Is Self-Hosted Analytics?

Self-hosted analytics is web analytics software that you install and run on your own server rather than relying on a third-party service such as Google Analytics 4 (GA4). With a hosted service, every page view is sent to a company’s cloud, processed on their terms, and stored wherever they choose. With the self-hosted model, the tracking script talks to your VPS, the data is written to a database you own, and you decide the retention period, the access controls and the physical location of every record.

That distinction matters most for two reasons: data ownership and data residency. You are no longer a product feeding an advertising ecosystem, and you can keep every byte of visitor data inside the UK. Combined with modern privacy-friendly analytics tools that collect no personal data at all, this is the cleanest route to a genuine GDPR-compliant hosting setup.

Why Self-Host Your Web Analytics

There are practical, legal and technical reasons UK site owners are moving away from GA4. None of them require you to hate Google; they simply reflect what a growing number of businesses now need from a Google Analytics alternative.

• UK data residency: keep visitor data on a UK VPS, not routed to servers outside the UK or EU.
• Data ownership: your traffic data is your asset, exportable and never mined for advertising.
• Often no cookie banner: cookieless tools that store no personal data frequently avoid the need for a consent pop-up.
• Simpler reporting: a clean single-page dashboard instead of GA4’s steep learning curve.
• No sampling: you see 100% of your traffic, not a statistical estimate.

The compliance angle is the strongest driver. If you also run WooCommerce or handle customer accounts, it pays to read our UK Data Protection Act 2025 checklist alongside this guide, because analytics is only one part of a wider obligation.

What You Need for Self-Hosted Analytics

Getting started with self-hosted analytics is well within reach of any competent site owner or agency. You will need a small UK VPS (two vCPUs and 2–4GB of RAM comfortably runs any of these tools for a typical business site), a domain or subdomain such as analytics.yourdomain.co.uk, Docker and Docker Compose installed, and an SSL certificate through a reverse proxy. If you would rather someone else patched and maintained the box, weigh up managed versus unmanaged VPS hosting before you commit.

Plausible vs Matomo vs Umami

The three leading open-source options each suit a different kind of site. In the Plausible vs Matomo vs Umami debate, the honest answer is that they are not really competitors so much as points on a spectrum from “minimal and cookieless” to “full GA replacement”. The table below summarises the differences.

Plausible is lightweight, open-source and cookieless by design. It collects no personal data and does no cross-site tracking, which makes it GDPR, PECR and CCPA friendly out of the box. Matomo is the closest thing to a like-for-like GA replacement, with funnels, heatmaps, goals and e-commerce reporting; it is more resource-hungry but hard to beat for depth. Umami is the minimalist’s choice: fast, cookieless, privacy-first and trivial to deploy, with fewer features but a beautifully clean interface.

How to Install Plausible on UK VPS

Plausible Community Edition ships as a Docker Compose stack, so installation on a UK VPS is a matter of cloning the repository and configuring a few environment variables. Point your subdomain’s DNS at the server first.

# Clone the community edition
git clone https://github.com/plausible/community-edition plausible
cd plausible

# Generate a secret key and add it to the env file
openssl rand -base64 48

# Edit plausible-conf.env with your domain and secret
# BASE_URL=https://analytics.yourdomain.co.uk
# SECRET_KEY_BASE=your-generated-key

# Start the stack
docker compose up -d

Plausible listens on an internal port (8000 by default). Put a reverse proxy such as Caddy or Nginx in front to terminate SSL and serve it on your subdomain. Once it is up, log in, add your website in the dashboard, and copy the snippet it gives you. If Docker on a VPS is new to you, our Docker Compose on UK VPS guide walks through reverse proxies and SSL in detail.

How to Install Matomo and Umami

Matomo via Docker

Matomo runs happily as a Docker Compose stack alongside a MariaDB database. A minimal compose.yaml looks like this:

services:
  db:
    image: mariadb:11
    environment:
      - MYSQL_ROOT_PASSWORD=change-me
      - MYSQL_DATABASE=matomo
    volumes:
      - db:/var/lib/mysql
  matomo:
    image: matomo:latest
    ports:
      - "8080:80"
    volumes:
      - matomo:/var/www/html
volumes:
  db:
  matomo:

Run docker compose up -d, browse to the server on port 8080, and follow the web installer to connect the database and create your admin account. As with Plausible, place it behind a reverse proxy with SSL.

Umami via Docker

Umami is the quickest of the three to stand up. It needs only a Node.js container and a PostgreSQL database:

services:
  umami:
    image: ghcr.io/umami-software/umami:postgresql-latest
    ports:
      - "3000:3000"
    environment:
      - DATABASE_URL=postgresql://umami:umami@db:5432/umami
      - DATABASE_TYPE=postgresql
      - APP_SECRET=change-me
    depends_on:
      - db
  db:
    image: postgres:16-alpine
    environment:
      - POSTGRES_DB=umami
      - POSTGRES_USER=umami
      - POSTGRES_PASSWORD=umami
    volumes:
      - db:/var/lib/postgresql/data
volumes:
  db:

Log in with the default credentials, change the password immediately, add your website and grab the tracking snippet. A UK VPS from a provider like UK Speed keeps all of this on British soil from the first request onwards.

Add the Tracking Script to WordPress

Whichever tool you chose, the final step is the same: place a small JavaScript snippet in the <head> of every page. Plausible and Umami give you a one-line script tag; Matomo gives you a short block.

<!-- Example: Plausible -->
<script defer data-domain="yourdomain.co.uk"
  src="https://analytics.yourdomain.co.uk/js/script.js"></script>

On WordPress you have three easy options. The simplest is a header-insert plugin such as WPCode, which lets you paste the snippet into a site-wide header without touching theme files. Alternatively, add it to your theme’s header.php (or a child theme) before the closing head tag. Matomo also publishes an official WordPress plugin that connects your site to a self-hosted Matomo instance and reports inside the dashboard. Because these scripts are tiny, they will not undermine the page speed that helps your SEO rankings — a welcome contrast to GA4’s heavier tag.

Configure Analytics for GDPR Compliance

Choosing a privacy-friendly tool is the start, not the end, of GDPR-compliant analytics. The Privacy and Electronic Communications Regulations (PECR) govern cookies and similar technologies in the UK, and they sit alongside the UK GDPR. The key point is that cookieless tools which store no personal data and set no cookies typically fall outside the consent requirement for cookie banners — but this depends entirely on how you configure them, so verify your setup against the ICO guidance on cookies and PECR rather than assuming.

Whichever tool you run, apply these settings to stay on the right side of the rules:

• Anonymise IP addresses so no individual visitor can be identified (Matomo has a built-in setting; Plausible and Umami never store them).
• Set a data retention period and delete raw data you no longer need.
• Keep data in the UK or EU by hosting on a UK VPS — this satisfies data residency expectations.
• Run Matomo in cookieless mode if you want to avoid a banner; in its default cookie mode you will still need consent.
• Document your setup in your privacy policy so visitors know what is measured and where it lives.

The reassuring part is that Plausible and Umami are designed to collect no personal data in the first place, which removes most of the risk before you configure anything. Matomo can match them but needs the cookieless option switched on. In all cases, “no banner” is a consequence of your configuration, not an automatic guarantee.

Choose the Right Analytics Tool

Match the tool to the questions you actually need to answer. If you run a blog, a SaaS product or a marketing site and mainly want to know which pages and channels perform, Plausible gives you a fast, cookieless dashboard with almost nothing to maintain. If you run WooCommerce or need funnels, heatmaps, goals and detailed e-commerce reporting, Matomo is the true GA4 replacement and worth its heavier footprint. If you are a developer or agency who values a lean, minimal footprint above all, Umami is the neatest and cheapest to run.

All three deliver the same core wins: data ownership, UK data residency and cookieless, privacy-friendly analytics. The right choice is simply the one whose feature depth matches your needs.

Conclusion

Self-hosted analytics has matured to the point where privacy compliance and useful reporting are no longer a trade-off. Running Plausible, Matomo or Umami on a UK VPS keeps every visitor record in the UK, hands you full ownership of the data, and in most cookieless configurations removes the need for a consent banner. It is one of the highest-value changes a privacy-conscious UK business can make in 2026.

• Pick your tool: Plausible for simplicity, Matomo for depth, Umami for a minimal footprint.
• Spin up a small UK VPS with Docker and a subdomain for the dashboard.
• Deploy with Docker Compose behind a reverse proxy with SSL.
• Add the tracking snippet, anonymise IPs, set retention, and confirm your PECR position against ICO guidance.