PostHog Pricing: A Practical Guide for MVP Teams

Most MVP teams researching product analytics eventually run into the same name: PostHog. It shows up in “best analytics tools” roundups, in Show HN threads, and in startup Slack channels as the tool that seems to do everything — event tracking, funnels, session replay, feature flags, A/B testing — under one roof. The appeal is obvious. The pricing model is where most founders get stuck.

This guide walks through how PostHog’s pricing actually works, what it’s genuinely good at for an MVP, and how it compares to lighter tools like Plausible and Fathom — which, worth saying up front, aren’t really solving the same problem.

What PostHog Actually Is

PostHog is an open-source, self-hostable product analytics platform. Unlike a simple page-view tracker, it’s built around the idea that one platform should cover the full loop of building and iterating on a product: capturing events, understanding user behavior, watching what actually happened on screen, and testing changes against real users.

In practice, that means PostHog bundles several tools that MVP teams would otherwise stitch together separately:

• Product analytics — custom event tracking, funnels, retention curves, user paths.
• Session replay — recordings of real user sessions, similar in spirit to what a dedicated tool like LogRocket offers.
• Feature flags — toggling features on and off, or for specific user segments, without a redeploy.
• A/B testing / experiments — running controlled tests on top of those feature flags.
• Surveys — lightweight in-app feedback collection.

For a two-or-three-person MVP team, the pitch is straightforward: one integration, one dashboard, one vendor relationship, instead of separately wiring up an analytics tool, a replay tool, and a feature-flagging service.

How PostHog Pricing Actually Works

The part that trips people up is that PostHog doesn’t charge a single flat monthly fee. It prices per product, based on usage — think events tracked, session recordings captured, feature flag requests served, and so on — each with its own free monthly allowance before usage-based charges kick in.

This structure has real implications for an MVP:

• It can be genuinely free at low volume. A brand-new MVP with a few hundred users and modest event volume can often stay within PostHog’s free monthly allowances across the products it actually uses.
• Cost scales with usage, not a fixed tier. Unlike a flat “$X/month” plan, your bill grows (or shrinks) with actual traffic. This is friendlier for pre-launch products but requires more active monitoring once you have real growth — a viral spike in event volume shows up as a bill, not just a dashboard number.
• You only pay for what you use. If your MVP only needs core analytics and skips session replay and feature flags entirely, you’re not paying for capacity you don’t use — a difference from bundled, all-inclusive platform pricing.

Because PostHog’s pricing tiers and free allowances are usage-based and can change, this guide won’t quote specific dollar figures or allowance numbers — check PostHog’s own pricing page directly for current details before budgeting, since publishing a specific number here risks going stale the moment PostHog adjusts a tier.

The practical takeaway for an MVP team: model your expected event volume, recording volume, and flag usage before committing, rather than assuming a number from a blog post or a competitor comparison will still be accurate by the time you sign up.

PostHog vs. Plausible vs. Fathom: Different Categories, Not Direct Competitors

This comparison gets searched a lot, but it’s worth being honest about what’s actually being compared. PostHog is a full product analytics platform. Plausible and Fathom are lightweight, privacy-first page-view analytics tools — a narrower category focused on simple, cookieless website traffic reporting.

	PostHog	Plausible / Fathom
What it covers	Event tracking, funnels, retention, session replay, feature flags, experiments, surveys	Page views, referrers, basic on-site events — simple website traffic analytics
Hosting model	Cloud (usage-based pricing) or self-hosted (open source)	Cloud-hosted (flat subscription); Plausible also offers self-hosting
Setup complexity	Moderate — event schema, more configuration surface	Low — script tag, minimal setup
Best for	Teams that need to understand in-product behavior: funnels, feature adoption, user sessions	Teams that just want to know where traffic comes from and which pages get read

