You can use PostHog for free. As in beer and as in speech. Also free as in every product, on every plan, resetting every month. No limit on monthly tracked users. 1M events. 5k session replays. 1M feature flag requests. More than that too: we have a graphic!
Get the answers you need from PostHog in Slack, and set your status to "🚌 Commuting" until EOD
And now, Google Analytics. Somebody requested this 5 minutes before it was released, so happy Friday to them in particular.
Session Replay's useful, they said. Only one problem: too many recordings to see, see? So this old gumshoe figured out the solution. Replay Vision, I call it. Watches your Session Replays for ya. Then pipes up with useful info. Now hop in the open beta waitlist or hop outta the squad car, toots.
Finally, the Discord feedback scout reads conversations in our PostHog Code community and routes signals into fixes. It found that our AI coding agent was still prompting for permissions in auto mode after a Claude SDK change.
Very meta is a skill scout which watches our own AI agent skills and files reports when it finds broken steps. It found broken link generation in an AI observability skill and crashes caused by type mismatches.
The bot detection scout watches web analytics logs for crawlers hitting our website and not being classified as bots. It found 37 self-declared crawlers slipping through, including one with 6,000+ requests per week, all showing up as regular traffic.
Our MCP feedback scout uses PostHog's MCP like an engineer would and files bugs it finds. It found execute-sql returns empty when a query exceeds budget, query-funnel silently shifts dates due to ISO midnight coercion, and a LLM traces tool missed a required field causing query failure.
Next, we have product-specific scouts like the AI observability one, which looks at LLM trace costs, latency spikes, and model error rates. It found that session summaries were silently failing when an old, hardcoded OpenAI model wasn't available.
The first is our general scout, which explores cross-product correlations and under-visited surfaces across the entire product. It found that insights with formulas could add up every day and silently exceed 100%.
Jina asked, our devs delivered: here's how to stop being the code review bottleneck go.posthog.com/GtAgVCH
We quintupled our conversion and doubled activation with our 🪄wizard🪄 That was after the first version of the 🪄wizard🪄 kinda sucked We learned 6 big lessons from it. Mainly, context is the most important thing. The rest, Edwin wrote about in detail: newsletter.posthog.com/p/we-used-a...
Our Context Warehouse team has been working overtime connecting, well, everything to PostHog. And by the time we published this graphic, they've probably added a dozen more. Your product being self-driving just became a lot easier.
Here the crier's voice grows hoarse and the parchment unrolls clean past mine knees, so for the remainder I shall recommend thy just go to the changelog. So let it be declared: PostHog hath shipped, and shipped well, this June of 2026. Go forth and build. Oyez!
Gee, you sure hit your head hard. Don't worry, you're in safe hands. You must have passed out from exhaustion, having to watch all of your Session Replay recordings one by one. Don't worry. While you've been recovering, our cracked team of 𝖽̶𝖾̶𝗏̶𝗌̶ doctors created Replay Vision.
Someone typing "po" into your search bar's always stressful. Almost as stressful as watching a join keep spinning.
This entire campaign was an excuse to put Max the hedgehog on a stripper pole. Mission accomplished. We did it, team.
Cross-breeding with a duck sounds pretty disgusting, but we swiped right anyways. Managed Warehouse is switching from ClickHouse to DuckDB.
PostHog engineers have fixed 508 papercuts since February 𝘰𝘯 𝘵𝘰𝘱 𝘰𝘧 𝘯𝘰𝘳𝘮𝘢𝘭 𝘸𝘰𝘳𝘬 and p95 for insights has been cut by more than 50%. More (papercut fixes, probably) at 11.