Self-Hosted Analytics: Tools, Server Costs, Setup and What Breaks

Self-hosted analytics means running an open-source web analytics tool, such as Umami, Plausible Community Edition or Matomo, on a server you control, so every pageview and event lands in your own database instead of a vendor’s cloud. You get the raw data, no per-pageview bill and a say over where the data lives. In exchange you become the operator: server, updates, backups, proxy setup and bot filtering are your job.

This guide compares the tools that are worth installing in 2026, gives the server requirements from each project’s own docs, walks through setup step by step, prices the whole thing including your time, and lists the failure modes that quietly break the numbers. It ends with the part most guides skip: turning self-hosted pageviews into conversions and money per landing page.

What self-hosted analytics is, and what it is not

A self-hosted analytics setup has three parts: a small JavaScript tracker on your pages, a collection endpoint that receives each hit, and a database plus dashboard where the reports live. In a self-hosted setup the last two run on your machine. The tracker usually sends a hit when a page loads and when you fire custom events such as a form submit.

Three things often get mixed up with it:

• Self-hosted Google Analytics does not exist. GA4 is a hosted Google service with no on-premise edition. A server-side tag container you run yourself still forwards the data to Google, so you do not own the reporting database.
• Server log analyzers are a different approach. Tools like AWStats and GoAccess read your web server’s access logs. They need no JavaScript and see visitors who block scripts, but they also count bots, cached assets and crawlers, and they cannot see what happens inside the page, like a form submit handled by JavaScript.
• Self-hosted is not “self-serve.” Self-serve analytics means business users can build their own reports without a data team, usually in a BI tool such as Looker Studio, Power BI, Tableau or Metabase (Metabase can itself be self-hosted). It describes who builds reports, not where the software runs.

Why teams self-host, and what it does not fix

The reasons cluster into four:

• Data ownership. Every row sits in your database. You can query it with SQL, keep it as long as you like, delete it on request and move it when you change tools.
• Data location and privacy posture. You choose the country the server is in, and no analytics vendor sits between your visitors and your database. Most of the popular tools are cookieless by default.
• Predictable cost. Hosted privacy tools usually bill by monthly pageviews or events. A server bill grows in steps, not per hit, which matters most on high-traffic sites.
• Fewer blocked hits. A tracker served from your own subdomain is not on the same blocklists as a well-known vendor domain. In a Plausible GitHub discussion, a maintainer said their own self-hosted instance recorded more traffic than the cloud one because the cloud domain is blocked by uBlock and Brave.

What self-hosting does not do on its own:

• It does not make you compliant. You are now the party deciding what is collected and for how long, so retention, IP handling and your privacy notice are on you.
• It does not give you more features. Several vendors keep their best features in the paid cloud product (details below).
• It does not replace Google Ads conversion tracking or audience features. If your ad bidding depends on GA4 conversions, you still need GA4 or a direct ads tag.
• It does not tell you what a visit was worth. Most self-hosted tools count visits well and value them poorly. See the last section.

Self-hosted analytics tools compared

The list below covers every tool that appears in the current search results and community threads. Licenses are the projects’ own; “stack” is what you have to run and maintain.

One pattern is worth knowing before you choose: the companies behind most of these tools earn their money from hosted plans, so the self-hosted edition is often deliberately smaller. Plausible is explicit about it. Its GitHub README says the Community Edition is a long-term release published twice a year, uses basic bot filtering based on the User-Agent header and referrer spam lists, and leaves out marketing funnels, ecommerce revenue goals, SSO and the sites API. It is also community supported only. Read the equivalent page for any tool before you assume the self-hosted build matches the demo.

Which tool to pick

If you are still weighing hosted options too, our GA4 alternative guide covers the cloud tools, product analytics and enterprise suites by category. For app-style analytics, see PostHog alternatives.

Server requirements

Sizing advice in blog posts varies a lot, so start from each project’s own numbers. Matomo publishes the most detailed table. From its on-premise requirements FAQ:

