Lightweight, open-source web analytics platform without cookies, engineered for real-time tracking, privacy compliance (GDPR/CCPA/PECR), and rapid query speeds via ClickHouse.
Linux server running Docker Engine and Docker Compose v2.
x86_64 CPU with SSE 4.2 support (mandatory requirement for ClickHouse).
Minimum 2 GB RAM (4 GB recommended to provide headroom for ClickHouse JVM memory allocation).
Fast SSD or NVMe storage for ClickHouse columnar database shards.
Recommended
Documented guidance
2 vCPU / 4 GB RAM KVM Cloud Server with NVMe disk.ClickHouse leverages columnar compression and memory-mapped files for near-instant aggregations.
Public IPv4 and IPv6 addresses with reverse proxy (Nginx or Caddy) handling SSL.
Capacity depends on your workload
A 4 GB RAM server running Plausible Community Edition can comfortably ingest millions of monthly pageviews due to ClickHouse columnar storage efficiency.
We only compare what providers publish. A RAM figure alone can't confirm compatibility or production capacity.
Deploy with
Supported paths
Docker Compose (Official Community Edition setup)
Kubernetes via community Helm charts
The host must provide
Runtime
ClickHouse
>= 23.3 (Columnar database)
PostgreSQL
>= 14 (Metadata & user accounts)
Docker Compose
>= 2.15
Storage
Persistent data
Plausible uses PostgreSQL for user accounts and site metadata, and ClickHouse for event records. Both data directories must be mounted to persistent host volumes. Fast NVMe disks are strongly recommended for analytical aggregations.
Step by step
Deploying Plausible Community Edition
Clone official hosting repository
Run git clone https://github.com/plausible/community-edition /opt/plausible and enter the directory.
Generate a 64-character secret using openssl rand -base64 64 and assign it to SECRET_KEY_BASE in plausible-conf.env. Set BASE_URL to your public domain.
Run docker compose up -d. Verify that plausible, clickhouse, and postgres containers are running. Configure your reverse proxy to forward traffic on port 8000.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
Linux server running Docker Engine and Docker Compose v2.This prerequisite has no comparable published plan field.
x86_64 CPU with SSE 4.2 support (mandatory requirement for ClickHouse).This prerequisite has no comparable published plan field.
Minimum 2 GB RAM (4 GB recommended to provide headroom for ClickHouse JVM memory allocation).This prerequisite has no comparable published plan field.
Fast SSD or NVMe storage for ClickHouse columnar database shards.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
Linux server running Docker Engine and Docker Compose v2.This prerequisite has no comparable published plan field.
x86_64 CPU with SSE 4.2 support (mandatory requirement for ClickHouse).This prerequisite has no comparable published plan field.
Minimum 2 GB RAM (4 GB recommended to provide headroom for ClickHouse JVM memory allocation).This prerequisite has no comparable published plan field.
Fast SSD or NVMe storage for ClickHouse columnar database shards.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
Linux server running Docker Engine and Docker Compose v2.This prerequisite has no comparable published plan field.
x86_64 CPU with SSE 4.2 support (mandatory requirement for ClickHouse).This prerequisite has no comparable published plan field.
Minimum 2 GB RAM (4 GB recommended to provide headroom for ClickHouse JVM memory allocation).This prerequisite has no comparable published plan field.
Fast SSD or NVMe storage for ClickHouse columnar database shards.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
Linux server running Docker Engine and Docker Compose v2.This prerequisite has no comparable published plan field.
x86_64 CPU with SSE 4.2 support (mandatory requirement for ClickHouse).This prerequisite has no comparable published plan field.
Minimum 2 GB RAM (4 GB recommended to provide headroom for ClickHouse JVM memory allocation).This prerequisite has no comparable published plan field.
Fast SSD or NVMe storage for ClickHouse columnar database shards.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
Linux server running Docker Engine and Docker Compose v2.This prerequisite has no comparable published plan field.
x86_64 CPU with SSE 4.2 support (mandatory requirement for ClickHouse).This prerequisite has no comparable published plan field.
Minimum 2 GB RAM (4 GB recommended to provide headroom for ClickHouse JVM memory allocation).This prerequisite has no comparable published plan field.
Fast SSD or NVMe storage for ClickHouse columnar database shards.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
Linux server running Docker Engine and Docker Compose v2.This prerequisite has no comparable published plan field.
x86_64 CPU with SSE 4.2 support (mandatory requirement for ClickHouse).This prerequisite has no comparable published plan field.
Minimum 2 GB RAM (4 GB recommended to provide headroom for ClickHouse JVM memory allocation).This prerequisite has no comparable published plan field.
Fast SSD or NVMe storage for ClickHouse columnar database shards.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
Linux server running Docker Engine and Docker Compose v2.This prerequisite has no comparable published plan field.
x86_64 CPU with SSE 4.2 support (mandatory requirement for ClickHouse).This prerequisite has no comparable published plan field.
Minimum 2 GB RAM (4 GB recommended to provide headroom for ClickHouse JVM memory allocation).This prerequisite has no comparable published plan field.
Fast SSD or NVMe storage for ClickHouse columnar database shards.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
Linux server running Docker Engine and Docker Compose v2.This prerequisite has no comparable published plan field.
x86_64 CPU with SSE 4.2 support (mandatory requirement for ClickHouse).This prerequisite has no comparable published plan field.
Minimum 2 GB RAM (4 GB recommended to provide headroom for ClickHouse JVM memory allocation).This prerequisite has no comparable published plan field.
Fast SSD or NVMe storage for ClickHouse columnar database shards.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
Linux server running Docker Engine and Docker Compose v2.This prerequisite has no comparable published plan field.
x86_64 CPU with SSE 4.2 support (mandatory requirement for ClickHouse).This prerequisite has no comparable published plan field.
Minimum 2 GB RAM (4 GB recommended to provide headroom for ClickHouse JVM memory allocation).This prerequisite has no comparable published plan field.
Fast SSD or NVMe storage for ClickHouse columnar database shards.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
Linux server running Docker Engine and Docker Compose v2.This prerequisite has no comparable published plan field.
x86_64 CPU with SSE 4.2 support (mandatory requirement for ClickHouse).This prerequisite has no comparable published plan field.
Minimum 2 GB RAM (4 GB recommended to provide headroom for ClickHouse JVM memory allocation).This prerequisite has no comparable published plan field.
Fast SSD or NVMe storage for ClickHouse columnar database shards.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
Linux server running Docker Engine and Docker Compose v2.This prerequisite has no comparable published plan field.
x86_64 CPU with SSE 4.2 support (mandatory requirement for ClickHouse).This prerequisite has no comparable published plan field.
Minimum 2 GB RAM (4 GB recommended to provide headroom for ClickHouse JVM memory allocation).This prerequisite has no comparable published plan field.
Fast SSD or NVMe storage for ClickHouse columnar database shards.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
Linux server running Docker Engine and Docker Compose v2.This prerequisite has no comparable published plan field.
x86_64 CPU with SSE 4.2 support (mandatory requirement for ClickHouse).This prerequisite has no comparable published plan field.
Minimum 2 GB RAM (4 GB recommended to provide headroom for ClickHouse JVM memory allocation).This prerequisite has no comparable published plan field.
Fast SSD or NVMe storage for ClickHouse columnar database shards.This prerequisite has no comparable published plan field.
