Plausible
Privacy-friendly web analytics - cookie-free, no consent banner, your visitor data on your own box.
One-click deploy, from $25/mo on a Miget plan.
Plausible is privacy-friendly web analytics: a clean, single-page dashboard that tells you what you need to know without cookies, without collecting personal data, and without a consent banner. The tracking script is roughly 75x smaller than Google Analytics. This is the self-hosted Community Edition.
It is a real analytics stack: the app and a managed Postgres for accounts and settings, plus a ClickHouse sidecar that stores the event data. Miget has no managed ClickHouse, so it runs as a private sidecar - a thin wrapper bakes the four tuning configs from Plausible’s official setup (ClickHouse otherwise assumes a 16 GB box) and another bakes the database migration step Plausible does not run on its own.
You already have lighter analytics in this catalogue with umami; Plausible adds funnels, goals, custom events, and a more polished dashboard for when a project needs them - all with the visitor data sitting on infrastructure you own.
Upstream project: Plausible Community Edition
#what you get
- Cookie-free, no consent banner needed, GDPR-friendly
- Tiny tracking script (~75x smaller than GA)
- Goals, funnels, custom events, and UTM tracking
- Managed Postgres + a private ClickHouse sidecar
- First registration becomes owner; later signups invite-only
- AGPL-3.0; your visitor data on your own infrastructure
#topology
| Service | Role | Public |
|---|---|---|
| plausible | analytics app (:5000) | yes |
| clickhouse | event store (private sidecar) | no |
| db | managed Postgres (accounts/settings) | no |
#miget sizing
// this stack needs
4 GiB RAM · 25 GB disk · 3 services
Budget ~3 GB usable: the app ~1 GB, ClickHouse ~2 GB (the baked low-resources config keeps it honest). Events live in ClickHouse on its own volume; app data in managed Postgres.
Hobby - recommended fit
$25/mo
2 vCPU · 4 GiB · 80 GiB disk
Headroom for your own apps: 8 GiB at $49/mo
Professional - production
$43/mo
2 vCPU · 4 GiB · 25 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 |
|---|---|---|---|
| Plausible on Miget ★ | 4 GiB plan | $25 | this whole stack, flat - no usage meters, and room left for your own apps |
| Fathom | Starter | ~$15 | $15/mo (100k pageviews) |
| Plausible Cloud | Growth | ~$9 | from $9/mo, metered by pageviews |
Self-hosted Plausible is one flat plan regardless of traffic, with visitor data on your own infrastructure.
#vs. other PaaS
Estimated monthly cost of running this exact stack (4 GiB RAM, 25 GB disk, 3 containers) elsewhere, from published June 2026 rates.
| Platform | Est. monthly | Notes |
|---|---|---|
| Miget ★ | $25 flat | compose stacks first-class: one deploy, dedicated vCPU, managed Postgres/Valkey, volumes and TLS all included in the plan |
| Heroku | ~$200 | no volumes; nothing between 1 GB ($50) and 2.5 GB ($250) dynos - 2 GB containers cost far more than shown |
| Render | ~$56 | per-service instances (0.5 GB $7, 2 GB $25) - every container is its own paid service |
| DO App Platform | ~$53 | no persistent volumes - stateful containers need managed DBs/Spaces (base $5 Spaces included here) |
| Railway | ~$44 | usage-based ($10/GB RAM-mo); vCPU billed separately at $20/vCPU-mo on top |
| Fly.io | ~$27 | 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
plausible -
Set the required variables:
SECRET_KEY_BASE, >= 64 bytes (openssl rand -base64 48), stable across deploysBASE_URL, the https domain, matched exactly (WebSocket/login)
- 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/plausible
docker compose up -dSame files, same behavior. The template README covers connection strings and scaling notes.
#faq
How is this different from the umami template?
Both are privacy-friendly analytics. Umami is lighter (a single app on Postgres); Plausible adds funnels, goals, and a more polished dashboard at the cost of a ClickHouse sidecar. Pick umami for minimal, Plausible for more depth.
Why does it need ClickHouse?
Plausible stores pageview events in ClickHouse, a columnar database built for fast analytics queries. Miget has no managed ClickHouse, so this template runs it as a private sidecar with a durable volume and the official low-resource tuning baked in.
What does it cost compared to Plausible Cloud?
Plausible Cloud starts at $9/month metered by pageviews. Self-hosted is one flat plan regardless of traffic, with the visitor data on your own infrastructure - the trade is that you run the ClickHouse sidecar yourself.
Ship Plausible today
One compose stack, 4 GiB of RAM, from $25/month flat, and it runs on your laptop with the same files.