SSD Nodes Learn Hosting plans →
How to do am Matt ConnorBy Matt Connor

Which self-hosted analytics fit run for small VPS?

Compare GoatCounter, Medama, Umami, Plausible, Rybbit, Matomo and GoAccess: 1 GB RAM options, ClickHouse needs, disk growth and ad blocker gaps.

Which self-hosted web analytics tool you suppose run for your VPS?

Self-hosted web analytics get two families, and if you pick the wrong family, e go cost you pass if you just pick the wrong product. One family dey run small script for visitor browser and e dey store wetin that script report. The other family dey read the access log wey your web server don already write. Everything wey come after that, including the database and the memory wey e need, depend on that one choice.

The short answer for small server: GoatCounter and Medama fit run for 1 GB RAM, because each one na just single process wey dey use local database files: one for GoatCounter, two for Medama. Umami add Postgres container and e give you dashboard wey person wey no sabi tech fit read. Plausible Community Edition and Rybbit both dey run ClickHouse, so make you plan for 2 GB of RAM or more. Matomo na the full product and e need server wey size fit your traffic. GoAccess no dey add anything to the page at all, because e just dey read log wey already dey ground.

Script tag or server log: wetin each one fit see

Script tag dey measure browsers. Page go load, script go run, then e go send one request go your collector. Anything wey break that chain no go visible to you: JavaScript wey dem turn off, filter list wey block the request, failed request go collector, or crawler wey no ever run scripts.

Log parser dey measure requests. Your web server go write one line for every request whether you install anything or not, so the data don already dey disk. E dey see every crawler and every hit on file wey no carry script tag. E no fit see wetin happen inside browser, and e no fit see page wey browser cache or CDN (content delivery network) serve for front of your box, because that request no reach your server.

The two numbers no go match, and neither one wrong. Matomo fit do both, and e document wetin log import give up compared with JavaScript tracker: screen resolution and page titles, events, content tracking, heatmaps, session recordings and form analytics. Na these things you lose when you count requests instead of browsers.

Bot traffic na the other part of the difference. Log-based counts include crawlers unless you filter dem, and for ordinary site, crawler share fit big enough to change your conclusions. GoAccess and Matomo's log import both filter known bots. Neither one fit filter crawler wey dey lie about user agent. Na good reason to pair any log-based counting with blocking AI crawlers for server and read the log after the block, no be before am.

GoAccess: log wey you already get fit give analytics

Install am from the project own Debian and Ubuntu repository, because distribution packages dey behind newer releases.

wget -O - https://deb.goaccess.io/gnugpg.key | gpg --dearmor | sudo tee /usr/share/keyrings/goaccess.gpg >/dev/null
echo "deb [signed-by=/usr/share/keyrings/goaccess.gpg arch=$(dpkg --print-architecture)] https://deb.goaccess.io/ $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/goaccess.list
sudo apt-get update
sudo apt-get install goaccess

Then point am to the log and write a static report.

goaccess /var/log/nginx/access.log -o ~/report.html --log-format=COMBINED

That command go fail with Permission denied for ordinary user, because for Ubuntu, root own the nginx log and group adm dey use am. Add yourself to that group with sudo usermod -aG adm $USER, then log out and log in again, because system dey read group membership when you log in. Run id and check say adm dey inside the list before you try again.

Report wey you generate from the live log only cover wetin logrotate never move yet. Yesterday requests dey inside access.log.1, and older ones don compress, so weekly view need read the rotated files too.

zcat /var/log/nginx/access.log.*.gz | goaccess - --log-format=COMBINED -o ~/last-week.html

Live mode dey available too, na --real-time-html, and e dey update the page through WebSocket. E need second port and separate proxy rule. For most sites, hourly report wey cron write dey enough, and e get fewer things to secure.

GoatCounter: one Go binary and one SQLite file

GoatCounter dey ship as statically compiled binary, so you no need install any runtime. Download one build from the release page and run am, or use the image.

docker run -p 8080:8080 -v goatcounter-data:/home/goatcounter/goatcounter-data arp242/goatcounter

