---
title: "Deploy Plausible vs Umami"
description: "Plausible CE vs Umami, both self-hosted analytics"
category: "Analytics"
url: https://railway.com/deploy/deploy-plausible-vs-umami-analytics-on-r
---

# Deploy Plausible vs Umami

Plausible CE vs Umami, both self-hosted analytics

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

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

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

## Template content

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

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

### ClickHouse

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

### 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

## Documentation

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

Plausible CE and Umami are open-source, cookieless web analytics tools you can self-host. Plausible uses Postgres for config and ClickHouse for events, scaling to high traffic. Umami runs on one PostgreSQL database, simpler but capped sooner on huge volumes.

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

Plausible CE is AGPL-3.0, Elixir, with Postgres for users/sites/goals and ClickHouse for events. The official image `ghcr.io/plausible/community-edition:v3.2.1` runs the same start command as upstream. The Railway template includes a public HTTPS domain, Postgres, ClickHouse, and volumes.

Plausible's dashboard covers top pages, referrers, countries, devices, live view. Goals, custom events, outbound links, downloads, form submissions are built in. v3 added scroll depth, engagement time, segments, team roles. Umami offers a clean dashboard with pageviews, referrers, custom events, but fewer advanced features. Neither ships marketing funnels.

Pick Umami for a single-database, MIT setup on lower traffic. Pick Plausible CE for ClickHouse scale, Stats API, or documented daily rotating salt hashing.

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

Running either on Railway keeps data in a region you choose without patching a VPS. The Plausible template wires app, Postgres, and ClickHouse with private networking and volumes.

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 Umami 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 Umami self hosting

| Provider | Data location control | Who runs the box | Plausible vs Umami fit |
|---|---|---|---|
| DigitalOcean | Pick a region, but you manage droplets and backups | You | Fine for Umami on one droplet; Plausible CE needs manual Postgres and ClickHouse setup |
| AWS | Broad region choice, but IAM, VPC, and RDS add overhead | You | Overkill for a small analytics stack unless you already live in AWS |
| Hetzner | EU regions by default, cheap servers | You | Good for EU residency if self-managed; Railway with an EU region gives same data location with less ops |

## Common Use Cases for hosted Plausible vs Umami

- **GDPR-friendly pageview analytics:** No cookies or persistent identifiers, so typically no cookie banner. Plausible publishes a legal assessment; a lawyer or DPO has the final word.
- **Client reporting:** Create a site per client, invite teammates, share revocable dashboards.

## Dependencies for Plausible vs Umami Docker hosted on Railway

Plausible CE needs the Elixir app, PostgreSQL for config, ClickHouse for events, and two persistent volumes. Umami needs only a Node.js app and one PostgreSQL database, lighter but less scalable at high event counts. Plausible's ClickHouse volume holds all raw events; Postgres holds configuration. Backing up one without the other loses data.

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

- **Plausible CE app:** Image `ghcr.io/plausible/community-edition:v3.2.1`, port 8000, public domain, volume `/var/lib/plausible`, start command runs createdb, migrate, run.
- **Railway Postgres:** Stores users, sites, goals, settings; app reads `DATABASE_URL`.

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

The template uses the official image, not a fork. v3.2.1 removed a `/storybook` RCE endpoint (CVE-2026-8467) present in v3.0.0-v3.2.0. Security fixes aren't backported, so patching is part of privacy duty. Healthcheck hits `/api/health`, reporting Postgres, ClickHouse, sessions. Railway private networking is IPv6, so set `LISTEN_IP=::` and `ECTO_CH_IPV6=true`.

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

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

* **Cookies and consent:** GA4 uses cookies, usually requires consent banners on EU sites; Plausible CE uses none, Plausible says consent typically not needed.
* **Script weight:** Plausible's script is about 54x smaller.
* **Data ownership:** GA4 is closed, Google-hosted; Plausible CE puts data in your Postgres and ClickHouse volumes.

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

* **Default tracking:** Matomo uses cookies by default, needs cookieless config; Plausible CE is cookie-free by design.
* **Feature set:** Matomo heatmaps, funnels, A/B testing are paid plugins; Plausible CE includes goals, events, segments, Stats API free.
* **Stack:** Matomo is PHP + MySQL/MariaDB; Plausible CE is Elixir + Postgres + ClickHouse.

