Home/PostHog alternative

A PostHog alternative for a website, not a product team

PostHog is a platform: session replay, feature flags, experiments, surveys, error tracking, a data warehouse, SQL. It is generous — a million events a month for free — and its JavaScript bundle weighs about 95 KB gzipped, it stores data in a cookie by default, and it asks you to choose a region before you have measured anything. Kipstats is the other end of that: one 4.2 KB script, no cookie, and the numbers a website owner acts on.

Start for free Open the live demo

PostHog figures read on its pricing, docs and CDN, September 2026.

In short: if you are building a product and need to watch a session, flip a flag or run an experiment, PostHog is the right tool and this page will not talk you out of it. If you run a website that has to convert — a shop, a SaaS marketing site, a lead form — you are carrying a 95 KB bundle and a cookie banner for a dashboard you use at 10 %.

Kipstats vs PostHog, line by line

PostHog's free tier is genuinely large; the table says so.

Free tier

Kipstats

1 site, 10K pageviews/month

PostHog

1M events/month, 1 project

Paid from

Kipstats

9€/month

PostHog

Pay as you go, ~$50 for the 2nd million events

Script, gzipped

Kipstats

4.2 KB

PostHog

~95 KB

Cookies by default

Kipstats

None

PostHog

Yes, 1 year

Cookieless mode

Kipstats

Always

PostHog

Yes, drops identify() and alias()

EU hosting

Kipstats

Yes

PostHog

EU Cloud (Frankfurt), chosen at signup

Session replay

Kipstats

PostHog

Yes

Feature flags & A/B tests

Kipstats

PostHog

Yes

Surveys, error tracking, warehouse

Kipstats

PostHog

Yes

Rage clicks, dead clicks, JS errors

Kipstats

Yes

PostHog

Via session replay

Revenue from your server

Kipstats

Yes

PostHog

Via events / warehouse

Humans separated from robots

Kipstats

Yes

PostHog

AI assistants as a channel

Kipstats

Yes

PostHog

Analytics retention

Kipstats

No limit today

PostHog

1 year free, 7 years paid

Support on the free plan

Kipstats

PostHog

Community

Self-hosting

Kipstats

PostHog

Unsupported, no paid features

	Kipstats	PostHog
Free tier	1 site, 10K pageviews/month	1M events/month, 1 project
Paid from	9€/month	Pay as you go, ~$50 for the 2nd million events
Script, gzipped	4.2 KB	~95 KB
Cookies by default	None	Yes, 1 year
Cookieless mode	Always	Yes, drops identify() and alias()
EU hosting	✓	EU Cloud (Frankfurt), chosen at signup
Session replay	—	✓
Feature flags & A/B tests	—	✓
Surveys, error tracking, warehouse	—	✓
Rage clicks, dead clicks, JS errors	✓	Via session replay
Revenue from your server	✓	Via events / warehouse
Humans separated from robots	✓	✗
AI assistants as a channel	✓	✗
Analytics retention	No limit today	1 year free, 7 years paid
Support on the free plan	Email	Community
Self-hosting	—	Unsupported, no paid features

PostHog figures read on its own pricing and documentation pages, September 2026. Prices move — check theirs before deciding.

What actually separates them

1. 95 KB against 4.2 KB

Measured on their CDN in September 2026, array.js is about 305 KB raw and 95 KB gzipped; a slim bundle exists and is marked experimental. Kipstats serves 11.5 KB raw, 4.2 KB gzipped. On a marketing page judged by its Largest Contentful Paint, that difference is not theoretical.

2. A cookie by default, and what removing it costs

PostHog persists in localStorage+cookie by default, with a one-year cookie, and its own GDPR page says you should use a cookie banner in that case. A cookieless mode exists — and it drops identify() and alias(), which is most of what makes PostHog PostHog. Kipstats has nothing to configure: no cookie, no identity, no banner.

3. What each one shows you on a Monday morning

PostHog answers "how does this feature behave for this cohort". Kipstats answers "where did this week's visitors get stuck, what did they buy, and was any of it a robot" — rage clicks and dead clicks captured with no instrumentation, purchases pushed from your payment webhook, humans separated from declared crawlers.

Where PostHog is simply ahead

Session replay, feature flags, A/B testing, surveys, error tracking, SQL on your own data, a warehouse, SDKs for every platform, HIPAA. Kipstats has none of them and is not on that road. PostHog's free tier — a million events, 5,000 replays a month — is also more generous than ours in raw volume.

Which one is for you

Pick Kipstats if…

The thing you measure is a website, and its job is to convert.
A 95 KB analytics bundle on a landing page is not acceptable to you.
You want no cookie and no banner, without losing half the product.
You want a sale recorded from your payment webhook, in one call.

Stay on PostHog if…

You need session replay, feature flags, experiments or surveys.
You are instrumenting a product behind a login, not a public site.
You want SQL over your own event data, or a warehouse.
A million events a month for free is the number that decides it.

Questions

Is PostHog free?

Up to a million events a month, one project, community support. Beyond that it is pay-as-you-go per product; the second million events costs about $50 at the published rates. Add-ons for teams and scale are flat monthly fees.

Does PostHog require a cookie banner?

By default it stores an identifier in a cookie for a year, and its own GDPR documentation tells you to use a banner in that case. Its cookieless mode avoids it, at the cost of identify() and alias().

Can I use both?

Yes, and it is a common split: PostHog inside the app, Kipstats on the public site where weight and consent matter most.

Does Kipstats do session replay?

No, deliberately. Replays record what a person did on your pages, which is exactly the data that turns an analytics tool into a privacy problem. We record aggregate friction signals instead: rage clicks, dead clicks, abandoned fields, JS errors.

Keep PostHog for the product, use Kipstats for the site

Plenty of teams do exactly that: the heavy SDK behind the login, the 4.2 KB script on the public pages.

Start for free