Umami
Privacy-first web analytics - no cookies, no consent banner - on a managed Postgres, unlimited sites and events.
One-click deploy, from $13/mo on a Miget plan.
Google Analytics became a compliance question; the answer for most sites is privacy-first analytics: no cookies, no cross-site tracking, no consent banner needed, and a dashboard that shows what you actually check - visitors, referrers, pages, countries, events. Umami is the open-source standard of that category.
This template runs Umami v3 (PostgreSQL-only since v3) as one stateless container on a managed Postgres that Miget provisions and auto-wires. One secret (APP_SECRET), a default admin/umami login to change on first visit, and a ~2 KB script tag for your sites.
Hosted privacy analytics price per pageview tier and per site. Self-hosted Umami has neither meter: track every site you own, keep the data on your infrastructure, and let the database be the only thing that grows.
Upstream project: Umami
#what you get
- Cookie-free, GDPR/PECR-friendly - no consent banner required
- ~2 KB tracking script; realtime dashboard, UTM and event tracking
- Unlimited websites, team members, and events
- Stateless container on a managed Postgres - migrations run on start
- Public share URLs for dashboards
- API for custom reporting
#topology
| Service | Role | Public |
|---|---|---|
| umami | dashboard + collection API (:5000) | yes |
| db | Postgres - managed service on Miget, container locally | no |
#miget sizing
// this stack needs
1.5 GiB RAM · 5 GB disk · 2 services
512 MiB for the app is plenty; the managed Postgres carries the data. Millions of pageviews a month fit comfortably in this footprint.
Hobby - recommended fit
$13/mo
1 vCPU · 2 GiB · 50 GiB disk
Headroom for your own apps: 2 GiB at $19/mo
Professional - production
$22/mo
1 vCPU · 2 GiB · 10 GiB disk
Dedicated resources, production SLOs - plan details
One Miget plan is a fixed pool of compute - the whole stack (managed databases included) deploys inside it, and anything left over runs your other apps. No per-service or per-seat math.
#vs. the managed service
What the hosted equivalents charge, against the flat Miget plan this stack fits on. Prices as of June 2026, sources linked.
| Service | Plan | Monthly | What you get |
|---|---|---|---|
| Umami on Miget ★ | 2 GiB plan | $13 | this whole stack, flat - no usage meters, and room left for your own apps |
| Plausible | Starter | ~$9 | 1 site, 10k pageviews/mo, 3-year retention |
| Fathom | entry | ~$15 | 100k pageviews/mo across up to 50 sites |
| Umami Cloud | paid | ~$20 | 1M events/mo, then $0.02 per extra 1k events |
Self-hosted Umami has no site or event caps and keeps visitor data on your infrastructure - the entire point of privacy-first analytics.
#vs. other PaaS
Estimated monthly cost of running this exact stack (1.5 GiB RAM, 5 GB disk, 2 containers) elsewhere, from published June 2026 rates.
| Platform | Est. monthly | Notes |
|---|---|---|
| Miget ★ | $13 flat | compose stacks first-class: one deploy, dedicated vCPU, managed Postgres/Valkey, volumes and TLS all included in the plan |
| Heroku | ~$75 | no volumes; nothing between 1 GB ($50) and 2.5 GB ($250) dynos - 2 GB containers cost far more than shown |
| DO App Platform | ~$23 | no persistent volumes - stateful containers need managed DBs/Spaces (base $5 Spaces included here) |
| Render | ~$20 | per-service instances (0.5 GB $7, 2 GB $25) - every container is its own paid service |
| Railway | ~$16 | usage-based ($10/GB RAM-mo); vCPU billed separately at $20/vCPU-mo on top |
| Fly.io | ~$10 | cheapest sticker price - but burstable shared CPUs (1/16 core; dedicated vCPUs cost ~2-3×), no compose deploys (one app per container, manual wiring), managed DBs billed extra |
Estimates assume RAM fully allocated at published on-demand rates - and sticker price isn't the whole comparison: the cheaper rows buy burstable shared CPUs, per-service wiring instead of a compose deploy, and managed databases billed separately. Heroku and DO App Platform have no persistent volumes at all - stateful stacks like this one need workarounds there.
#deploy it
On Miget
- Create a Compose Stack in app.miget.com pointing at the templates repository
- Set the stack path to
umami -
Set the required variable:
APP_SECRET, signs auth tokens (openssl rand -hex 32)
- Deploy. Miget layers
compose.miget.yaml(RAM, privacy, volumes, managed services) automatically
Locally first?
Every template is portable, vanilla Docker Compose - the Miget overrides are ignored locally:
git clone https://github.com/deployable-sh/stacks
cd miget-compose-templates/umami
docker compose up -dSame files, same behavior. The template README covers connection strings and scaling notes.
#faq
How does self-hosted Umami compare to Plausible or Fathom pricing?
Plausible starts at $9/month for one site and 10k pageviews; Fathom at $15/month for 100k; Umami Cloud at $20/month for 1M events. This stack is $13/month flat with no site, pageview, or event caps - and the visitor data never leaves your infrastructure.
Do I still need a cookie consent banner?
Not for Umami itself - it sets no cookies and stores no personal identifiers, which is the design goal of privacy-first analytics. (Your other scripts may still need consent; Umami stops being the reason.)
How do I add a website?
Log in, add the site in the dashboard, and paste the generated script tag - https://your-domain/script.js with your website id - into your pages. Data appears in realtime; UTM parameters and custom events work out of the box.
Can it handle real traffic volumes?
Yes - the collection endpoint is a lightweight Next.js API writing to Postgres, and a 1 GiB managed instance absorbs millions of monthly pageviews. Past that, scale the database plan before the app.
Why is Umami v3 Postgres-only?
Upstream dropped MySQL in v3.0 to focus the schema and migrations on one engine. Convenient here: the managed Postgres is exactly what it wants, auto-provisioned and auto-wired.
Ship Umami today
One compose stack, 1.5 GiB of RAM, from $13/month flat, and it runs on your laptop with the same files.