Self-host Matomo on redu

Matomo is a privacy-respecting, self-hosted web analytics platform, an open source alternative to Google Analytics where you keep full ownership of your visitor data. People self-host it to get accurate, cookie-friendly analytics without handing traffic data to a third party. On redu, your AI agent runs Matomo for you on real EU infrastructure, so you set nothing up by hand.

License: Matomo is licensed under GPL-3.0. It is open source, so you can self-host it freely, and in this guide you are the operator running Matomo 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/mcp

Point your agent at Matomo’s official Docker setup and tell it:


Deploy Matomo on redu using its official docker-compose, and expose the web UI.

Matomo ships an official Docker image and docker-compose examples (the matomo-org/docker project), which is a multi-container stack (the Matomo web app plus a database). Your agent uses deploy_compose to run the whole stack on one EU VM and serve the Matomo web UI at https://<name>.redu.cloud. redu does not rewrite your compose file, it runs it as is and exposes the one service you point it at.

Database

Matomo requires a MySQL or MariaDB database. You have two clean options:

Keep the db service from Matomo’s compose file (the default). The official example includes a MariaDB service, so the whole stack, app plus database, runs together on the one VM. Nothing extra to provision.
Use a redu managed database if you want the database on its own VM, separate from the app. Tell your agent:
```
Deploy Matomo on redu with a managed database and expose the web UI.
```
The agent provisions the managed database and appends the connection details to the compose project’s .env. redu injects DATABASE_* env aliases alongside the standard MYSQL_* variables, so the connection is available without extra mapping.

Either way your visitor data stays on your redu infrastructure in the EU.

Access it

Once the deploy finishes, Matomo comes up at https://<name>.redu.cloud with TLS already in place (a wildcard cert), so there is no per-app certificate setup. On first load, Matomo walks you through its own installation wizard to confirm the database connection and create your admin account. Follow that wizard in the browser to finish setup.

Keep it running

Deploys are self-healing: redu recreates and retries until Matomo actually runs, and get_deployment returns the build log if you want to see what happened. Day two, your agent can SSH into the VM to update Matomo, adjust config, or fix the stack in place, and commit any repo changes back with a GitHub token. You stay the operator without babysitting the machine.

What’s next

Stuck? support@redu.cloud