Engineering-led early-stage teams that want an all-in-one platform, or regulated/data-sovereign organizations that self-host.
Non-technical teams (configuration is code-forward) or large enterprises that need mature SSO, governance, and dedicated support (Amplitude fits better).
What is PostHog?
PostHog is an open-source all-in-one product analytics platform that bundles what traditionally required three tools: analytics (Amplitude/Mixpanel), session replay (FullStory/Hotjar), and feature flagging (LaunchDarkly). Self-hosting is free and popular with data-sovereignty-conscious teams; the managed cloud with a generous free tier has captured significant SMB share. Newer modules add error tracking and a data warehouse. Best for early-stage engineering-led teams.
Key features
Integrations
Third-party ratings
What people actually pay
No price data yet — be the first to share
No price data yet for PostHog. Help the community — share what you pay (anonymized).
The product analytics suite that ate three categories
PostHog has quietly become the default for product analytics, session replay, feature flags, and experiments in one tool. Each individual product is good enough, the bundle is undefeatable on price, and self-hosting is genuinely viable.
PostHog's strategy of consolidating product analytics, session replay, feature flags, A/B testing, and surveys into one platform sounded like a pricing gimmick three years ago. It is now the obvious play. For most product teams, the alternative is paying separately for Mixpanel or Amplitude, LogRocket or FullStory, LaunchDarkly, and Statsig — that combined bill at moderate scale is brutal, and PostHog at $0 to start with usage-based scaling beats it on every dimension except depth-of-feature in any single category.
The individual products are credible, not category-leading. Product analytics is good enough that Mixpanel users do not feel downgraded, session replay is fine, and the feature flag implementation is technically equivalent to LaunchDarkly for the use cases most teams actually have. The recent push into LLM observability and the Max AI assistant for natural-language queries are smart category extensions that match where product teams are headed.
The weaknesses match the all-in-one positioning. First, the UI complexity grows as the product surface expands; new users land on a product that does too much, and onboarding makes the wrong first impression. Second, performance on very large event volumes (50M+ events/month) on the cloud tier can degrade, and the self-host operational burden is real once you have meaningful scale. Third, each individual product has a "best in class" alternative that is sharper if you only need one thing — Statsig for experiments, LaunchDarkly for enterprise feature flags, Mixpanel for marketing-team-friendly funnels.
Buy PostHog as the default for any product team that wants analytics plus replay plus flags without three vendor relationships. Self-host if you have data residency requirements or are cost-conscious at scale. Stay on Mixpanel or Amplitude if your marketing or growth team has built their workflows there and switching cost is high — PostHog wins on bundle, not on individual analytics depth.
Product teams that want analytics, session replay, and feature flags in one tool with usage-based pricing and self-host as a real option.
Marketing-led growth teams with deep Mixpanel or Amplitude workflows, or enterprises that need a category-leader in any single sub-product.
Written by StackMatch Editorial. StackMatch editorial reviews are independent analyst commentary, not user reviews. We have no affiliate relationship with this tool. See user reviews below for community perspective.
Before you buy PostHog
Vendors don't tell you about their competitors. We do — with verdicts attached when we have them.
What PostHog actually costs
Sticker price isn't the real cost. We add implementation, training, and a probability-weighted lock-in penalty.
When to negotiate PostHog
Vendor sales pressure is non-uniform — quarter-close, year-end, and post-funding-round are your high-leverage windows.
Strong negotiation window. Reps will push for end-of-quarter signature. Don't move first — let them initiate the discount. Target 15-30% off list plus negotiated terms.
Take this to your sales call
9 questions vendor sales teams steer around — generated from PostHog's pricing tier, lock-in profile, and editorial verdict.
- 1PRICINGPostHog starts on the free tier. What forces an upgrade — specific feature gates, usage caps, or support tier? Give me the realistic monthly bill at small scale.
- 2CONTRACTAuto-renewal: how many days notice is required to terminate, and what happens if we miss the window? Will you commit to a renewal-reminder email at 90 and 60 days?
- 3MIGRATIONData export: what's the complete spec — format, frequency, and what data does the export NOT include? After contract end, how long do we have read-only access?
- 4MIGRATIONImplementation runs 1–3 weeks. Who from your team is included by default, and who do we add at additional cost? Is a CSM assigned?
- 5FITPostHog is best for: Product teams that want analytics, session replay, and feature flags in one tool with usage-based pricing and self-host as a real option.. We're [describe your situation]. Walk me through the failure modes if our profile doesn't match.
- 6FITConnect us with 2-3 reference customers at our company size in SaaS — not the case-study list, customers who've been live for 18+ months and have churned at least one tool from your stack.
- 7INTEGRATIONPostHog lists 5 integrations including Segment, Slack, Snowflake. Which of OUR existing tools — bring our list — have you confirmed shipping integration with versus "on roadmap"? Show me the actual status.
- 8VENDORTrack record over the last 18 months: any pricing model changes, executive departures, layoffs, M&A activity, or material customer churn we should know about?
- 9VENDORIf you're acquired or shut down, what's the contractual continuity — source-code escrow, data portability, transition period? Show me the actual clause.
What to actually test in the demo
Vendor sales teams script demos to maximize close rate. Here's what they'd rather you not test — derived from PostHog's lock-in profile and editorial verdict.
- 1PERFORMANCEBring YOUR data, not their demo data. Insist on running the demo workflow against a sample of your real records, files, or queries. If they refuse — that's a signal.
- 2PERFORMANCEPostHog demo will be built around the happy path. Ask: "Show me what happens when [the most common failure mode in our context]" — make them improvise.
- 3EDGE CASESPush the limits live: largest dataset, longest workflow, most users concurrent. Vendors prep demos for medium loads — your real-world usage might 10x what they show.
- 4EDGE CASESMobile and offline behavior: how does PostHog degrade on slow connections, on iPad, in airplane mode? Test in the demo if your team uses these surfaces.
- 5PRICINGFind the upgrade triggers. Which features force a paid plan? Which usage limits trigger overage? Get the rep to demo your team hitting each cap.
- 6INTEGRATIONVendors love their integration logo wall. Test the actual depth: pick the 2-3 (Segment, Slack-style) integrations you depend on most, and ask the rep to demo a real two-way data sync, not a marketing screenshot.
- 7INTEGRATIONAPI and webhook reality check: rate limits, payload size limits, retry behavior, auth refresh handling. Ask for actual API docs in the demo, not "we'll send those."
- 8MIGRATIONDemo the full data export workflow. Even with low lock-in, you want to see how clean the exit looks before signing.
- 9SUPPORTSubmit a real support ticket DURING the demo. Use the actual support channel customers use, not the rep's email. Time the response. This is your most honest data point about post-sale reality.
- 10SUPPORTAsk to be connected with a customer in the demo who you can email TODAY (not "we'll arrange a reference call next week"). The vendor's confidence in their references is a tell.
User Reviews
Be the first to review this tool