Skip to main content
OSSAlt

How to Self-Host Umami: Simple Web Analytics 2026

·OSSAlt Team
umamianalyticsprivacyself-hostingdockergoogle-analytics2026
Share:

TL;DR

Umami (MIT, ~21K GitHub stars, Next.js/TypeScript) is a simple, lightweight self-hosted web analytics tool. It's faster and simpler than Plausible, with a clean real-time dashboard, custom event tracking, and multi-site support. No cookies, no personal data, GDPR-compliant out of the box. The tracking script is under 2KB. Google Analytics is free but tracks users extensively; Umami gives you traffic insights without surveillance.

Key Takeaways

  • Umami: MIT, ~21K stars, Next.js — simple analytics, no cookies, real-time dashboard
  • Multi-site: Track unlimited websites from a single Umami instance
  • Teams: Share analytics access with team members per site
  • Custom events: Track clicks, form submissions, any user interaction
  • vs Plausible: Umami is simpler and lighter; Plausible has more features (funnels, revenue)
  • Share URL: Public dashboard URLs for client reporting

Part 1: Docker Setup

# docker-compose.yml
services:
  umami:
    image: ghcr.io/umami-software/umami:postgresql-latest
    container_name: umami
    restart: unless-stopped
    ports:
      - "3000:3000"
    environment:
      DATABASE_URL: "postgresql://umami:${POSTGRES_PASSWORD}@db:5432/umami"
      DATABASE_TYPE: postgresql
      APP_SECRET: "${APP_SECRET}"
    depends_on:
      db:
        condition: service_healthy

  db:
    image: postgres:15-alpine
    restart: unless-stopped
    environment:
      POSTGRES_DB: umami
      POSTGRES_USER: umami
      POSTGRES_PASSWORD: "${POSTGRES_PASSWORD}"
    volumes:
      - db_data:/var/lib/postgresql/data
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U umami"]
      interval: 5s
      start_period: 20s

volumes:
  db_data:

# .env
POSTGRES_PASSWORD=your-db-password
APP_SECRET=$(openssl rand -hex 32)

docker compose up -d

Visit http://your-server:3000 → log in with admin / umami → change password immediately.

Part 2: HTTPS with Caddy

stats.yourdomain.com {
    reverse_proxy localhost:3000
}

Part 3: Add a Website

  1. Settings → Websites → + Add website
  2. Name: My Blog
  3. Domain: yourdomain.com
  4. Copy the tracking script
<!-- Add to your site's <head>: -->
<script async src="https://stats.yourdomain.com/script.js"
  data-website-id="YOUR-WEBSITE-UUID">
</script>

Part 4: Install Tracking Script

Static HTML

<head>
  <script async src="https://stats.yourdomain.com/script.js"
    data-website-id="YOUR-UUID">
  </script>
</head>

Next.js

npm install @umami/analytics

// app/layout.tsx:
import Script from 'next/script'

export default function RootLayout({ children }) {
  return (
    <html>
      <head>
        <Script
          src="https://stats.yourdomain.com/script.js"
          data-website-id="YOUR-UUID"
          strategy="afterInteractive"
        />
      </head>
      <body>{children}</body>
    </html>
  )
}

WordPress

Plugin: Insert Headers and Footers
Header section: paste script tag

Or use the official Umami WordPress plugin.

Ghost

Admin → Settings → Code injection → Site header:
<script async src="https://stats.yourdomain.com/script.js" data-website-id="UUID"></script>

Part 5: Custom Events

Track user interactions beyond page views:

// Track a button click:
document.getElementById('signup-btn').addEventListener('click', function() {
  umami.track('signup-click', { plan: 'pro' })
})

// Track form submission:
document.getElementById('contact-form').addEventListener('submit', function() {
  umami.track('form-submit', { form: 'contact' })
})

// Track with properties:
umami.track('purchase', {
  amount: 49.99,
  product: 'Pro Plan',
  currency: 'USD'
})

HTML data attributes (no JavaScript needed)

<!-- Automatically track this button click: -->
<button data-umami-event="CTA Click" data-umami-event-location="hero">
  Get Started
</button>

<!-- Track link clicks: -->
<a href="/pricing" data-umami-event="Pricing Link">View Pricing</a>

