Skip to main content
Upstream source: Current installation guide. Plausible Community Edition uses PostgreSQL for accounts and sites, ClickHouse for events, and its own application data directory. They share one Compose network. This example keeps both databases private; Towbar does not treat their Compose volumes as managed Datastores.

Towbar manifest

.towbar/services/plausible-ce.compose.yml

Compose project

deploy/plausible-ce/compose.yml

Configure

  1. Prepare the example server, connect the repository, and map production to the branch containing these files. Replace the example server IP and domain.
  2. Commit every file shown below under deploy/plausible-ce/. The Towbar manifest points to the Compose file; it does not create it for you.
  3. Sync the repository and inspect the resolved Compose project. Save the runtime values below if this example declares any.
  4. Give the server enough memory for ClickHouse as well as the application; the official low-memory configuration is a separate tuning step.
  5. Back up PostgreSQL, ClickHouse, and Plausible’s own data volume together. These Compose databases do not receive Towbar Datastore backup/restore operations.
  6. Deploy it manually and run the verification below before enabling auto-deploy.

Runtime values

Save these values on the Compose project after the repository sync. The manifest declares required keys, not their values.

Verify

Create an account and a site, install its tracking snippet on a test page, and confirm a visit appears. Then restart the project and verify historical visits remain. For field constraints, see Compose guide.
Last modified on September 27, 2026