A 0–3 score across the 8 moats, anchored to comparable companies. It surfaces where PostHog's defensibility is real, where it's thin, and where the story outruns the structure.
PostHog scores 8 out of 24, with two moats at 2 or higher: Workflow and Distribution. Both are real. Instrumentation that lives in a customer's codebase across analytics, replay, flags and experiments is genuinely painful to remove, and a word-of-mouth engine that brought in 500,000+ teams without a paid-ads habit is rare in developer tools. What PostHog does not yet have is a third wall. The data it collects stays inside each customer's project for now, and its bet on training models across customers is months old and unproven. Few companies build a business on top of it, and its size is spent on low prices rather than turned into pricing power. That lands it below the three-moat stack threshold, despite one of the strongest growth curves in the category.
PostHog's homepage leads with "Your product's context layer," and the story around it is the self-driving product: scouts that watch your product around the clock, file reports to an inbox, and open pull requests. The implied moat is that PostHog holds the context and owns the agents that act on it. Structurally, that context still mostly sharpens each customer's own view, PostHog's plan to train models across customers is only months old, and the agent layer on top is the part every coding agent and observability vendor is racing to ship. PostHog even opens its data to those same outside agents over MCP. The walls actually holding are the quieter ones: code-level instrumentation across a dozen products, and a distribution engine built on brand and word of mouth.
Each moat is scored 0–3 for structural durability — not for how useful or popular it is. The tier is set by how many moats reach 2+, not by the total.
| Moat | Meter | Score | One-line take | |
|---|---|---|---|---|
| 01 | Data | 1 | Per-project today. A deliberate bet on cross-customer training is underway. | |
| 02 | Workflow | 2 | Flags, experiments and events live in the codebase. Real, but bundleable. | |
| 03 | Regulatory | 0 | Standard compliance kit. Cost of entry, not a barrier. | |
| 04 | Distribution | 2 | Owned reach, built on purpose. Best in category, still contested. | |
| 05 | Ecosystem | 1 | Integrates widely, but few build businesses on it. | |
| 06 | Network Effects | 1 | Team value inside one project. No cross-customer pull. | |
| 07 | Physical / Infra. | 0 | Software on rented cloud. | |
| 08 | Scale | 1 | Fast-growing leader by adoption. The pricing gives the leverage away. | |
| Total | 8 / 24 |
The tier is set by counting how many moats score 2 or higher — not by the total out of 24. One strong moat isn't a stack.
| Exposed | 0 moats at 2+ | No defenses; open to attack from every direction. |
| Partial← This company | 1–2 moats at 2+ | Some defense, but below the stack threshold. |
| Stacked | 3 moats at 2+ | Stack threshold met; defensibility begins here. |
| Fortified | 4+ moats at 2+ | Multiple moats compound; the strongest state. |
PostHog has 2 moats at 2+, which lands it in Partial.
Scores are anchored against comparable companies in the same category — not isolated opinion.
PostHog captures events, replays, errors, logs and warehouse syncs from 900+ sources. Until mid-2026 that data only sharpened each customer's own view. In May, PostHog announced it would train its own models on anonymized customer data, starting with features like automated session replay analysis. US cloud customers are opted in by default; EU cloud customers and those with agreements that prevent training are opted out. That is a deliberate bet on a cross-customer Data moat, but the public evidence doesn't yet show it working, so it stays a 1, alongside Amplitude and Mixpanel. A 2 would need learning across customers to produce a measurable improvement a competitor would struggle to match. Gong's conversation corpus is what a 3 looks like.
PostHog's SDK sits in the customer's code, feature flags gate releases, and experiments run on its event stream. PostHog's own handbook says its happiest and best-retained users, including on revenue retention, are the ones who adopt two or more products. Leaving means recreating release flags, experiment definitions and the events used to measure results, and losing the history behind them. It stops short of 3 because PostHog is not a system of record in the Salesforce sense: the base skews toward startups, most of it on free tiers, and each product can be swapped out one at a time. LaunchDarkly holds a similar 2 on flags alone, and Calendly is the standing 2 anchor for embedded but bundleable.
PostHog offers the compliance kit a serious analytics vendor needs, including EU hosting and an open-source core for teams that want data on their own infrastructure. None of it is a license competitors can't obtain: Amplitude, Mixpanel and Datadog clear the same bar. Like Attio and HubSpot in the GTM set, this is table stakes. A 2 would require a structural legal barrier, which horizontal product tooling rarely has.
PostHog built its reach deliberately. Its handbook makes word of mouth the default over paid ads and PR, and its Product for Engineers newsletter is a channel it owns outright. A free tier that 98% of customers never leave feeds a self-serve funnel: 41% of revenue runs through checkout inside the product. Account managers then cross-sell from a documented playbook. That is owned reach in the HubSpot inbound sense, which scores 2. It isn't a 3 because the channel is brand-bound and contested: Vercel and Supabase run similar developer-brand plays, and a generous free tier can be matched by anyone willing to spend margin.
PostHog pulls from 900+ data sources, pushes to destinations through its CDP, ships an MCP server, and has an open-source core with community-built apps. Partners like Unify have built connectors that route PostHog signals into sales plays. But the dependency runs mostly one way: PostHog plugs into others' stacks rather than being the platform others structure their products and revenue around. Calendly scores 1 here for the same reason; Notion's template economy earns a 2, and Stripe Connect is the 3. A 2 would need a real market of builders whose revenue depends on PostHog.
Notebooks, shared dashboards and an inbox of agent reports make PostHog more useful as more of a team uses it, but that value stays inside the account. One more company adopting PostHog doesn't improve it for the next. The open-source community and public roadmap voting shape the product, but they aren't a network effect. Attio and HubSpot score 1 for the same within-account effect; G2 and LinkedIn are the cross-customer 3s that almost nothing in SaaS reaches.
PostHog runs its ClickHouse-based ingestion and warehouse on public cloud, and has sunset support for self-hosted Kubernetes deployments. That is serious engineering, but competitors can rent the same infrastructure. Every product analytics vendor, from Amplitude to Mixpanel, sits at 0 here. This isn't a weakness; the moat simply doesn't fit the model.
With roughly $58M in ARR in early 2026 by Sacra's estimate, more than doubling year over year, and 500,000+ teams, PostHog leads its segment on adoption. But it uses that size to price low and keep free tiers generous, which competes margin away to win share rather than showing pricing power. Apollo sits at 1 for the same pattern. Amplitude, at several times PostHog's revenue, and Datadog above it, mean bigger players can still cross-subsidize. A 2 would need size that visibly lowers unit cost or supports higher prices than smaller rivals can match.
Not every moat fits every business. Three buckets narrow the field — they don't name which available moat to pursue. That's the Playbook's job.
PostHog has two real moats, and they are the ones it talks about least: code-level instrumentation and a word-of-mouth engine. What it does not yet have is a stack. The Defensibility Stress Test pressure-tests each of these scores, runs PostHog head-to-head against 3 to 5 players across product analytics, observability and AI coding agents, and identifies which available moats could carry it past the three-moat threshold. From there, the Stacking Moats Playbook takes over: matching the stack to a durable archetype and naming the missing leg.
Plus a head-to-head competitive analysis against 3 to 5 players in PostHog's field.
The rigorous follow-on to this scorecard, run on your own company with the full methodology visible.
Thanks — your scorecard and a short email series are on the way, and I'll be in touch within one business day. If you want the rigorous version, the discovery call on the left is the fastest way to start.