Self-host Plausible on redu
Plausible is lightweight, privacy-friendly, cookie-free web analytics, a simple alternative to Google Analytics that does not track personal data. People self-host it to keep full ownership of their visitor data and run their own analytics stack. With redu, your agent runs Plausible for you on real EU infrastructure, so you set nothing up by hand.
License: Plausible is licensed under AGPL-3.0. AGPL, GPL, and permissive licenses all allow self-hosting freely, and in this guide you are the operator running Plausible on your own redu infrastructure.
Deploy it with your agent
Connect the redu MCP:
claude mcp add --transport http redu-cloud https://mcp.redu.cloud/mcpPoint your agent (Claude Code is one example, any MCP client works) at Plausible’s official Community Edition Docker setup and tell it:
Deploy Plausible on redu using its official docker-compose, and expose the web UI.Plausible Community Edition ships an official docker-compose.yml that runs the app together with its datastores. Your agent uses deploy_compose to bring the whole stack up on one EU VM with podman-compose up -d --build, and serves the Plausible web UI at https://<name>.redu.cloud. redu never rewrites your compose file; it runs the stack as published and exposes the one service you asked for.
Database
Plausible needs two datastores: PostgreSQL for app and account data, and ClickHouse for the analytics event data. The cleanest option is to keep both database services from Plausible’s official compose file, so the full stack runs together on the one VM. That is the default deploy_compose mode, and it works out of the box.
If you would rather run Plausible’s relational data on managed infrastructure, your agent can provision a redu managed Postgres and point Plausible’s Postgres connection at it:
Provision a managed Postgres and use it for Plausible's PostgreSQL, keeping ClickHouse in the compose stack.When a managed database is provisioned, its connection env (including DATABASE_* aliases alongside the standard PG* variables) is appended to the compose project’s .env. ClickHouse stays as a service in the compose file, since it holds the analytics events.
Access it
Once the deploy finishes, Plausible comes up at https://<name>.redu.cloud with TLS handled for you by a wildcard certificate, so there is no per-app certificate setup. On first run, open that URL and follow Plausible’s own setup flow to create your admin account and register your first site.
Keep it running
Deploys are self-healing: redu recreates and retries until Plausible actually runs, and get_deployment returns the build log if you want to see what happened. Day-2, because this is a real VM with SSH, your agent can connect to the machine to update Plausible, adjust its configuration, or fix an issue in place, and commit any repo changes back with a GitHub token.
What’s next
Stuck? support@redu.cloud