What does PostHog
cost to run?
Product analytics, replay, experimentation and data warehouse tools.
monthly recurring run cost
PostHog is modeled from its public product surface, documented architecture where available, current pricing, and the operational demands implied by its major features. The range is an editorial estimate—not a leaked invoice or a claim from PostHog.
The largest cost pressure comes from high-volume event ingestion, session replay storage, analytics queries. Build-time assumes a production product with authentication, billing, observability, security, responsive clients and the core workflow represented honestly—not a visual clone.
Infrastructure can vary dramatically with negotiated contracts, caching, region, reliability targets and customer behavior. Use the itemized receipt and assumptions to challenge the estimate. Founders can submit a correction or verify their real range without publishing sensitive vendor contracts.
How the bill grows.
Same product class, different usage. This is directional—not a pricing quote.
Where this could be wrong.
- Open-source deployment topology anchors the estimate
- Cloud customer mix and retention are not public
Public sources used.
Make this estimate better.
Founders can verify a range or correct an assumption without exposing confidential vendor contracts.