Independent listing
PostHog
An engineering-focused suite for product analytics, replay, flags, experiments, and data.
Overview
PostHog is an engineering-focused product and data platform. Its product suite includes product analytics, web analytics, session replay, feature flags, experiments, surveys, error tracking, a managed warehouse, data pipelines, logs, AI observability, and workflow features. These tools share event, person, property, and data concepts so a team can move from a metric to related user behavior or release context without starting in a separate vendor.
PostHog began with open-source product analytics and still offers deployment choices, but its hosted platform now spans a much wider set of jobs. This independent listing was written by sheeplaunch; PostHog did not submit it.
Best fit
PostHog fits product-minded engineering teams that want analytics and product delivery tools close together. A startup can instrument events, inspect funnels and retention, watch session replays, release behind feature flags, run an experiment, and collect a survey without integrating a different system for each step. The generous per-product free tiers make it practical to test the workflow before a large commitment.
It is best when developers can own instrumentation quality and when the organization is comfortable with an event-based data model. Teams that want only simple traffic counts may find the platform broader than necessary.
Core capabilities
- Product analytics for trends, funnels, retention, paths, stickiness, lifecycle, SQL, dashboards, and alerts.
- Session replay, heatmaps, surveys, and user context for investigating what happened behind a metric.
- Feature flags and experiments tied to the same users, events, and properties used for analysis.
- Data warehouse, pipelines, external sources, APIs, webhooks, CDP-like activity, logs, errors, and AI observability.
- Cloud regions, SDKs across common stacks, open-source components, self-hosting options, and billing controls by product.
The integrated context is the main advantage. A funnel change can be examined alongside recordings and the flag or experiment that changed an experience, reducing manual stitching between tools.
Tradeoffs and limitations
An all-in-one platform creates a larger learning surface. Each PostHog product has its own data volume, retention, configuration, and billing meter. Teams should add capabilities when a real question requires them rather than enabling everything and creating noisy, expensive data.
Analytics quality depends on instrumentation. Autocapture provides a starting point, but meaningful funnels and retention require stable event definitions, identity handling, property governance, and privacy decisions. Session recordings and person-level data need consent, masking, access control, and retention policies appropriate to the product’s users and jurisdictions.
Self-hosting offers control but transfers upgrades, scale, backups, and incident response to the team. Cloud hosting avoids that operational load but creates vendor and data-location decisions. Using flags for critical application behavior also requires safe defaults and failure handling in every SDK integration.
Pricing approach
PostHog offers free monthly allowances separately across many products, followed by usage-based rates that decrease at larger volumes. Customers can set billing limits for individual products. This is transparent but not a single flat subscription: analytics events, replay recordings, flag requests, exceptions, warehouse rows, logs, and AI usage scale independently. Estimate the exact products to be enabled and keep cost controls active.
Related choices
Sentry goes deeper on application errors, traces, and debugging workflows. Linear manages committed product work rather than behavioral evidence. Supabase can be an application data source, but analytics event design should remain separate from transactional database design. A team may combine these products, provided user identifiers and sensitive data are governed deliberately.
How to use this profile
Treat this page as a dated starting point, not a substitute for a technical trial. Confirm the features, regional availability, limits, privacy terms, and prices that apply to your account. Test the real workflow with representative data and traffic, identify the exit path for important data, and assign an owner to review the service after the product reaches production.
Official sources
Reviewed by the sheeplaunch editorial team on 18 August 2026.