If your MVP’s real question is “which marketing pages are working and where does traffic come from,” Plausible or Fathom answers that with far less setup and a predictable flat fee. If your real question is “where in the product do users get stuck, and which features actually get used,” that’s a product analytics question PostHog is built for and Plausible/Fathom simply aren’t designed to answer. Choosing between them isn’t really a feature comparison — it’s picking the right category for the question you’re asking. For a broader framework on making that first call, Choosing Analytics Tools for Your MVP covers how to decide what to track before picking any specific tool.

When PostHog Is Worth It for an MVP

PostHog earns its complexity when an MVP genuinely needs more than page-view counts:

• You need funnels across a multi-step product flow. Signup → onboarding → first core action → return visit is the kind of funnel a page-view tool can’t construct, but PostHog’s event-based model handles natively.
• You want session replay without adding a second vendor. If you’re already leaning toward needing session replay — covered in more depth in Session Replay Tools for Your MVP — PostHog’s built-in replay can cover that need without a separate LogRocket or Hotjar subscription.
• You want to ship features behind flags. Feature flags let you release a risky change to 5% of users, or gate a feature by plan tier, without a full redeploy cycle — useful once you have real users you don’t want to disrupt.
• Data residency or self-hosting matters to you. Because PostHog is open source, teams with strict compliance requirements, or simply a preference for owning their data pipeline, can self-host instead of using PostHog Cloud.

When It’s More Than an MVP Needs

Not every early-stage product needs this much platform. A few signs PostHog is premature:

• You only need to know where website traffic comes from — that’s Plausible or Fathom’s job, done more simply.
• You don’t yet have enough usage to generate a meaningful funnel or retention curve — the extra configuration buys you very little until there’s real volume flowing through it.
• Nobody on the team has time to actually configure event schemas, review session recordings, or run experiments — an underused platform is wasted setup time regardless of how capable it is.

If you’re still deciding what to track before picking a tool at all, that earlier decision is worth making first — see the analytics-tools guide linked above for a framework that applies whether you land on PostHog, a lighter tool, or something in between.

Getting Started Without Overcommitting

A reasonable way to trial PostHog on an MVP: start on the free tier with PostHog Cloud (skip self-hosting until you have a specific reason to manage that infrastructure yourself), instrument only the handful of events tied to activation and core usage, and turn on session replay or feature flags only once you have a concrete use for them. This keeps the setup proportional to an MVP’s actual stage, while leaving the option open to lean into PostHog’s deeper features — funnels, experiments, flags — once real usage gives you a specific question to answer.

Frequently Asked Questions

Is PostHog free to use for an MVP?

PostHog offers a free tier with monthly usage allowances across its products (events, recordings, feature flag requests, and more), which is often enough for an early MVP with modest traffic. Costs become usage-based once you exceed those free allowances, so the actual bill depends on your volume rather than a flat subscription fee.

How is PostHog priced compared to a flat-fee analytics tool?

PostHog uses usage-based pricing per product (analytics events, session replays, feature flag calls, and so on), rather than a single flat monthly fee. This means costs can scale up as usage grows, which is worth modeling against your expected volume rather than assuming a fixed price will apply indefinitely.

Should an MVP choose PostHog or Plausible/Fathom?

It depends on what you need. PostHog fits teams that want event tracking, funnels, session replay, and feature flags in one platform. Plausible or Fathom fit teams that just want simple, privacy-first page-view analytics without the added complexity — they are not really solving the same problem, so the choice comes down to how deep your tracking needs actually are.

Can PostHog be self-hosted?

Yes. PostHog is open source and can be self-hosted, which appeals to teams with strict data-residency or compliance requirements, or teams who want to avoid usage-based cloud billing entirely. Self-hosting adds its own operational overhead — server management, upgrades, scaling — so it's a trade of engineering time for infrastructure control, not a free option.

Does PostHog replace the need for a separate session replay tool?

For many MVPs, yes — PostHog bundles session replay alongside its analytics, so you don't need to run a separate tool like LogRocket or Hotjar just to watch user sessions. Teams with heavier frontend error-monitoring needs may still find a dedicated tool's error tracking more mature, but for basic replay, PostHog's built-in version is often sufficient.