When you run am as binary, goatcounter serve dey listen on port 8080 and create SQLite for ./goatcounter-data/db.sqlite3. Create the first site from command line instead of the web wizard when the instance don already dey behind proxy.

goatcounter db create site -vhost=stats.example.com -user.email=me@example.com

E fit manage e own certificate with goatcounter serve -listen=:443 -tls=tls,rdr,acme, using ACME (automatic certificate management environment). This one useful for server wey no dey run any other thing. If nginx or Caddy already dey control port 443, leave GoatCounter for 8080 and proxy traffic go am instead. The tracking script dey about 3.5K according to the project estimate, and tracking pixel dey available for pages wey no get JavaScript. If SQLite become the limit for busy site, the same binary fit use Postgres with goatcounter serve -db 'postgresql+dbname=goatcounter'. Backup na just copy the file, and na this be the main reason this kind tool dey useful.

Medama: one container wey dey claim 256 MB

Medama na the newest single binary option wey dey here. E no dey use cookie by design and the project talk say the tracker no reach 1 KB, plus small sites wey dey run for virtual machines with 256 MB of memory. Na wetin the project publish be this, no be numbers wey we measure for this guide.

docker volume create medama-data
docker run -d -p 127.0.0.1:8080:8080 -v medama-data:/app/data ghcr.io/medama-io/medama:latest

The official command dey publish the port as 8080:8080. The loopback prefix wey dey up so na sake of something, and the reverse proxy section go explain why. Medama dey keep im data for two database files, me_meta.db and me_analytics.db, and the container dey write dem under /app/data, so make you back up the whole volume instead of just one file. The first login na admin with the password CHANGE_ME_ON_FIRST_LOGIN, and the name of that password na the instruction.

One failure mode wey dem document fit catch you. Login only dey work over HTTPS or for localhost, so if you set up the proxy before the certificate, the form go reject correct password and e no go print the reason. Finish the TLS (transport layer security) setup first, before you log in.

Umami: Postgres, plus dashboard wey pipo sabi

git clone https://github.com/umami-software/umami.git
cd umami
docker compose up -d

Dat one go start di application for port 3000 wit one PostgreSQL container beside am. Di docs tok say PostgreSQL v12.14 na di minimum, and Node.js 20.19 or new pass dat, wit 22 LTS wey dem recommend, if you build am from source instead. One prebuilt image dey, docker.umami.is/umami-software/umami:latest, wey need DATABASE_URL make you point am go database wey you don dey run already.

Di first login na admin wit di password umami. Change am before you point DNS go di box, because di instance go dey reachable from internet di moment di record resolve and di proxy answer. For di Compose details, environment files and restart policy, check one Docker Compose stack for VPS instead of just copy one stack wey you never read.

Di footprint na one Node process plus Postgres. Dat one heavy pass single binary but e light well-well pass anytin wey dey run ClickHouse.

Plausible Community Edition: ClickHouse dey set RAM floor

git clone -b v3.2.1 --single-branch https://github.com/plausible/community-edition plausible-ce
cd plausible-ce
touch .env
echo "BASE_URL=https://stats.example.com" >> .env
echo "SECRET_KEY_BASE=$(openssl rand -base64 48)" >> .env
docker compose up -d

Version v3.2.1 na im be current version as of November 2026, and the clone command pin am for there sake of safety. The stack get three parts: the application, Postgres for accounts and settings, and ClickHouse for the event data. SECRET_KEY_BASE must be at least 64 byte string, na wetin the openssl call dey produce.

Plausible requirements talk say you need at least 2 GB of RAM so that ClickHouse and the application no go meet the out of memory killer, and CPU wey support SSE 4.2 or NEON, wey ClickHouse need. That second requirement dey important make you check am before you buy, and na one of the practical differences for how to choose between ARM and x86 VPS. ClickHouse go also take as much memory as e think say dey available, so if you dey use shared box, set limit as dem explain for how to cap container memory for Compose.

BASE_URL must match the public URL exactly. If e no match, you go log in, the app go redirect go wrong host, and the session cookie go write for domain wey your browser no dey, so you go land back for login form without any error message.

