PostHog, in its own terms
PostHog is an open-source product analytics platform spanning more than ten products, including session replay, feature flags, experiments, surveys, error tracking and a data warehouse. Its cloud has a generous free tier, a million analytics events a month among other allowances, with usage-based pricing above it. Self-hosting is MIT licensed and offered as a Docker Compose deployment, but PostHog's own documentation describes it as being for hobbyists, notes it runs on a single machine and is unlikely to scale far past a few hundred thousand events, and states that self-hosted users cannot receive commercial support.
Checked against posthog.com/pricing and posthog.com/docs/self-host/open-source/disclaimer in august 2026. Products change; verify anything you are deciding on.
Where they actually differ
| Falorb | PostHog | |
|---|---|---|
| Scope | Analytics only | 10+ products in one platform |
| Licence | MIT | MIT for the open-source build |
| Self-hosting | The supported, intended path | A hobby build, cloud recommended |
| Session replay | Deliberately not implemented | Included |
| Feature flags & experiments | Not offered | Included |
| Free tier | All of it, self-hosted | Generous free cloud tier |
| Portfolio view | Every property on the first screen | Project-based |
Which one you should actually use
- You want session replay, feature flags and experiments alongside analytics.
- A free cloud tier that covers your volume is more useful than self-hosting.
- You are instrumenting one product deeply rather than several lightly.
- You want a large team and roadmap behind the tool.
- Self-hosting in production is a requirement, not a preference.
- You want a system small enough to read in an afternoon.
- Your visitors span several properties that should resolve to one audience.
- You do not want session replay anywhere near your visitors' screens.
The Falorb side, in the real interface
vs PostHog: the usual questions
Can I not just self-host PostHog?
You can, and it is MIT licensed. PostHog's own documentation is candid that the open-source deployment is aimed at hobbyists, runs on a single machine, is unlikely to scale far past a few hundred thousand events without significant work, and comes with no commercial support. If production self-hosting is your requirement, that disclaimer is the thing to read first.
Does Falorb do session replay?
No, deliberately. Recording a visitor's screen is a much larger privacy commitment than counting their clicks. The event schema and the tracker leave the extension point open for anyone who wants to add it to their own deployment.
Still deciding?
The fastest way to decide is to run it
Clone the repository, bring the stack up with Docker Compose and paste one script tag. Ten minutes, and no account anywhere.