← all SaaS
Self-host Amplitude
Product analytics / event tracking / funnels ·
Category: observability & analytics
Amplitude tracks user events to power funnel, retention, and cohort analysis on product usage. The self-hostable replacements all do event ingest + analysis well; PostHog is the closest one-for-one fit because it bundles the same primitives (events, persons, cohorts, funnels) plus session replay.
Amplitude pricing anchor: Free tier up to 10M events/mo; Plus/Growth start at $49/mo and rise sharply with event volume.
- GitHub
- ★ 34.4k · last commit today · 3966 open issues
- License
-
MIT Core is MIT; PostHog also publishes a 'PostHog Cloud' commercial license for some enterprise add-ons, but self-host of the OSS edition is unrestricted.
- Setup time
- 20min docker-compose (the official `hobby` deploy is one command)
- Monthly cost
- $20-40 VPS — ClickHouse + Postgres + Kafka + Redis + the app; demanding stack but absorbs serious event volume.
Migration sketch. Use Amplitude's Export API (`GET /api/2/export`) to stream events as JSONL. Run PostHog's `posthog-cli migrate amplitude --in events.jsonl` (or write a 30-line Node script that POSTs to `/capture`). Person properties from Amplitude map to PostHog person properties; event names + properties carry over directly. Funnels and retention reports rebuild against the imported data.
Good fit forTeams whose Amplitude use is funnel + retention + feature flags — PostHog matches that surface and adds session replay and surveys.
Weak atHeavy resource footprint vs. lighter analytics tools; ClickHouse is excellent but adds an ops surface most small teams don't have.
- GitHub
- ★ 4.41k · last commit 2d ago · 39 open issues
- License
-
AGPL-3.0 AGPL on the OSS server; some downstream connectors are Elastic License v2.
- Setup time
- 30min docker-compose (rudder-server + Postgres + transformer + control plane)
- Monthly cost
- $15 VPS for the server; storage is wherever you route events (BigQuery / Snowflake / your own Postgres).
Migration sketch. RudderStack is shaped like a Segment / CDP — it ingests events and forwards them to destinations. To replace Amplitude: write a destination (or use the built-in Postgres / ClickHouse warehouse destination) and run analysis with Metabase or Superset on top. Amplitude SDKs swap to the RudderStack SDKs with similar APIs; backfill via Amplitude's Export API into your warehouse.
Good fit forTeams that want a CDP shape — events fan out to many tools — and are happy doing analysis in a separate BI layer.
Weak atNot an analytics tool by itself; you still need Metabase / Superset / a warehouse to do funnels. Higher overall stack count.
- GitHub
- ★ 24.8k · last commit 2d ago · 71 open issues
- License
-
AGPL-3.0 - Setup time
- 10min docker-compose (Elixir app + ClickHouse + Postgres)
- Monthly cost
- $10 VPS; ClickHouse is the heaviest piece but tiny at startup volumes.
Migration sketch. Plausible is more web-analytics-shaped than product-analytics-shaped — it replaces Amplitude only if your usage was mostly pageview / event count / referrer reporting, not deep funnels. Swap the snippet on your site, optionally backfill historical events via the import-from-GA tool (no Amplitude importer; you'd write JSON → Plausible Events API yourself).
Good fit forLightweight product/web analytics with great UX and a privacy-first stance; a step down in depth from Amplitude/PostHog.
Weak atNo funnels-as-first-class, no retention cohorts the way Amplitude or PostHog do them.
In a terminal? npx os-alt amplitude prints this table —
how the CLI works →