The compose file wey dem ship no dey publish port, because the plan be say proxy go dey front. Add override wey go publish the default application port for loopback only.

cat > compose.override.yml << EOF
services:
    plausible:
        ports:
            - 127.0.0.1:8000:8000
EOF

Matomo: di full product, and di server wey e need

Matomo dey run on top PHP wit MySQL or MariaDB, dis mean say e fit di classic web stack pass container stack. Na dis one be di only tool for dis list wey dey publish hardware guidance base on traffic volume.

ChartMatomo sizing guidance by monthly pageviews
Di data wey dey behind dis chart
[
  {
    "label": "100K/month",
    "cpu_cores": 2,
    "ram_gb": 2,
    "disk_gb": 50
  },
  {
    "label": "1M/month",
    "cpu_cores": 4,
    "ram_gb": 8,
    "disk_gb": 250
  },
  {
    "label": "10M/month",
    "cpu_cores": 8,
    "ram_gb": 16,
    "disk_gb": 400
  }
]

Dem be di minimum requirements wey Matomo publish as of November 2026, no be measurement wey we take for dis guide. Up to 100,000 pageviews per month, e ask for 2 CPU cores, 2 GB of RAM and 50 GB of SSD, and one server dey hold both di application and di database. At 1M/month e go turn to 8 GB of RAM and 250 GB of disk. At 10M/month Matomo recommend two servers, and di last row show di database server: 16 GB of RAM and 400 GB of disk. Read dose disk figures side-by-side wit di single binary options, wia di whole dataset dey stay inside one or two local database files.

Archiving na di tin wey dey surprise pipo. By default, Matomo dey build im reports wen pesin open di dashboard, so as di data dey grow, di dashboard dey slow down and e fit eventually time out. Di documented fix na to turn off browser triggered archiving for di general settings and run di archiver from cron instead, as di user wey own di Matomo files, from inside di Matomo directory.

php console core:archive --url=https://analytics.example.com

Matomo also dey keep raw log tables side-by-side wit im processed report tables, and e fit delete old raw data and old reports base on schedule. Turn dat one on wen you install, no wait until di disk full. Matomo fit import server access logs too, wey make am di only product for here wey cover both families at di same time.

Rybbit and di newer stacks

git clone https://github.com/rybbit-io/rybbit.git
cd rybbit
chmod +x *.sh
./setup.sh your.domain.name

Rybbit na recent project wey get modern dashboard. The setup script dey write the environment file and start the stack with Docker Compose. E dey run ClickHouse, and e ship Caddy as im own web server. Caddy go take port 443 and request certificate for the domain wey you pass give am. If nginx already dey use 443 for the server, the script no go fit bind to the port. Use the project manual Compose method instead, then put am behind your existing proxy. The docs talk say e need at least 2 GB of RAM. Dem test am on Ubuntu 24 LTS. For ARM, e need ARMv8.2-A or newer because of ClickHouse.

Make we talk the honest limitation for any young project: features dey land quickly, and breaking changes fit come too. Pin a tag, read the release notes before you pull, and back up the database first.

Disk growth: measure am for your own box

How disk dey grow depend on wetin the tool dey store for each event. GoatCounter dey combine hits into counters, so the file dey grow more with different pages and days than with raw volume. Umami and Matomo dey store rows for each event, and Matomo dey store processed report tables on top the raw ones. ClickHouse dey store events for columns and compress dem well well, na why Plausible fit handle volume wey go put pressure on row store.

This guide no publish any megabytes per million pageviews figure, because e no measure one for your traffic. Take the reading by yourself. Change the service and user names to match your own Compose file.

du -h goatcounter-data/db.sqlite3
docker compose exec db psql -U umami -d umami -c "SELECT pg_size_pretty(pg_database_size('umami'));"
docker compose exec plausible_events_db clickhouse-client -q "SELECT formatReadableSize(sum(bytes_on_disk)) FROM system.parts WHERE active"

