Compare / OpenReplay vs PostHog

OpenReplay vs PostHog

Pick OpenReplay if you only want recordings (skip ee/). Pick PostHog if you want the published Amplitude / Hotjar stack (funnels plus replay).

Facts checked 25 Oct 2026. License, language, and GitHub activity come from the catalog or the project's own repo. "Not in the catalog row" means the public catalog dump does not store that number.

OpenReplay in the catalog PostHog in the catalog Start on Railway

How they compare

OpenReplayPostHog
LicenseAGPL-3.0 default; ee/ is a separate license — skip it (catalog) sourceSee PostHog/posthog LICENSE (not in the catalog row) source
LanguageTypeScript (catalog) Python (PostHog/posthog)
GitHub activity13,043 stars in the catalog source40,416 stars, pushed 25 Oct 2026 (not in the catalog row) source
Self-hostNamed on /stacks/posthog-insights. Replay box; skip ee/. Published as /stacks/posthog-insights. Multi-service (web, worker, Postgres, Redis, ClickHouse).
Best forRecordings only. The published product-analytics plus replay path.

Self-hosting and resource needs

PostHog is the published lander — /stacks/posthog-insights. OpenReplay is openreplay/openreplay — skip ee/. Swetrix is pageviews, not this pair. Umami is cookieless pageviews.

FAQ

Is this Plausible?
Cookieless pageviews stay on /replace/plausible-cloud. This pair is replay.
Where is Swetrix?
Pageviews — /stacks/swetrix-analytics. Not this pair.
Are these free?
OpenReplay's default tree is AGPL-3.0 if you skip ee/. You pay hosting.
How do I deploy replay?
Open /stacks/posthog-insights. Persist the store. Confirm one replay.

Related pages

Stack of the Week

Get one stack a week that replaces a SaaS bill.

Sponsor this page