The same page lists Matomo 6 as needing PHP 8.1 or newer and MySQL 8.0+ or MariaDB 10.6+. Matomo also asks you to replace its default browser-triggered report archiving with an hourly cron job once traffic grows past a small site, or dashboards get slow.

For the other tools, the practical rules are:

• Umami is one Node.js app and a PostgreSQL database. According to the Umami environment variable docs, the database connection string is the only required setting, which is why it is the easiest to get running.
• Plausible CE bundles ClickHouse, which is memory-hungry and needs a modern CPU instruction set. Read the requirements in the community-edition repository before you buy the smallest server on offer.
• PostHog runs many services and is the heaviest by a wide margin. Treat it as a project, not a weekend install.
• Shared hosting works only for PHP tools (Matomo, Open Web Analytics, DooStats). Docker tools need a VPS or a container platform. Umami can also run on a serverless platform with a hosted PostgreSQL database, which removes the server but means your data sits with those two providers.

How to set up self-hosted analytics in 10 steps

The commands differ by tool, but the shape is the same for all of them. Follow your tool’s official install guide for the exact files; these steps are the decisions and checks around it.

Step 1: Pick the tool and a tracking hostname

Use the decision table above. Then choose a subdomain of your own site on the standard HTTPS port 443. Avoid obvious names like analytics. or stats., which blocklists match, and avoid non-standard ports: in the Plausible discussion above, moving the script off port 8000 brought the self-hosted counts back in line, and some school and office firewalls block other ports.

Step 2: Provision the server

Size it from the official requirements, not from the cheapest plan. If data location matters to you, pick a region accordingly, and remember that a CDN or proxy service in front of the endpoint is another company processing the data.

Step 3: Deploy the stack

Most tools ship a Docker Compose file. You set secrets (for example Umami’s APP_SECRET, Plausible’s SECRET_KEY_BASE), the public URL and the database connection, then start the containers. Pin a version tag instead of latest so an update never happens by accident.

Step 4: Put a reverse proxy in front and pass the real visitor IP

Caddy, nginx or Traefik terminates HTTPS and forwards requests to the app. This is the step that silently breaks most installs: unless the proxy forwards the visitor’s address in a header the app trusts, every hit arrives from the proxy’s own IP. Unique visitor counts collapse and every visitor appears to be in your server’s country. Umami documents a CLIENT_IP_HEADER variable for proxies that use non-standard headers. A minimal Caddy setup looks like this:

# Caddyfile
t.example.com {
    reverse_proxy localhost:3000
    # Caddy sets X-Forwarded-For by default; make sure the app reads it.
    # Behind a CDN, trust only the CDN's ranges and use its client IP header.
}

Step 5: Add the tracking script

Add the snippet once, in the layout every page shares, with defer, loaded from your own hostname. On a single-page app, confirm the tool records route changes. Never load two trackers that use the same global name on one page.

<script defer src="https://t.example.com/script.js" data-website-id="YOUR-ID"></script>

Step 6: Exclude yourself and check bot filtering

Exclude your own visits and staging hostnames. Check that bot filtering is on: Umami excludes bots by default, while Plausible CE’s filtering is the basic version described above, so watch for sudden spikes from data center traffic.

Step 7: Set retention and IP handling

Decide how long raw events are kept, whether IP addresses are stored, truncated or discarded, and write that into your privacy notice. These are your choices now, not a vendor’s.

Step 8: Back up and test a restore

Schedule a nightly database dump (for example pg_dump for PostgreSQL, mariadb-dump for MariaDB, and ClickHouse’s own backup for Plausible’s event data) and copy it off the server. Restore one to a spare machine once. A backup you have never restored is a guess.

Step 9: Plan updates and monitoring

Watch the project’s releases, read the upgrade notes (database migrations are where updates fail), and update on a schedule. Add an uptime check on the tracking endpoint and an alert on disk usage. An analytics server that is down loses data for good: hits sent while it is offline are not resent.

Step 10: Run it next to your current tool

Run both for two to four weeks. Expect different totals, because each tool defines visitors and sessions differently and is blocked differently. Compare trends and the ranking of pages and sources, not exact counts. Export your old tool’s history before you remove it. Matomo has a Google Analytics importer; check whether your new tool has one before you count on it.