Write down the number, wait one week, write am down again, then divide the difference by the pageviews wey dashboard report for that week. That figure na about your site and your bot filtering, so e get more value than any published average. Then set a retention limit while the number still small. Full disk fit bring down every service for the VPS, no be analytics alone. Na this be the strongest reason to keep the database volume for somewhere df -h go warn you about. This risk need more attention for box wey already dey hold something bulky, because self-hosted photo server go exhaust the disk long before any analytics database come near that point.

How e dey behave behind one reverse proxy for subdomain

Put the collector for one subdomain of the site wey e dey measure, like stats.example.com. Dis one go make the collector request be first party, so browser rules wey dey block third party requests no go touch am.

Bind the application to loopback when you publish the container port. Docker dey write im own firewall rules before ufw, so container wey you publish as -p 3000:3000 fit reach from internet even if ufw status talk say the port dey denied. Test am from another machine with curl http://SERVER_IP:3000 and you go see the dashboard. If you publish am as -p 127.0.0.1:3000:3000, the same test go give Connection refused, because na only the Docker host itself fit reach the port. Dis one still mean say every process and user for the box, no be only the proxy, and for Docker Engine releases wey old pass 28.0.0, hosts wey dey the same L2 network segment fit reach ports wey dem publish to localhost too, so make sure your engine dey current. The same habit dey do pass just to hide dashboard: na im be the core of running one onion service for the same box, where any service wey still dey answer for the public interface na im dey link the hidden address back to your IP. The collector endpoint must remain reachable from the open internet, but the dashboard no need, and if you prefer to read am over one private network instead of publishing a second subdomain, advertising the VPS network to your tailnet with one subnet router go give you access without opening any port.

