Tools· Data, Analytics & Finance

    PostHog

    PostHog is a product analytics platform that combines events, feature flags, session replay, experiments and error tracking through a shared event model, priced on usage with a generous free allowance.

    executabledata-drivenanalyticalOpen Source

    Description

    Strengths

    Shared event model
    Analytics, session replay, feature flags, experiments and error tracking run on the same data foundation, so you can jump from any evaluation point straight into the matching session recording.
    Context warehouse with external sources
    A data warehouse combines data from more than 120 external sources such as Stripe, Postgres or HubSpot with insights from PostHog's other tools, queryable through a SQL editor.
    Autocapture without extra code
    On the web, pageviews, clicks and form submissions are captured automatically; mobile apps or backend events need an SDK.
    Access across multiple surfaces
    Besides the browser, a shared Slack channel, a terminal CLI and editor integration through MCP are available.
    Generous free allowance
    According to the provider, 98 percent of customers use PostHog within the free limits, and sign-up requires no credit card.

    Assessment

    AI features

    • PostHog MCP A Model Context Protocol server connects PostHog to MCP-compatible clients such as Claude Code, Cursor or VS Code. According to the provider, connected agents can run analytics queries, feature flag and experiment management, SQL queries, CDP destinations and support ticket triage.
    • Queries directly from the editor Trends, funnels, retention and usage metrics can be queried from Cursor, Claude Code, VS Code or any other MCP-compatible agent without leaving the editor.
    • PostHog AI An AI chat built into the platform answers product questions, builds insights and writes SQL queries. According to the provider, it draws on the product, documentation, community discussions, the codebase and GitHub issues.
    • Installation by prompt According to the provider, setting up an SDK can be handed off to an AI coding assistant with a single prompt, which then runs the installation in the terminal or editor.

    Suitable for

    • Product teams that want to run analytics, feature flags, session replay and experiments in one tool instead of several point solutions
    • Engineering-oriented teams that value an API-first approach and optional self-hosting
    • Organizations with irregular or growing traffic that benefit from automatic volume discounts
    • Less suitable for Less suited to pure marketing analytics without real product events; classic web analytics tools are a better fit there

    Limitations and notes

    • MCP use partly billable According to the provider, connecting to the MCP server and calling its tools is free, but some tools use LLMs internally and are then billed as PostHog AI spend.
    • Usage-based costs Events are billed based on volume and on whether custom user properties are sent with them. Without steady traffic, monthly costs are harder to predict than with a fixed seat-based model.
    • Data retention tied to the plan According to the provider, the free plan retains data for one year, the paid plan for seven years.
    • Tiered support The free plan offers support through the community forum; direct email and Slack-based support, according to the provider, only start once monthly spend passes 2,000 US dollars.

    Quick start

    1. Create a free account at posthog.com, according to the provider with no credit card required.
    2. Set up the SDK for your application, or hand the installation off to an AI coding assistant with a prompt; supported stacks include, according to the provider, Next.js, React and Python.
    3. If needed, connect the PostHog MCP server to run analytics queries, feature flags and experiments directly from Claude Code, Cursor or VS Code.
    4. Check autocapture: on the web, pageviews, clicks and form submissions are captured automatically, and custom events and user identification can be added.

    Tips

    • Set billing limits per product so usage-based costs stay within your own expectations.
    • Use the MCP server for recurring analytics questions instead of switching to the browser for every query.
    • Distinguish between anonymous and identified events in your tracking design, since the two are billed differently.
    • Jump from a funnel step or a metric straight into the matching session replay recording to understand the "why" behind a number.

    Access

    Last reviewed: · Pricing, plans and features are a snapshot in time. Check the provider's own page before deciding.

    In the workshop this becomes your method.

    Whoever sees this process run once wants the agent behind it next. We build that in the workshop From Process to Agent.

    View workshops

    Related resources

    Browse all resources

    Conversation, not pitch

    Understand first, then decide. We take time for an initial conversation, without sales pressure, without obligation.

    Schedule a call