We are not going to pretend otherwise on our own website. Here is where each of us wins, with every number sourced.
This section comes first because putting it last would be a trick. All of it is real, shipped, and ours is not.
PostHog is MIT-licensed and you can run it. Their own guide is candid about the limits, and quoting only the first half of that sentence would be the dishonest way to tell a true story:
You can land external data next to your events and query all of it. Kilden has no warehouse and no SQL surface: you get the reports we built, and when a question falls outside them you are stuck.
Whole products we simply do not have. Our session replay records exceptions and network activity, which is a different and much smaller thing.
Both are theirs. Ours is a short list.
Their volume tiers keep stepping down. Ours do not, and the price table below shows exactly where that overtakes us.
Plenty of pages still claim PostHog is analytics-only. It has not been for a while: replay, feature flags and experiments are all there and mature. If you read that somewhere else, it was out of date — including, until we checked, on this site.
Correcting a competitor in their favour is the cheapest way to earn the right to be believed about the rest.
Four things. We are going to describe them at their real size rather than inflate them.
A conversation in Kilden cannot be read without a JWT signed by your server. It is not a setting; the messenger refuses unsigned reads outright. That is an architectural decision made once, and it is the difference between "we support identity verification" and "impersonation is not reachable".
Campaign journeys, a two-way messenger with an inbox, and in-app guides all run in production for our customers today. PostHog is building the same territory and is honest about where it is:
For a lot of Latin America, email is not where customers answer. Kilden sends campaign steps over WhatsApp; PostHog's workflows document email, Slack and webhooks.
Spanish, Portuguese and French, fully translated — not a locale file with half the strings in English. If your team does not work in English, this is the difference between a tool people use and one that one person on the team operates.
Three usage profiles, fixed before the numbers were run so we could not pick the flattering one. Both columns are computed from published rates.
| Monthly usage | PostHog | Kilden |
|---|---|---|
|
Starting out
1M events · 5K replays
|
Free | Free |
|
In the plan
2M events · 10K replays
|
$75.00 | $49.00 |
|
Growing
5M events · 10K replays
|
$177.90 | $349.00 |
Kilden is the cheaper option between about 1.5M and 2.4M events a month, at 10K replays. Outside that band, PostHog is — their usage-only bill undercuts our flat base below it, and their volume tiers do above it.
PostHog bills anonymous events far below identified ones, which most sites will benefit from and our table does not model. They also publish a discount you can simply ask for. Both make their real bill lower than the column above.
PostHog meters each product separately: events, recordings, flag requests, survey responses, warehouse rows. Kilden bills three meters and includes the rest. That is a preference, not a victory — a metered bill is fairer when you use one product, and worse when you use five.
It is on our roadmap and we are not going to promise a date. If running the code yourself is a requirement rather than a preference, that decision is already made, and it is not us.
No. Open sourcing is on our roadmap and we will not promise a date for it. PostHog is MIT-licensed today, and if that is a hard requirement your decision is already made.
Up to roughly a couple of million events a month with steady replay usage, yes. Past that, no — their volume tiers step down and ours do not. The table on this page computes both from published rates so you can find your own volume rather than trust a slogan.
Yes to both, and anyone telling you otherwise is working from old information. Their Workflows have graduated to beta and they ship a support inbox with a chat widget. The difference we claim is maturity, not existence.
You can, and their own documentation is the best guide to whether you should: they call self-hosted deployments officially unsupported, keep paid features to their cloud, and steer you to hosting once you pass a fairly small monthly volume.
Because breadth is a cost as well as a feature. If what you need is analytics plus the messaging that acts on it, in your language, on one bill, a smaller surface is easier to hold in your head. If you need a warehouse and error tracking, it plainly is not.
Every PostHog figure on this page was verified against the pages below on August 1, 2026. If one of them has changed since, tell us and we will fix it.
Free plan, no card. If you end up on PostHog instead, we would rather it was for a reason you found here than a claim we made up.