Deploy Plausible Analytics

Plausible is a privacy-focused web analytics platform with a compact dashboard and cookie-free event collection. Moltern deploys Plausible Community Edition with managed PostgreSQL and ClickHouse dependencies.

What Moltern deploys​

The Plausible runtime is stateless. Both databases use isolated paths in the team workspace and are provisioned before Plausible starts.

Deploy Plausible​

1. Open Services and choose Plausible.
2. Select the project and environment.
3. Enter a service name.
4. Review the three-workload install impact.
5. Choose Deploy service and wait until Plausible reports Running.

Create an account and site​

Open the generated URL:

1. Enter the first owner's name, email and a strong password.
2. Create the account.
3. Enter the website domain without a path.
4. Select the reporting timezone.
5. Choose Install Plausible.

Use a domain that exactly matches the hostname sent by the tracking script. Protocol and path are not part of the site domain.

Configure email delivery​

Plausible starts in local email mode, so account and site creation do not fail when an external mail provider has not been connected. Configure delivery before you rely on password reset, invitations or scheduled analytics reports:

1. Open the Plausible service in Moltern and choose Settings.
2. Add MAILER_ADAPTER=Bamboo.Mua and a verified MAILER_EMAIL sender.
3. Add SMTP_HOST_ADDR, SMTP_HOST_PORT, SMTP_USER_NAME and SMTP_USER_PWD for your provider. Store the password as a sensitive value.
4. Add SMTP_HOST_SSL_ENABLED=true when the provider requires implicit TLS.
5. Save the variables and restart Plausible, then test a password-reset email.

Use the adapter and connection settings required by your provider. Do not place SMTP credentials in site tracking code, screenshots or application repositories.

Install tracking​

Copy the script shown during onboarding into the HTML <head> of the website:

<script
  defer
  data-domain="analytics.example.com"
  src="https://your-plausible-domain/js/script.js">
</script>

Replace both example domains. After loading a page, open the Plausible dashboard and confirm that at least one visitor and the expected path are visible.

Browser privacy extensions can block analytics scripts even when your service is healthy. Verify with a clean browser profile or a controlled server-side event when troubleshooting.

Restart and persistence​

Stopping and starting Plausible replaces only its stateless runtime. The owner, site configuration and page views remain in managed PostgreSQL and ClickHouse. The same site dashboard must reopen after the service returns to Running.

Storage and metering​

Moltern records Plausible, PostgreSQL and ClickHouse as separate workloads. Billing shows CPU, memory, replicas and measured workspace usage for each. There is no hidden Plausible volume and no database is exposed through a public route.

Delete Plausible​

Choose Delete Service, select the option to remove stored data and confirm the protected action. Moltern removes Plausible, both auto-provisioned database dependencies, all three usage allocations, credentials, routes and assigned workspace paths.

Troubleshooting​

Related guides​

• PostgreSQL
• ClickHouse
• Umami
• All services

Upstream resources​

• Plausible Community Edition documentation
• Plausible integration guide