### Plausible CE vs Umami (Umami Alternative)

* **License and stack:** Plausible CE AGPL-3.0 on Elixir with Postgres+ClickHouse; Umami MIT on Node/Next.js with PostgreSQL only since v3.
* **Operational complexity:** Umami runs one app and one DB; Plausible adds ClickHouse, more memory but scales further.

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

* **Cost and support:** CE free AGPL-3.0, community support, two releases/year; Cloud from $9/mo up to 10k pageviews, advanced bot filtering.
* **Missing features:** CE lacks funnels, user journeys, ecommerce revenue goals, SSO, Sites API. Data Studio connector not in CE.

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

After registering first user at `/register`, add a site and copy the site-specific snippet from Site Settings / General / Site Installation into the page head. Since v3.1 the snippet is site-specific. Custom events via tracker API or `@plausible-analytics/tracker`. Goals come from page URLs or event names. Umami: add website, copy script tag, use tracker.

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

Plausible CE setup is more involved; Umami is simpler (clone repo, set database URL, run Next.js with Postgres).

### 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

Docker and Docker Compose. CPU needs SSE 4.2 or NEON for ClickHouse. At least 2 GB RAM recommended.

### Configure Environment Variables

Create `.env` with `BASE_URL` and `SECRET_KEY_BASE` (`openssl rand -base64 48`). Set `HTTP_PORT=80` and `HTTPS_PORT=443` for Let's Encrypt, or use reverse proxy. Add `DISABLE_REGISTRATION=invite_only` after first user.

### Start the Plausible vs Umami Application

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

Visit `BASE_URL`, register at `/register`. For Umami: `npm install`, set `DATABASE_URL`, then `npm run build && npm start`.

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

Plausible Cloud monthly up to 10k pageviews: Starter $9 (1 site, 3yr retention), Growth $14 (3 sites, 3 members), Business $19 (10 sites, 10 members, 5yr retention, funnels, revenue, Stats API). Prices rise with pageviews; 100k costs $19/$29/$39. Yearly billing gives 2 months free, 30-day trial, no credit card. Plausible CE free AGPL-3.0.

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

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

Low-traffic Plausible CE typically $10-20/mo across three services. Railway Hobby is $5/mo including $5 usage; new accounts get $5 trial credit. Trial services cap 1 GB RAM each, tight for ClickHouse. Umami costs less, often under $10/mo (app+Postgres). Backups: Plausible needs Postgres plus ClickHouse volume; Umami one Postgres backup.

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

Plausible CE: CPU with SSE 4.2 or NEON, at least 2 GB RAM, disk for Postgres and ClickHouse; ClickHouse is biggest memory consumer. Umami runs on 1 GB RAM and small Postgres for low traffic; high volume needs scaling. Both run behind HTTPS.

## Frequently Asked Questions (FAQs)

### Is self-hosted Plausible GDPR compliant?

Plausible says its cookieless tracking doesn't require cookie banners or consent for analytics, and publishes a legal assessment. That position applies to CE code as well. GDPR still applies to any processing; your privacy policy should mention analytics and hosting provider; lawyer/DPO has final word. Software doesn't make you automatically compliant.

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

No. Plausible uses no cookies, no localStorage/browser cache, no persistent identifiers. Plausible says consent not needed. Check local guidance if combined with cookie-using tools.

### Does Plausible store IP addresses?

No. Raw IPs never stored. Unique visitors hashed with daily salt, website domain, IP, user agent. Salt rotates and is deleted every 24h, so same person can't be recognized across days. Raw User-Agent not stored.

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

In Postgres and ClickHouse volumes in the Railway region you choose. Pick EU region if residency matters. Railway becomes your hosting provider/processor; you control backups and retention.

### How much does it cost on Railway?

Low-traffic Plausible CE usually $10-20/mo across three services. Umami often under $10/mo. Trial services cap 1 GB RAM, tight for ClickHouse.

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

CE lacks marketing funnels, user journeys, ecommerce revenue goals, SSO, Sites API, advanced bot filtering (data center IP exclusion). Community support only, releases twice a year. Security fixes not backported; patch promptly.


## Similar templates

- [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
- [Typesense vs Meilisearch](https://railway.com/deploy/typesense-vs-meilisearch) — self-hosted Typesense vs Meilisearch

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