community-edition: five files, and the compose file sets the database password to postgres
Example Docker Compose setup for hosting Plausible Community Edition
At a glance
- What is it?
- A getting started guide for self-hosting Plausible, delivered as a Docker Compose file, four ClickHouse configuration files and a readme. The database password is written into the compose file as a literal word, the branch is named after a version rather than main, and the recommended two gigabytes of memory sits oddly beside configuration files written for machines under sixteen.
- Who is it for?
- This is the shortest path to a self-hosted Plausible instance if you already run containers and want a starting point rather than a maintained distribution. Two things to do before you expose it.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Activity is slowing. The repository last received commits 6 months ago.
- What is it written in?
- GitHub does not report a main language for this repository.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- plausible/community-edition2,956 ★ · +75
| Repository | 2026-10-04 | 2026-11-15 |
|---|---|---|
| plausible/community-edition | 2.9k | 3k |
75 Stars in the last 42 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The compose file writes the database password as a literal word
The database service in the compose file sets its environment in the file itself:
environment:
- POSTGRES_PASSWORD=postgresThere is no environment variable reference, no substitution and no note about changing it. The password for the analytics database is the word postgres, and it is the same word the health check uses as the user. Everything else about that service is careful: the image is a pinned major on alpine, the restart policy is always, the data directory is a named volume, and there is a readiness check with a one minute start period. The value that matters for anyone exposing the instance is the one written as a plain literal, and the readme's configuration steps cover the application URL and the secret key base without mentioning it.
Two gigabytes is the recommendation and the shipped configs target sixteen
The prerequisites ask for Docker and Docker Compose, a CPU with a fairly old instruction set extension or its newer equivalent, which the readme attributes to ClickHouse rather than to Plausible, and at least two gigabytes of memory, phrased as what is needed to run ClickHouse and Plausible without running out. Meanwhile the compose file mounts four configuration files into the ClickHouse container, two of which are explicitly about saving resources, and the comment beside them cites ClickHouse's own guidance on running in less than sixteen gigabytes of memory. So the document recommends a floor two gigabytes above the low end, and the configuration it ships is written for a ceiling well below that guidance's upper end. Neither number is wrong on its own; the gap between them is what a reader sizing a small instance has to reason about.
The default branch is a version number and the logo points at an older one
The default branch of this repository is not main or master. It is named after the version the getting started guide installs. The guide reinforces that by pinning the clone to the same branch and taking only that one:
$ git clone -b v3.2.1 --single-branch https://github.com/plausible/community-edition plausible-ceSo there is no moving development branch for this repository to track, which is a defensible choice for a versioned deployment recipe. The header of the same file is less consistent. The logo is loaded from raw image paths on a branch named after a different, earlier version than the one the guide installs, in both its light and dark variants. The repository has no releases of its own, so a reader has three version numbers in the first screen of the file: the branch they land on, the version in the clone command, and the older one in the image addresses.
The application image is pinned exactly while the databases float
Three container images are named in the compose file and they are pinned three different ways. The application image is pinned to the full version, the same one as the branch. The relational database image is pinned to a major version on alpine, which means it tracks patch releases within that major but not the major itself. The analytical database image is pinned more tightly still, to a month-and-year release on alpine. So the component this repository exists to deploy is reproducible and the two databases underneath it are not. That is a reasonable split, since a stale application image is the failure people notice, and it is still worth knowing that two of the three services will change under a deployment that was pinned on purpose.
ClickHouse is forced onto IPv4 and the file names the warning it removes
One of the four mounted configuration files exists to solve one problem, and the comment says which. Because Docker does not enable IPv6 in bridge networks by default, ClickHouse is made to bind to IPv4 only, and the warning that produces otherwise is quoted in the file: a listen attempt on the IPv6 wildcard address failing because the address family for the hostname is not supported. The other three files cover logging, resource reduction and the matching user profile overrides for that reduction, all mounted read only. The service also raises the open file limit to a quarter of a million in both the soft and hard sense, skips its own user setup because the compose file is meant to be authoritative about that, and checks readiness by fetching a local ping endpoint over HTTP.
Release announcements are announced in a different repository
This repository has no releases. The readme's contact section sends release announcements to the releases page of the main analytics repository instead, and questions to a self-hosted support category in that repository's discussions. So the deployment recipe lives here, the history of what changed lives there, and the wiki that covers installation, upgrades, configuration and integrations is attached to this repository. That split is a deliberate consequence of separating a versioned deployment recipe from the product's own development, and it does mean that a reader who wants to know what changed between two versions of this recipe has to look in a repository that does not contain it.
Exposing the instance is a documented compose override, not a compose edit
The application service is not published to the host by default, and the guide handles that with a separate override file rather than by telling you to edit the tracked compose file. It sets two port values in the environment file, then writes an override through a heredoc:
services:
plausible:
ports:
- 80:80
- 443:443Setting those two values to the standard ports is what triggers automatic certificate issuance, which in turn requires the domain to already have a DNS entry pointing at the server. The guide also explains the alternative, running behind a reverse proxy on different values, and gives a worked local case where the application is reached on a loopback port and the override maps that port to the container's port. The secret key base is generated with a command that produces forty eight bytes of base64 output, while the requirement beside it is stated in terms of a sixty four byte string.
Editorial conclusion
This is the shortest path to a self-hosted Plausible instance if you already run containers and want a starting point rather than a maintained distribution. Two things to do before you expose it. Change the database password, because the compose file writes one into the configuration and the readme does not tell you to replace it. And register the domain in DNS first, because automatic certificate issuance depends on the domain already resolving. Read the ClickHouse configuration files as a starting point rather than a tuned one, since they are described as saving resources on small machines.
Frequently asked questions
What is plausible/community-edition?
It is a getting started guide to self-hosting Plausible, delivered as a Docker Compose setup. The repository holds a compose file, a clickhouse directory of configuration files, a readme, a licence and a gitignore, and its default branch is named after the version it installs.
How do I install Plausible Community Edition?
Clone the repository on the branch matching the version you want, create an environment file holding the base URL and a secret key base, optionally write a compose override to publish the ports, then bring the services up with Docker Compose. After that, visit the instance at your base URL and create the first user.
What does the compose file set the Postgres password to?
The literal word postgres, written into the compose file's environment block for the database service with no variable reference. The same file uses that word as the user in its readiness check.
How much memory does Plausible Community Edition need?
The prerequisites recommend at least two gigabytes so that ClickHouse and Plausible run without running out of memory. The compose file separately mounts ClickHouse configuration files that are described as reducing resource use, with a comment citing ClickHouse's guidance for machines with less than sixteen gigabytes.
Does Plausible Community Edition get TLS certificates automatically?
Yes, when the two port variables are set to the standard HTTP and HTTPS ports and the domain already has a DNS entry pointing at the server. The guide also covers running behind a reverse proxy on different port values, and a local evaluation case using a loopback address.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/plausible-community-edition)Star history chart for your README
[](https://hysenlabs.com/projects/plausible-community-edition)Was this useful?