Apps / Docker Images
Plausible CE in Docker.
Analytics without the cookies.
Plausible Community Edition is the privacy-first answer to Google Analytics: one lightweight script, cookieless by design, every metric on one page, and the data on your server instead of an ad company's.
docker pull ghcr.io/remarkablecloud/plausible Current build
3.2.1-r1
Updated Sep 12, 2026
Base
Plausible CE, digest-pinned
What's inside
Postgres + ClickHouse wired and migrated, generated owner, invite-only
Upstream license
Plausible Community Edition: AGPL-3.0.
Free to pull and run anywhere. Digest-pinned, updated deliberately; each build is recorded in the changelog.
The image
What our image adds.
Plausible Community Edition is the privacy-first answer to Google Analytics: one lightweight script, cookieless by design, every metric on one page, and the data on your server instead of an ad company's.
Both databases wired and migrated
Postgres and ClickHouse come up, get their schemas, and connect; the part of self-hosting Plausible that generates the most issues is done.
Generated owner, invite-only registration
The owner exists before the port opens, and nobody else can register without an invite.
Non-root runtime, digest-pinned base
Rebuilt and scanned on our cadence.
Proxy-aware BASE_URL
Script snippets, links and emails all follow your real domain.
Rather skip the compose file? Deploy Plausible CE with one click on your own VPS: TLS, domain and database already wired.
Deploy Plausible CE in one clickThe guide
Run it in production.
Architecture at a glance
Three containers: plausible (the app, port 8000 internal), postgres (16, metadata: sites, users, goals), clickhouse (24.12, the events). ClickHouse requires its password (CH_PASSWORD is mandatory, not a nicety). The events volume grows with traffic; metadata stays small.
Docker Compose walkthrough
Set DB_PASSWORD, CH_PASSWORD and SITE_URL, bring it up, read the generated owner credentials from the log, log in, add your first site, and paste the one-line script into your pages. Numbers appear within minutes.
Environment variable reference
| Variable | Purpose |
|---|---|
| DATABASE_URL | PostgreSQL connection (metadata) |
| CLICKHOUSE_DATABASE_URL | ClickHouse connection (events) |
| BASE_URL | Public https URL; drives the tracking script and links |
| CH_PASSWORD | ClickHouse password, required by the shipped ClickHouse version |
Hardening notes
Keep both databases on the internal network only; ClickHouse especially has no business with a published port. Registration stays invite-only. The tracking script is public by nature; the dashboard is what your proxy protects.
Backups
pg_dump for metadata and the ClickHouse volume for events. Metadata is tiny and precious (site configs, goals); events are the history. Losing events loses charts; losing metadata loses the install.
Upgrades
Pull the new tag, recreate, migrations run for both stores on boot. CE tracks upstream closely; ride our promoted tags.
Or skip the ops
Host Plausible CE on your own private VPS.
One click installs this exact image on a VPS that is yours alone, domain and TLS wizard included. The same server runs as many apps as fit, with no per-app charge.
FAQ
Questions we get.
Is this really equivalent to Google Analytics?
For the questions most sites actually ask (visitors, sources, pages, goals, campaigns), yes, on one page, without cookie banners. It deliberately does not do ad-tech level user tracking; that is the point.
GDPR and cookie banners?
Plausible is cookieless and stores no personal identifiers, which is exactly why teams switch to it. Your compliance posture is yours to confirm, but this is the tool built for it.
How heavy is it?
Light. The app idles small; ClickHouse wants RAM as events grow. A 2 GB server runs many small-to-mid sites comfortably.
Can I track more than one site?
Yes, add as many sites as you like from the dashboard; one install serves them all.
Your server runs. You sleep.
Fully managed hosting from people who have been doing this since 2001.