Part 6: Multi-Site Management

Add multiple sites

Settings → Websites:
├── yourdomain.com (Website 1)
├── blog.yourdomain.com (Website 2)
├── client-a.com (Website 3)
└── client-b.com (Website 4)

Each site gets its own unique tracking script with a different data-website-id.

Teams

  1. Settings → Teams → + Create team
  2. Add members: client@example.com → Viewer access
  3. Share only the sites you want them to see
  1. Website → Edit → Enable share URL
  2. Share the read-only link with clients: https://stats.yourdomain.com/share/TOKEN/site-name

Part 7: Dashboard Overview

The Umami dashboard shows:

Overview:
├── Visitors (unique)
├── Views (total page views)
├── Sessions
├── Bounce rate
└── Average session duration

Sources:
├── Referrers
├── Browsers
├── Operating systems
└── Devices (desktop/mobile/tablet)

Pages:
├── Most visited pages
└── Entry/exit pages

Location:
├── Countries
├── Regions
└── Cities (if enabled)

Events:
└── Custom event counts and properties

Part 8: API

API_KEY="your-api-key"  # Settings → API Keys
BASE="https://stats.yourdomain.com/api"
WEBSITE_ID="your-website-uuid"

# Get website stats:
curl "$BASE/websites/$WEBSITE_ID/stats?startAt=1704067200000&endAt=$(date +%s)000" \
  -H "x-umami-api-key: $API_KEY" | jq '.pageviews'

# Get top pages:
curl "$BASE/websites/$WEBSITE_ID/metrics?startAt=1704067200000&endAt=$(date +%s)000&type=url" \
  -H "x-umami-api-key: $API_KEY" | jq '.[0:10]'

# Get active visitors right now:
curl "$BASE/websites/$WEBSITE_ID/active" \
  -H "x-umami-api-key: $API_KEY"

# Send a custom event via API (server-side tracking):
curl -X POST "$BASE/send" \
  -H "Content-Type: application/json" \
  -d '{
    "payload": {
      "website": "YOUR-WEBSITE-UUID",
      "url": "/api/checkout",
      "name": "Purchase",
      "data": {"amount": 49.99, "plan": "pro"}
    },
    "type": "event"
  }'

Maintenance

# Update:
docker compose pull
docker compose up -d

# Backup:
docker exec umami-db-1 pg_dump -U umami umami \
  | gzip > umami-db-$(date +%Y%m%d).sql.gz

# Logs:
docker compose logs -f umami

Why Self-Host Umami?

The case for self-hosting Umami comes down to three practical factors: data ownership, cost at scale, and operational control.

Data ownership is the fundamental argument. When you use a SaaS version of any tool, your data lives on someone else's infrastructure subject to their terms of service, their security practices, and their business continuity. If the vendor raises prices, gets acquired, changes API limits, or shuts down, you're left scrambling. Self-hosting Umami means your data and configuration stay on infrastructure you control — whether that's a VPS, a bare metal server, or a home lab.

Cost at scale matters once you move beyond individual use. Most SaaS equivalents charge per user or per data volume. A self-hosted instance on a $10-20/month VPS typically costs less than per-user SaaS pricing for teams of five or more — and the cost doesn't scale linearly with usage. One well-configured server handles dozens of users for a flat monthly fee.

Operational control is the third factor. The Docker Compose configuration above exposes every setting that commercial equivalents often hide behind enterprise plans: custom networking, environment variables, storage backends, and authentication integrations. You decide when to update, how to configure backups, and what access controls to apply.

The honest tradeoff: you're responsible for updates, backups, and availability. For teams running any production workloads, this is familiar territory. For individuals, the learning curve is real but the tooling (Docker, Caddy, automated backups) is well-documented and widely supported.

Server Requirements and Sizing

Before deploying Umami, assess your server capacity against expected workload.

Minimum viable setup: A 1 vCPU, 1GB RAM VPS with 20GB SSD is sufficient for personal use or small teams. Most consumer VPS providers — Hetzner, DigitalOcean, Linode, Vultr — offer machines in this range for $5-10/month. Hetzner offers excellent price-to-performance for European and US regions.

