PostHog Pricing Calculator
Use this estimator to model your expected PostHog Cloud spend. You can adjust usage and rates to match your contract or current public pricing.
Disclaimer: This is an independent planning calculator, not an official quote. Taxes, regional charges, enterprise minimums, and negotiated discounts are not included unless you add them via platform fee or rate adjustments.
Why teams use a PostHog pricing calculator
PostHog is a powerful product analytics stack, but usage can scale fast. A single growth experiment can double event volume, and replay-heavy debugging can push costs up quickly. A pricing calculator helps you answer practical budget questions before surprises happen on your invoice.
For founders, product managers, and engineering leaders, cost modeling is often part of launch readiness. If you know your expected events per user, replay sampling rate, and feature flag traffic, you can forecast spend with enough confidence to make roadmap decisions.
How this calculator works
This page estimates monthly and annual costs across four common PostHog workloads:
- Product Analytics events (capture calls, pageviews, custom events)
- Session Replay recordings (recorded user sessions)
- Feature Flag requests (flag evaluations from client or server)
- Warehouse exports (rows synced to your data warehouse)
Each category follows the same formula:
- Billable units = max(0, usage − free tier)
- Cost = billable units × rate
- Total monthly = sum of all category costs + fixed platform fee
If annual billing discount is selected, the calculator applies a 10% reduction to the monthly estimate and then multiplies by 12 for annual total.
Why the rates are editable
Pricing can change over time, and your organization may have custom terms. Editable rate fields make this calculator future-proof: instead of hard-coding assumptions, you can match today’s official pricing page or your specific contract in under a minute.
Example planning scenarios
1) Early-stage SaaS
A startup with ~15k MAU may sit inside free tiers for analytics but exceed replay limits during onboarding optimization. In this case, the major cost driver is usually session replay. Reducing replay capture percentage can dramatically lower spend while preserving insight quality.
2) Growth-stage B2B product
At 50k–150k MAU, analytics events often become the biggest line item. Teams frequently instrument heavily (clicks, views, form interactions, backend events), and over-instrumentation can create noisy dashboards and unnecessary cost. A clean tracking plan can improve data quality and reduce billable volume at the same time.
3) Consumer app with high request volume
Consumer products may generate massive feature-flag traffic due to mobile app startups, frequent UI checks, and API request fan-out. Even at low per-unit rates, very high volume creates meaningful cost. Caching flag evaluations and reducing duplicate checks can help.
Practical cost optimization tips
- Create an event taxonomy: standardize naming and remove duplicates before they reach production.
- Sample replay strategically: capture 100% only for critical flows and lower sample rates elsewhere.
- Filter noisy events: skip low-value heartbeat or debug events unless needed for a specific analysis.
- Review flag evaluation patterns: avoid repeated client-side evaluations when server-side caching can do the job.
- Set monthly budget guardrails: monitor trend lines by feature release, not just by calendar month.
Common forecasting mistakes
Ignoring growth curves
Teams often budget based on current usage and forget launch effects, new market expansion, or improved activation. A realistic model should include at least low, expected, and high-volume scenarios.
Forgetting instrumentation changes
A new analytics event can multiply volume if fired in a loop or on every render. Add analytics review to your release checklist so tracking updates get cost-reviewed before shipping.
Using only monthly totals
Monthly totals hide spikes. If you have campaigns or seasonality, peak days can reveal architecture issues and budget risk. Track daily rates and tie them back to product releases.
FAQ
Is this an official PostHog quote?
No. This is an independent estimator for planning and budgeting.
Can I use this for enterprise plans?
Yes, as a baseline. Enter your contract rates and any committed platform fee. Keep in mind that enterprise support, legal terms, and additional services may be billed separately.
Should I estimate with or without free tiers?
Both. First, model with free tiers to reflect current spend. Then model a no-free-tier scenario to understand future “steady-state” cost once your product scales.
Bottom line
A PostHog pricing calculator gives you a fast, practical way to turn product usage into clear budget numbers. Use it before major launches, revisit it after instrumentation changes, and share the forecast with product, engineering, and finance so everyone has the same cost expectations.