Replace PostHog
Self-hostable, but as a large separate deployment rather than something you mount.
Why teams move off PostHog
PostHog is self-hostable and genuinely good, and it is a large separate deployment with its own datastore rather than something you mount.
What you give up
Session replay and the integrated feature-flag and experiment suite.
This directory says so when an engine only covers part of the job. A replacement that needs a caveat is still worth knowing about — it just should not surprise you in week three.
1 Rails engine that replaces PostHog
Questions
- Is there an open-source alternative to PostHog for Rails?
- Yes — Ahoy. It mounts into an application you already run, so there is no second deployment and no second database.
- What do I give up by replacing PostHog?
- Session replay and the integrated feature-flag and experiment suite.
- How do I replace PostHog in a Rails app?
- Add ahoy_matey to your Gemfile, mount it in config/routes.rb at /ahoy, and run its migrations. The whole integration is two lines and a migration.
- How much does replacing PostHog save?
- PostHog is priced free tier, usage-priced. The engines here are open source, so the cost becomes the time to mount one and the resources it uses inside your existing application.
Same category
