Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
upstream: github.com/rybbit-io/rybbit (opens in new tab) · github.com/plausible/community-edition (opens in new tab)
Pick Rybbit
For a cookieless Google Analytics replacement that also gives you sessions, funnels, retention, user journeys and session replays under AGPL-3.0, installed by one script that brings its own Caddy — accepting that a real domain is required on day one because the tracking script must be served over HTTPS.
Pick Plausible
For the proven, deliberately minimal privacy-first dashboard with years of production use behind it, which its README lets you evaluate on localhost before a domain is involved; both stacks want 2 GB of RAM.
Rybbit and Plausible are the two picks in this hub that most people will shortlist together: both are cookieless, both are AGPL-3.0, both run on ClickHouse + PostgreSQL and both put 2 GB of RAM on the box before you store a pageview. The difference is what the dashboard is for. Plausible is the proven privacy-first report that replaced Google Analytics for a generation of self-hosters; Rybbit is the newer project that keeps the same privacy posture and adds the layer GA's free tier never had — sessions, funnels, retention, user journeys and session replays.
Plausible is a single, deliberately simple dashboard: visitors, pageviews, bounce rate, referrers, top pages, countries, devices, goals. That restraint is the product. It has been the default answer to "cookieless GA replacement" for years. Its Community Edition is the self-hostable build, and it is narrower than the cloud service: funnels, user journeys and revenue goals are Cloud features that CE does not include.
Rybbit describes itself as "the modern open source and privacy friendly alternative to Google Analytics", and its README lists what that means: sessions, unique users, pageviews, bounce rate and session duration; session replays; customizable goals, retention, user journeys and funnels; filtering across 15+ dimensions; custom events with JSON properties; country → region → city location with map visualizations; a real-time dashboard; organizations with an unlimited number of sites. That is a product-analytics feature set on a web-analytics footprint.
Both rate a modest difficulty, but the shapes differ.
SECRET_KEY_BASE, set BASE_URL, docker compose up -d, reach it on port
8000. Its README documents BASE_URL=http://localhost:8000 for evaluating
locally, and says production needs an actual domain with a DNS entry for
Let's Encrypt — so the domain comes later, not first.setup.sh that takes your domain name, writes .env
(including a generated BETTER_AUTH_SECRET), and starts Caddy,
ClickHouse, PostgreSQL, Redis, the backend and the client. The docs are
explicit: "You'll need a domain or subdomain … pointed to your VPS's IP
address. HTTPS is required because browsers block tracking scripts served
over insecure HTTP." Caddy obtains the certificate for you. If ports 80/443
already belong to your own proxy, --no-webserver exposes the backend on
3001 and the client on 3002 instead.Rybbit's docs also note the install was tested on Ubuntu 24 LTS and that an ARM server must be at least ARMv8.2-A for ClickHouse.
Both are 2 GB machines: Rybbit's docs say "try to get one with at least 2GB of RAM", and Plausible's stack (Elixir app, ClickHouse, PostgreSQL) lands on the same figure on our page. Rybbit adds Redis and Caddy to the container count, so it is the slightly busier box, but on an entry-tier VPS the two cost the same to run.
Plausible has years of production use behind it and a company whose business depends on the software staying boring. Rybbit is the newer, faster-moving project — a real consideration if you want a dashboard you never think about again. One detail to know: Web Vitals is cloud-only in practice. Rybbit's README marks it "Only available on paid tiers", and the self-hosted build hides the Performance page and its toggle, even though the docs' self-hosted-vs-cloud table still ticks it.
--no-webserver.Rybbit wins this comparison for most self-hosters because it gives the same cookieless, AGPL-3.0, 2 GB deal as Plausible and adds the sessions, funnels and replays people otherwise reach for a second tool to get — for the price of needing a real domain on day one. Plausible remains the better pick if simplicity is the feature: it is the proven, minimal report, and nothing in Rybbit's extra depth helps a site that only wants to know how it is doing.
Pick Rybbit if you want sessions, funnels, retention, user journeys or session replays from your analytics and you have a sub-domain to point at the server — its docs require a domain because the tracking script must be served over HTTPS, and the bundled Caddy issues the certificate. Pick Plausible if you want the simplest possible cookieless dashboard with a long production track record and would rather evaluate on localhost first. Both are AGPL-3.0 and both want 2 GB of RAM.
Yes. The setup script accepts --no-webserver, which skips the bundled Caddy and exposes the backend on port 3001 and the client on port 3002 for your own proxy to terminate TLS. You still need a domain: the HTTPS requirement is a browser constraint on tracking scripts, not a Caddy one.
Essentially yes. Both put ClickHouse and PostgreSQL beside the app, and both land on a 2 GB floor — Rybbit's docs say to get a VPS with at least 2 GB of RAM, and Plausible's Elixir + ClickHouse + PostgreSQL stack is 2 GB on our page. Rybbit adds Redis and Caddy to the container count, and on ARM its docs require at least ARMv8.2-A for ClickHouse.
Paid link — we earn a commission if you shop through it.
The full GA replacement vs. the privacy-first dashboard.
Funnels, journeys and replays on both — two containers on 1 GB, or six on ClickHouse and 2 GB.
A single Go binary on a SQLite file vs. the lightest modern analytics dashboard.