Before you start
- Register the first account as soon as the deployment is ready: it becomes the owner, and later users need an invitation.
- A stable HTTPS site host or custom domain; BASE_URL and every tracking snippet use it.
- No mailer is configured; add SMTP settings in Edit TOML before relying on invitations or password resets.
- Back up PostgreSQL and ClickHouse, bundled or existing; keep all secrets stable.
- An existing PostgreSQL or ClickHouse must already have its database created and be reachable from the application network; the role must be allowed to run Plausible's migrations.
Configuration that needs your attention
DATABASE_URL comes from a native postgres binding for bundled PostgreSQL; CLICKHOUSE_DATABASE_URL is assembled in the container from clickhouse-password for bundled ClickHouse. Existing databases take complete URL secrets. No password is stored in the preset.
Required secrets
Configure these scoped secrets during deployment review in your Hakopod installation. Secret values stay out of the application TOML.
-
clickhouse-password -
database-password -
secret-key-base
This preset needs a public site URL. Set the correct origin before starting the application.
Use this preset
- Open the Catalog in your own Hakopod dashboard and select Plausible Analytics.
- Choose the project, environment, and application name. Set the required values and secret references.
- Review the generated configuration, resource requests, networking, and storage plan.
- Deploy, then inspect readiness and logs. Configure backups for persistent data before relying on the service.
Read the upstream setup documentation ↗
View native TOML and setup notes ↗
Pinned container image
ghcr.io/plausible/community-edition:v3.2.1@sha256:33e60bfb40f2df5da00f8753b76fad04f67dba3abe6d73eb516e440e3fb62985
The catalog pins this image for reproducibility. Review upstream updates and compatibility before changing it.