Skip to main content
Plausible is open-source, privacy-friendly web analytics — a lightweight, cookie-free alternative to Google Analytics. The template uses Plausible Community Edition; features may differ from Plausible’s hosted service. You manage it from its web UI at your *.suji.fr address and embed a small script on the sites you track. This guide covers configuring Plausible on Suji. Check the version and release notes shown in the marketplace before installing or upgrading. Plausible is maintained upstream; Suji provides the marketplace packaging.

​
Before you install

Plausible needs one thing you generate yourself: a secret key of at least 64 characters. Create one with:
Keep it handy for the install form. The template bundles PostgreSQL and ClickHouse. You still manage their data, backups, disk usage and upgrades as part of this install.
Create your account after install and review the self-hosted registration settings before sharing the URL.

​
Install

Dashboard → Apps → Plausible → Install: Recommended VM size: Medium or larger — Plausible bundles its own PostgreSQL and ClickHouse, so it’s heavier than a single-container app. See Recommended size. Click Deploy. First boot runs database migrations, so it takes a little longer than a single-container app. When it’s running, it’s live at https://plausible-<random>.suji.fr over HTTPS through the tunnel.

​
First connection — create your account

  1. Open the install URL (https://plausible-<random>.suji.fr).
  2. You’re redirected to /register — create your account (email + password).
  3. Add your first site (the domain you want to track) and copy the tracking snippet.
  4. Paste the snippet into that site’s <head>. Stats start flowing in.
Review registration and access settings before sharing the public URL. See Plausible Community Edition’s self-hosting instructions for controlling new account registration.

​
Email & reports

Plausible sends email for account invites, password resets, and scheduled email reports — but no mail provider is configured by default, so those won’t send until you add SMTP. Use your mail provider’s documented SMTP settings and test delivery; port 587 with STARTTLS is a common option. Add the SMTP env vars to the install yourself in the install’s Variables tab, then click Apply changes to redeploy.

​
Using an external database

The default install includes PostgreSQL and ClickHouse. Connecting external databases requires a separately planned custom Compose deployment, compatible database versions and data migration. Changing a URL does not move existing data. Back up first; customized Compose installs do not use the standard Variables editing flow.

​
Day-to-day management

​
Troubleshooting

The app waits for its databases and runs initialization/migrations before serving. Migrations may also run during upgrades. Follow deployment progress and inspect all three services’ logs if startup fails.
The secret must be at least 64 characters. Regenerate with openssl rand -base64 64 and update the install.
Expected until you configure SMTP — see Email & reports above (check credentials, TLS settings and outbound connectivity).
Plausible isn’t reachable through the tunnel yet — usually still migrating/starting (wait ~30–60 s). If it persists, the Logs tab shows why the container isn’t up.

​
Where things live

Uninstalling deletes both volumes by default — that’s all your analytics history. Choose keep data during uninstall to preserve it.
  • The template declares 3 GiB minimum and 4 GiB recommended memory. Its container limits are 1 GiB for Plausible, 512 MiB for PostgreSQL and 1 GiB for ClickHouse. Medium (8 GB) provides additional host headroom; traffic and retained history determine actual needs.
  • Memory/disk grow with traffic volume and history retention.
  • If you run other apps on the same VM, factor in that the VM’s total CPU/memory is shared — Plausible is one of the heavier marketplace apps.

​
Reporting issues