PostHog Pricing in 2026: What You Actually Pay

As of July 2026, PostHog has no monthly subscription and no seat pricing. It is free to start, needs no credit card, and each of its products meters independently once you cross a generous free allowance. That design is why the same tool shows up in one Reddit thread as "basically free" and in the next as a "$60k/month" bill. Both are true. The difference is almost never the plan; it is how many events you send, whether they are identified, and whether you set a billing limit.

PostHog is a usage-based product analytics platform that bundles analytics, session replay, feature flags, experiments, surveys, error tracking, and a data warehouse under one $0 base. This is the arithmetic the pricing page and the third-party summaries leave out: the per-product free tiers, the identified-event multiplier, and three real 30-day bills you can map onto your own traffic.

How PostHog pricing works in 2026

There are two plans: a Free plan and a Pay-as-you-go plan that also starts at $0/month. Neither has a fixed fee. You are billed per product, per unit, and only after that product's free tier is used up. From PostHog's own pricing page (July 2026), the monthly free allowances are:

Two things fall out of this table that single-number teardowns miss.

First, the free tiers stack. Because each product has its own allowance, a small app can run analytics, replay, flags, surveys, and error tracking all at once and still pay nothing. Tools that meter on monthly tracked users (MTUs), like Mixpanel or Amplitude, bill against one shared meter, so the same activity lands on a single growing line. PostHog's split meters are genuinely friendlier at the bottom.

Second, the price is marginal and tiered. Product analytics does not cost a flat $0.00005 forever. The rate steps down as volume rises:

So the second million events costs $50, but the fifteenth million costs $34.30, and beyond 250M events you are paying $9 per million. Effective cost per event drops the more you send.

The identified-event trap that quietly quadruples your bill

Here is the single biggest lever, and it is buried in the docs rather than the pricing page. PostHog charges more for identified events than anonymous ones. From PostHog's anonymous vs identified events documentation (2026): "Anonymous events can be up to 4x cheaper than identified ones."

An event becomes identified the moment your code calls identify(), alias(), group(), or setPersonProperties(). After that, PostHog builds a person profile and every subsequent event for that user is billed at the identified rate. Call identify() on every pageview and your $0.00005 events can quietly bill at up to four times that.

The fix is a one-line config, not a plan change. PostHog's recommended default is person_profiles: 'identified_only', which captures anonymous events by default and only creates a person profile when you explicitly identify someone (a signup, a login). In backend SDKs, setting $process_person_profile: false keeps high-volume server events anonymous. Most teams do not need a person profile on a marketing pageview; they need it on the ten events after login.

Math check preview: on a 5M-event month, the analytics line is about $153 if those events are anonymous, and up to roughly $610 if every one is identified. Same traffic, same product, 4x the bill, decided by one SDK flag.

Three real 30-day PostHog bills

Numbers below use the July 2026 rates above, anonymous events unless noted, and add up the products a typical team actually turns on.

Bill 1: the side project, $0

800,000 analytics events, 3,000 web session replays, 300,000 feature-flag requests, and 40,000 error-tracking exceptions. Every figure sits under its free tier (1M / 5K / 1M / 100K).

Total: $0.00/month. This is the "too good to be true" thread on r/nextjs. It is real, as long as you stay under the allowances.

Bill 2: the growing B2B SaaS, about $370

5M analytics events (anonymous), 12,000 web replays, 3M feature-flag requests, 200,000 error-tracking exceptions.

Two lessons here. Feature flags are the surprise line: the first paid million of flag requests costs $100, more than the first three million analytics events. If you evaluate flags locally in your backend instead of calling PostHog on every request, that line collapses. And if those 5M events were all identified, the analytics line alone climbs from $152.90 toward $610, pushing the bill past $800. The config flag, not the traffic, decides which SaaS you are.

Bill 3: the high-volume consumer app, and the $60k horror story

Take 60M analytics events a month, kept anonymous with autocapture tuned, plus 50,000 web replays.

Now the cautionary tale. A product manager on r/ProductManagement reported that at 300M+ events "PostHog's cloud option, the cost went up to ~60k$ per month." That is not a different price list; it is the same tiers with three multipliers stacked: five times the event volume, every event identified (up to 4x), and autocapture firing many events per interaction with no filtering. Autocapture is convenient and it is also why the r/reactnative thread describes an "ideal spend ~$50/month" that ballooned until the author "tried disabling autocapture." Volume you never chose to send is still volume you pay for.

How to cap PostHog so you never get a surprise bill

The answer to the horror story is a feature PostHog ships and almost nobody enables: per-product billing limits. From the pricing page, "You can set billing limits for each product so you never get an unexpected bill." Set a dollar cap on analytics, another on replay, and when you hit it PostHog stops ingesting that product's data for the rest of the month rather than billing past your number. It is a hard ceiling, per product, and it turns an open-ended usage bill into a budget you control.

The other levers, in order of impact:

• Keep events anonymous by default (identified_only); identify only after signup. Up to 4x.
• Tune autocapture or switch to explicit capture() calls for the events you actually analyze. Cuts raw volume.
• Evaluate feature flags locally in the backend to avoid a request per check.
• Sample high-frequency events, and set billing limits as the backstop.

One correction for anyone reading older guides: teardowns from 2024 and early 2025 still cite a "$65/month basic plan for 5,000 sessions." That plan is gone. In 2026 PostHog is pure pay-as-you-go on a $0 base; the paid tiers you will see, Boost at $250/mo and Scale at $750/mo, buy support and security features (priority support, SAML, RBAC), not usage. Your usage is billed the same whether or not you add them.

Is PostHog cheaper than the alternatives?

Honestly, it depends on shape, not logos. For an early product juggling analytics, replay, and flags, the stacked free tiers make PostHog hard to beat, and if you only want privacy-friendly web stats, a flat tool like Plausible or free GA4 may be simpler. At high, mostly-identified volume, an MTU-priced competitor can undercut usage pricing, which is exactly why the r/analytics consensus is "PostHog is great for startups since it's cheaper" with the caveat that it scales in cost with usage. PostHog also overlaps tools you may already pay for: its error tracking competes with a dedicated monitor, so if you are pricing that separately it is worth reading our Sentry pricing teardown alongside this one, and its usage-metered model rhymes with other per-unit infra like Upstash.

Math check: PostHog's bill is set by three multipliers, not a plan. Volume x identified-vs-anonymous (up to 4x) x autocapture-noise. Set a per-product billing limit and keep events anonymous by default, and a "$60k" tool becomes a "$0 to a few hundred" tool.