Recommended production setup: 2 vCPUs with 4GB RAM and 40GB SSD handles most medium deployments without resource contention. This gives Umami headroom for background tasks, caching, and concurrent users while leaving capacity for other services on the same host.

Storage planning: The Docker volumes in this docker-compose.yml store all persistent Umami data. Estimate your storage growth rate early — for data-intensive tools, budget for 3-5x your initial estimate. Hetzner Cloud and Vultr both support online volume resizing without stopping your instance.

Operating system: Any modern 64-bit Linux distribution works. Ubuntu 22.04 LTS and Debian 12 are the most commonly tested configurations. Ensure Docker Engine 24.0+ and Docker Compose v2 are installed — verify with docker --version and docker compose version. Avoid Docker Desktop on production Linux servers; it adds virtualization overhead and behaves differently from Docker Engine in ways that cause subtle networking issues.

Network: Only ports 80 and 443 need to be publicly accessible when running behind a reverse proxy. Internal service ports should be bound to localhost only. A minimal UFW firewall that blocks all inbound traffic except SSH, HTTP, and HTTPS is the single most effective security measure for a self-hosted server.

Backup and Disaster Recovery

Running Umami without a tested backup strategy is an unacceptable availability risk. Docker volumes are not automatically backed up — if you delete a volume or the host fails, data is gone with no recovery path.

What to back up: The named Docker volumes containing Umami's data (database files, user uploads, application state), your docker-compose.yml and any customized configuration files, and .env files containing secrets.

Backup approach: For simple setups, stop the container, archive the volume contents, then restart. For production environments where stopping causes disruption, use filesystem snapshots or database dump commands (PostgreSQL pg_dump, SQLite .backup, MySQL mysqldump) that produce consistent backups without downtime.

For a complete automated backup workflow that ships snapshots to S3-compatible object storage, see the Restic + Rclone backup guide. Restic handles deduplication and encryption; Rclone handles multi-destination uploads. The same setup works for any Docker volume.

Backup cadence: Daily backups to remote storage are a reasonable baseline for actively used tools. Use a 30-day retention window minimum — long enough to recover from mistakes discovered weeks later. For critical data, extend to 90 days and use a secondary destination.

Restore testing: A backup that has never been restored is a backup you cannot trust. Once a month, restore your Umami backup to a separate Docker Compose stack on different ports and verify the data is intact. This catches silent backup failures, script errors, and volume permission issues before they matter in a real recovery.

Security Hardening

Self-hosting means you are responsible for Umami's security posture. The Docker Compose setup provides a functional base; production deployments need additional hardening.

Always use a reverse proxy: Never expose Umami's internal port directly to the internet. The docker-compose.yml binds to localhost; Caddy or Nginx provides HTTPS termination. Direct HTTP access transmits credentials in plaintext. A reverse proxy also centralizes TLS management, rate limiting, and access logging.

Strong credentials: Change default passwords immediately after first login. For secrets in docker-compose environment variables, generate random values with openssl rand -base64 32 rather than reusing existing passwords.

Firewall configuration:

ufw default deny incoming
ufw allow 22/tcp
ufw allow 80/tcp
ufw allow 443/tcp
ufw enable

Internal service ports (databases, admin panels, internal APIs) should only be reachable from localhost or the Docker network, never directly from the internet.

Network isolation: Docker Compose named networks keep Umami's services isolated from other containers on the same host. Database containers should not share networks with containers that don't need direct database access.

VPN access for sensitive services: For internal-only tools, restricting access to a VPN adds a strong second layer. Headscale is an open source Tailscale control server that puts your self-hosted stack behind a WireGuard mesh, eliminating public internet exposure for internal tools.

Update discipline: Subscribe to Umami's GitHub releases page to receive security advisory notifications. Schedule a monthly maintenance window to pull updated images. Running outdated container images is the most common cause of self-hosted service compromises.

Troubleshooting Common Issues

Container exits immediately or won't start

Check logs first — they almost always explain the failure:

docker compose logs -f umami

Common causes: a missing required environment variable, a port already in use, or a volume permission error. Port conflicts appear as bind: address already in use. Find the conflicting process with ss -tlpn | grep PORT and either stop it or change Umami's port mapping in docker-compose.yml.