What it really costs: a worked example

Most comparisons price only the server. The bigger cost is the time you spend on it. Here is the full calculation with illustrative numbers; swap in your own.

Compare that with a hosted plan of the same tool. At an illustrative $20 a month ($240 a year), self-hosting costs more in both years. At an illustrative $150 a month ($1,800 a year), which is the range hosted tools reach at high traffic, self-hosting wins from year one. The break-even point is:

With the numbers above that is $14 (server and backup) + $60 = $74 a month. Below that hosted price, self-host only for reasons other than money: data location, ownership or the learning. If your maintenance time is really zero, you are not maintaining it, and that risk shows up later as a breach or a lost database.

Failure modes: why self-hosted numbers go wrong

When a self-hosted install reports odd numbers, the cause is almost always in this table.

Privacy, consent and licenses

Is self-hosting legal? Yes. The licenses of all the open-source tools above allow you to run them on your own server for any purpose. Two license details matter. Plausible’s AGPLv3 says that if you modify the code and let others use it over a network, you must publish your changes; running it unmodified for your own site triggers nothing. Matomo’s core is GPLv3 and some of its plugins, such as heatmaps and session recording, are sold separately.

Consent. Whether you need a cookie banner depends on where your visitors are and what the tool stores on their device, not on where the server sits. Cookieless tools that keep no persistent identifier are designed to avoid consent prompts in many jurisdictions, but EU rules are interpreted by each country’s regulator, so check your own. A self-hosted Matomo with cookies turned on is no more consent-free than any other cookie-based tool. Our cookieless tracking guide explains the methods and what each one stores.

Data location. A server in your chosen country removes the analytics vendor from the data flow. Your hosting company, backup storage and any CDN in front of the endpoint still process the data, so they belong in your records and privacy notice.

Where the top results disagree

• How much memory Umami needs. Estimates in current guides range from about 256 MB to 1 GB. Both can be right: the app idles small, and PostgreSQL grows with your data. Start small and watch memory for a month.
• Whether Fathom Lite is “well maintained.” One list calls it maintained for bug fixes, another calls it stale. Both agree it gets no new features and that the company builds its paid cloud product. For an internet-facing service, check the date of the last release and image yourself before deploying.
• Matomo’s minimum server. Guides quote anything from 2 GB to 8 GB for a small site. Matomo’s own table says 2 CPU and 2 GB RAM for up to 100,000 pageviews a month, so start there.
• Whether self-hosting is easy. Some guides call it a 20-minute job; developers in community threads describe failing to get Umami and Plausible running. The difference is usually the proxy, TLS and IP steps above, which quick-start guides skip.

When self-hosting is the wrong call

• Nobody on the team can SSH into a server and fix it on a bad day.
• Your small traffic puts the hosted plan well under the break-even price above, and data location is not a requirement.
• Your ad bidding depends on GA4 conversions, audiences or Google Ads imports. Keep GA4 for that and add a second tool only if you will read it.
• You need certifications such as SOC 2 or HIPAA-grade audit trails for the analytics processor. You would have to build and audit that yourself.

From self-hosted pageviews to conversions and value

Self-hosted tools are good at counting visits by page and source. The question a business asks next is which pages and channels produce leads and revenue, and how much. Getting there takes three additions on top of any tool:

• Track the actions that matter: form submits, calls, email clicks, demo bookings and purchases, as custom events or goals.
• Give each action a value, using the method in how to calculate conversion value.
• Report by landing page and channel, because search engines hide most keywords and AI assistants send visits from their own referrers.

An illustrative example shows why the third step changes decisions:

The value per lead here is an illustrative $1,500 average deal times a 20% lead-to-customer rate, which is $300. A traffic report ranks the blog post first; a value report shows the smaller page is worth three times as much. Our SEO conversion tracking guide covers the full setup. If you would rather not build this on top of a self-hosted install, SEOConversion is a cookieless, first-party script that tracks forms, calls and purchases, puts a value on each conversion and reports it by landing page for organic search and AI assistants.

FAQ