---
title: "Deploy Plausible vs Matomo"
description: "Lightweight Plausible CE vs full-suite Matomo"
category: "Analytics"
url: https://railway.com/deploy/deploy-plausible-vs-matomo-analytics
---

# Deploy Plausible vs Matomo

Lightweight Plausible CE vs full-suite Matomo

**[Deploy Plausible vs Matomo on Railway](https://railway.com/template/deploy-plausible-vs-matomo-analytics)**

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/deploy-plausible-vs-matomo-analytics/manifest.json

- **Creator:** onepush
- **Category:** Analytics

## Template content

### plausible

- **Image:** ghcr.io/plausible/community-edition:v3.2.1
- **Start command:** `sh -c "/entrypoint.sh db createdb && /entrypoint.sh db migrate && /entrypoint.sh run"`
- **Health check:** /api/health
- **Public domain:** Yes

### ClickHouse

- **Image:** clickhouse/clickhouse-server:24.12-alpine

### Postgres https://devicons.railway.app/i/postgresql.svg

- **Image:** ghcr.io/railwayapp-templates/postgres-ssl:18

## Documentation

# Deploy and Host self hosted Plausible vs Matomo (Open-Source Cookieless Web Analytics) on Railway

Plausible CE is cookieless by default with a light dashboard. Matomo is a full GA-style suite that can run cookieless only if configured. Both are open source, but the tradeoffs differ.

## About Hosting Plausible vs Matomo open-source software on Railway (self hosted Plausible template)

This template runs Plausible CE v3.2.1, an AGPL-3.0 Elixir app on Postgres and ClickHouse. Matomo is not deployed here, but teams compare both. Plausible CE sets no cookies, localStorage, browser cache, or persistent identifiers. Unique visitors use a daily rotating salt, IP, and User-Agent hash; raw IPs and User-Agents are never stored.

## Why Deploy Plausible vs Matomo, the cookie-free Google Analytics alternative on Railway (Railway Free Trial)

Deploy Plausible CE on Railway to keep visitor data on infrastructure you control, in a region you choose, without cookie banners or Google pageviews. The CE image matches the official community-edition compose file, so the stack is the same as upstream. Plausible publishes a legal assessment saying no cookie banner or consent is needed for analytics.

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Plausible vs Matomo on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.

### Railway vs Other Hosting Providers and VPS for Plausible vs Matomo self hosting

| Provider | Data location and who runs the box |
|---|---|
| DigitalOcean | You pick a region, but you run and patch the VM, Docker, and backups. |
| AWS | Broad region choice, but IAM, VPC, EBS snapshots, and patching are your job. |
| Hetzner | Usually EU-first, good for privacy questionnaires; you manage the server. |

## Common Use Cases for hosted Plausible vs Matomo

- Marketing sites needing pageview/referrer data without consent banners.
- Product teams tracking custom events and goals without sending PII to a third party.
- Agencies needing shared or embedded dashboards.
- Internal apps tracking outbound links, downloads, and form submissions.
- GA4 migration when legal says no cookies before consent.

## Dependencies for Plausible vs Matomo Docker hosted on Railway

This template uses three Railway services: Plausible CE, managed Postgres, and ClickHouse. Postgres stores accounts, sites, goals, and settings. ClickHouse stores raw events. The app uses the official image, a volume at `/var/lib/plausible`, and port 8000 on a public HTTPS domain.

### Deployment Dependencies for Managed Plausible vs Matomo Service (Cookieless Web Analytics)

- `plausible`: `ghcr.io/plausible/community-edition:v3.2.1`, port 8000, HTTPS domain, volume `/var/lib/plausible`, healthcheck `/api/health`.
- `Postgres`: Railway managed Postgres for users, sites, goals, settings.
- `ClickHouse`: `clickhouse/clickhouse-server:24.12-alpine`, volume `/var/lib/clickhouse`, user `plausible`, database `plausible_events_db`.

### Implementation Details for Plausible vs Matomo (Using Plausible CE official docker image)

The start command runs `/entrypoint.sh db createdb`, then `db migrate`, then `run`. Railway private networking is IPv6, so `LISTEN_IP=::` and `ECTO_CH_IPV6=true` are set. `BASE_URL` uses the Railway public domain, `SECRET_KEY_BASE` is 64 bytes and stable, `TOTP_VAULT_KEY` encrypts 2FA. `DISABLE_REGISTRATION=invite_only` lets the first user register as owner.

## How does Plausible vs Matomo compare against other privacy-friendly analytics platforms

### Plausible CE vs Google Analytics 4 (GDPR and consent)

- **Cookies and consent:** GA4 uses cookies and Google hosting, so EU sites usually need consent. Plausible CE stores no cookies, so Plausible says no cookie banner is needed.
- **Script weight:** Plausible says its script is 54 times smaller than GA.
- **Data ownership:** CE events stay in your Postgres and ClickHouse. GA4 is closed and Google-hosted.
- **Features:** GA4 has deeper ads/ecommerce. CE has a one-page dashboard, goals, custom events, and GA import.

### Plausible CE vs Matomo (cookieless mode vs cookie-free by design)

- **Default behavior:** CE is cookie-free by design. Matomo sets cookies by default; cookieless mode is config.
- **Stack weight:** CE is Elixir plus Postgres and ClickHouse. Matomo is PHP plus MySQL/MariaDB, with some paid plugins.
- **Report depth:** Matomo offers full reports, ecommerce, and recordings. CE has one dashboard, goals, events, campaigns. Funnels and ecommerce revenue are not in CE.
- **Scaling:** CE uses ClickHouse, which scales raw events well but adds memory. Matomo raw visits in MySQL can get heavy without archiving.

### Plausible CE vs Umami (Umami Alternative)

- **License and stack:** Umami is MIT/Node.js; CE is AGPL/Elixir. Both cookieless.
- **Database:** Umami v3 uses PostgreSQL only. CE uses Postgres plus ClickHouse.
- **Hosted plans:** Umami Hobby free up to 100K events/mo, Pro $20/mo. Plausible Cloud starts at $9/mo.
- **Features:** CE has GA import, teams, email/Slack reports. Umami is leaner with one DB.

### Plausible CE vs Plausible Cloud (EU-hosted SaaS)

- **Data location:** Cloud is EU-hosted by an Estonian company. CE sits in your Railway region; pick EU if needed.
- **Bot filtering:** Cloud excludes about 32K data center IP ranges. CE has basic UA/referrer filtering.
- **Missing features:** Funnels, journeys, ecommerce revenue, SSO, Sites API, Looker Studio are not in CE.
- **Ops burden:** Cloud patches everything. CE means you own upgrades and security fixes, like v3.2.1's RCE fix.

## How to use Plausible vs Matomo (the OSS cookieless analytics tool)?

Create the first user at `/register`; that account becomes owner. Registration stays invite-only. Add a site, copy the snippet, and paste it into the head section. Enable 2FA for every account. For invites, resets, or reports, configure Postmark, Mailgun, or SendGrid; Railway blocks outbound SMTP below Pro. Country geolocation works offline with bundled db-ip.

## How to self host Plausible vs Matomo on other VPS Services (Plausible CE self hosting guide)

This covers Plausible CE on a VPS, not Matomo.

### Clone the Repository

```bash
git clone -b v3.2.1 --single-branch https://github.com/plausible/community-edition plausible-ce
cd plausible-ce
```

### Install Dependencies

Use Docker Compose. CPU must support SSE 4.2 or NEON for ClickHouse.

```bash
docker compose pull
```

### Configure Environment Variables

Create `.env` with `BASE_URL=https://analytics.example.com` and `SECRET_KEY_BASE=$(openssl rand -base64 48)`. Set `HTTP_PORT=80` and `HTTPS_PORT=443`, plus a compose override for ports 80/443 for Let's Encrypt, or use a reverse proxy.

### Start the Plausible vs Matomo Application

```bash
docker compose up -d
```

Visit `BASE_URL`, create the first user, and keep the image current; security fixes are not backported.

## Official Pricing of Plausible vs Matomo (Plausible pricing)

Plausible CE is free, AGPL-3.0. Plausible Cloud starts at $9/mo for 10K pageviews, one site, 3 years retention. Growth $14/mo for 3 sites, 3 members. Business $19/mo for 10 sites, 10 members, 5 years retention, funnels, revenue, Stats API. Prices rise with pageviews; yearly billing gives two months free; 30-day trial, no card.

## Plausible vs Matomo cloud vs self hosted comparison (Pricing, features, costs, and more)

### Monthly cost of self hosting Plausible vs Matomo on Railway

A low-traffic CE site usually costs $10-20/mo across three Railway services. Hobby is $5/mo including $5 usage; new accounts get $5 trial credit. Trial services cap at 1 GB RAM each, tight for ClickHouse, so treat trial as a test. Back up Postgres and the ClickHouse volume; one without the other loses data.

### System Requirements for Hosting Plausible vs Matomo on a VPS

Plausible CE needs SSE 4.2 or NEON and 2 GB RAM to avoid OOM kills. ClickHouse is the biggest memory consumer. MaxMind city data adds about 1 GB RAM. Matomo has different PHP/MySQL requirements; this template doesn't deploy it.

## Frequently Asked Questions (FAQs)

### Is self-hosted Plausible GDPR compliant?

Plausible's legal assessment says no cookie banner or consent is needed for analytics. That's Plausible's position, not legal advice. GDPR still applies; your privacy policy should name analytics and hosting provider; a lawyer or DPO has final word.

### Do I need a cookie banner with Plausible?

No. CE sets no cookies, localStorage, or browser cache, and uses no persistent identifiers. Plausible says no cookie banner is needed. Other tools may still require consent.

### Does Plausible store IP addresses?

No. Unique visitors use `hash(daily_salt + website_domain + ip_address + user_agent)`. Salt rotates daily and is deleted; raw IPs and User-Agents never stored. Stored: page URL (query params dropped except campaign params like `utm_source`), referrer, campaign, derived browser/OS/device, country, engagement, pageviews, custom events, custom properties.

### Where is my analytics data stored on Railway?

Postgres and ClickHouse live in the Railway region you choose. Pick EU if residency matters. Railway is your hosting provider/processor. Deleting a site removes stats, but backups also hold copies; include them in retention.

### How much does it cost on Railway?

Around $10-20/mo for low traffic. Hobby $5/mo including $5 usage; new accounts get $5 trial credit. More events/RAM cost more.

### What's missing from CE compared to Cloud?

CE lacks funnels, journeys, ecommerce revenue, SSO, Sites API, Looker Studio. CE has basic bot filtering; Cloud excludes about 32K data center IPs. CE can export/import to and from Cloud.


## Similar templates

- [Typesense Multilingual](https://railway.com/deploy/deploy-typesense-multilingual-search) — Locale-aware multilingual search with Typesense
- [Formbricks | Open-Source Typeform & Qualtrics Alternative](https://railway.com/deploy/formbricks-surveys) — Surveys, NPS and in-app feedback on your own Postgres, Hub and Cube
- [Typesense PHP](https://railway.com/deploy/typesense-php) — official PHP client against Railway

Open this page in a browser: https://railway.com/deploy/deploy-plausible-vs-matomo-analytics