Cannot reach the web interface

Work through this checklist:

  1. Confirm the container is running: docker compose ps
  2. Test locally on the server: curl -I http://localhost:PORT
  3. If local access works but external doesn't, check your firewall: ufw status
  4. If using a reverse proxy, verify it's running and the config is valid: caddy validate --config /etc/caddy/Caddyfile

Permission errors on volume mounts

Some containers run as a non-root user. If the Docker volume is owned by root, the container process cannot write to it. Find the volume's host path with docker volume inspect VOLUME_NAME, check the tool's documentation for its expected UID, and apply correct ownership:

chown -R 1000:1000 /var/lib/docker/volumes/your_volume/_data

High resource usage over time

Memory or CPU growing continuously usually indicates unconfigured log rotation, an unbound cache, or accumulated data needing pruning. Check current usage with docker stats umami. Add resource limits in docker-compose.yml to prevent one container from starving others. For ongoing visibility into resource trends, deploy Prometheus + Grafana or Netdata.

Data disappears after container restart

Data stored in the container's writable layer — rather than a named volume — is lost when the container is removed or recreated. This happens when the volume mount path in docker-compose.yml doesn't match where the application writes data. Verify mount paths against the tool's documentation and correct the mapping. Named volumes persist across container removal; only docker compose down -v deletes them.

Keeping Umami Updated

Umami follows a regular release cadence. Staying current matters for security patches and compatibility. The update process with Docker Compose is straightforward:

docker compose pull          # Download updated images
docker compose up -d         # Restart with new images
docker image prune -f        # Remove old image layers (optional)

Read the changelog before major version updates. Some releases include database migrations or breaking configuration changes. For major version bumps, test in a staging environment first — run a copy of the service on different ports with the same volume data to validate the migration before touching production.

Version pinning: For stability, pin to a specific image tag in docker-compose.yml instead of latest. Update deliberately after reviewing the changelog. This trades automatic patch delivery for predictable behavior — the right call for business-critical services.

Post-update verification: After updating, confirm Umami is functioning correctly. Most services expose a /health endpoint that returns HTTP 200 — curl it from the server or monitor it with your uptime tool.

Frequently Asked Questions

How much does it cost to self-host Umami?

The primary cost is your server. A Hetzner CAX11 (2 vCPU ARM, 4GB RAM) runs about $5/month — enough for Umami plus a few companion services. Add a domain ($12/year) and you're under $75/year for a complete self-hosted deployment. Compare that to SaaS pricing that typically starts at $5-15/user/month.

Can I run Umami on a VPS with other services?

Yes. The docker-compose.yml above isolates Umami on its own named Docker network. As long as your server has sufficient RAM and disk — 4GB RAM and 20GB disk handles most combinations — running multiple self-hosted services on one VPS is both practical and common. Tools like Dozzle and Portainer make monitoring multi-container setups manageable.

How do I migrate data if I switch servers?

Stop the Umami container, export the Docker volumes (using docker run --rm -v VOLUME:/data -v $(pwd):/backup alpine tar czf /backup/backup.tar.gz /data), transfer to the new server, restore the volumes, and update your DNS. Most migrations complete in under an hour. Test the restoration on the new server before decommissioning the old one.

What happens if Umami releases a breaking update?

Pin your docker-compose.yml to a specific image tag (e.g., image: umami:1.2.3 instead of latest). Subscribe to the GitHub releases page for advance notice. When you're ready to upgrade, read the release notes, back up first, test on a staging instance, then update production.

Is Umami suitable for production use?

Yes, with the hardening described above: reverse proxy for HTTPS, firewall rules, regular backups, and a pinned image tag. Many teams run Umami in production successfully. The main requirement is treating your self-hosted instance with the same operational discipline you'd apply to any business-critical service.

See also: Plausible Analytics — more features; Matomo — enterprise-grade

See all open source analytics tools at OSSAlt.com/categories/analytics.

See open source alternatives to Umami on OSSAlt.

The SaaS-to-Self-Hosted Migration Guide (Free PDF)

Step-by-step: infrastructure setup, data migration, backups, and security for 15+ common SaaS replacements. Used by 300+ developers.

Join 300+ self-hosters. Unsubscribe in one click.