server {
    listen 443 ssl;
    server_name stats.example.com;

    location / {
        proxy_pass http://127.0.0.1:3000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

The forwarding headers no be optional for here. Without dem, every visit go arrive from 127.0.0.1, so the country report go empty and unique visitors go collapse enter one. Umami, for example, dey check X-Real-IP before X-Forwarded-For and e dey use the first one wey get value, so with the block wey dey up, e go read X-Real-IP. Each project dey decide which header e go trust and under which setting, so check the proxy documentation once instead of to assume. Caddy dey set those headers by itself, and one Caddyfile for the same job na just two lines.

stats.example.com {
    reverse_proxy 127.0.0.1:3000
}

If you never choose proxy yet, the comparison of nginx, Caddy and Traefik go show you which one fit one box wey get few subdomains.

Self-hosting change who dey hold the data. E no change wetin law talk about the data. Keep these two rules separate. The ePrivacy consent rule concern storing or reading anything for visitor device, so tool wey no set cookie and no write anything to local storage dey outside that specific requirement. GDPR concern processing personal data, and IP address count as personal data, so you still need lawful basis, retention limit, and answer when person ask wetin you dey hold about dem.

Plausible, Umami, GoatCounter and Medama no set cookie by default. Wetin each one derive instead dey differ between projects and fit change between versions, so read the project own privacy documentation instead of summary. Matomo ship IP anonymisation and opt-out endpoint wey you enable for admin interface.

Regulators fit reach different conclusions for different countries. France CNIL, for example, publish conditions wey audience measurement fit meet to get exemption from consent. This section na factual summary, no be legal advice. For real site wey get real users, ask lawyer for your jurisdiction.

One thing wey people dey miss: access log na personal data too. GoAccess no add script to the page, but e still process IP addresses, so log-based analytics no automatically dey outside the rules. Moving service go your own box relocate the exposure instead of removing am. Na the same reason wetin self-hosted SearXNG instance really hide stop for search engines, while the queries themselves still land for your own logs.

Ad blockers, and why your numbers go down

Filter lists dey match hostname and URL pattern. Hosted analytics product easy to match because everybody dey load am from the same known hostname. If you move the collector go your own subdomain, that hostname no go dey inside the request again. If you serve the script from path wey you choose, the known filename no go dey there again. Both changes the things wey list need match.

This post no dey claim any hit rate because e no measure one. The number of visitors wey block any particular setup depend on your audience. Developer audience dey block much more than general audience. Measure your own gap instead. For the same week, use GoAccess count requests for HTML pages inside the access log. Compare the result with the pageviews wey your script-based tool reports. The difference na blocked visits plus pages wey cache serve for your site.

Expect the totals to change on the day wey you switch from hosted product. Also expect say part of the change no get anything to do with blocking. Products no dey agree on wetin pageview mean, whether route change inside one single-page application count as one, and when session end. Compare trends across weeks before you conclude say traffic don drop.

Which one fit which site

  • Personal site or blog wey get under roughly 50,000 pageviews per month: GoatCounter or Medama, for one 1 GB VPS, with backups wey be just file copy.
  • Site wey you no fit add script, or audience wey dey block tracking well-well: GoAccess over the existing log, on a schedule.
  • Small business site wey another person go dey read the dashboard: Umami, with im Postgres container.
  • Site wey you want goal tracking, for one box wey get 2 GB of RAM or more: Plausible Community Edition, wey dey leave marketing funnels and user journeys for Plausible paid cloud, or Rybbit if you want the newer dashboard and you accept say the project still young.
  • Plenty sites, plenty user accounts, or requirement to keep raw data under your own retention policy: Matomo, wey you go size according to the published guidance wey dey above.

Start with the smallest tool wey answer your correct question. To move from GoatCounter go Plausible later go cost you one subdomain and some history. To move from Matomo go any other thing go cost you one migration wey you no go enjoy. If you still dey decide wetin else fit stay for the same box, the wider self-hosting roundup cover wetin fit stay near am, and if wetin you really want na request level tracing of one application instead of visitor counts, a self-hosted observability service na the tool for that work.

FAQ

No, the two mata no be the same. The consent rule wey dey under ePrivacy dey cover how you take store or read something for visitor device, so if your tool no dey set cookie and e no dey write anything for local storage, that one no concern that particular rule. GDPR na different rule wey dey cover how you take process personal data, and IP address na personal data, so you still need lawful basis and retention limit even if you no use cookie. Self-hosting just move the data go your own server and make you the person wey dey responsible for am. Check wetin your local regulator talk and ask lawyer for your own case.

How much RAM self-hosted analytics dey need for VPS?

Na the datastore dey decide, no be the dashboard. GoatCounter and Medama dey run as one process over local database files, one for GoatCounter and two for Medama, and Medama documentation talk say small sites fit run for machine wey get 256 MB. Umami dey add Postgres container join Node application. Plausible Community Edition and Rybbit both dey run ClickHouse, and both project talk say you need at least 2 GB. Matomo own guidance talk say you need 2 CPU cores and 2 GB of RAM for up to 100,000 pageviews every month.

Why my self-hosted numbers dey lower pass the analytics I replace?

Two reasons dey, and both of dem dey real. Filter lists dey block some collector requests, so every script-based tool go lose those visits. The products sef dey count differently, because wetin be pageview and when session go end dey vary between dem. Compare one week of HTML page requests from your access log against the same week of script-based pageviews. That gap na blocked visits plus cached pages, wey you measure for your own site instead of wetin you borrow from person wey publish im own rate.

I fit run Plausible or Rybbit for ARM VPS?

Both of dem dey run ClickHouse, and ClickHouse need SSE 4.2 for x86 or NEON for ARM. Plausible requirements talk say exactly that, and Rybbit docs talk say ARM systems need ARMv8.2-A or newer. Current ARM server cores fit do this, but the old ones no fit, and the failure go show as ClickHouse wey refuse to start with instruction set error instead of anything for application log. For small ARM box, the single-file tools no get this problem, because none of dem dey run ClickHouse.

I suppose parse server logs instead of using tracking script?

Use log parsing if you no fit add script, if your audience dey block things too much, or if you want count wey include crawlers. GoAccess dey read log wey your server already dey write, so e no dey add page weight and e no dey use database. You go lose everything wey dey happen inside browser, and you go miss any page wey CDN or browser cache serve, because that request no reach your server. Plenty sites dey run both and dem dey treat dem as two different measurements.

Dis article help you?