PostHog vs Hex
Side-by-side trajectory, velocity, and editorial themes.
PostHog is wiring itself into the MCP ecosystem while shoring up mobile-SDK feature parity.
PostHog continues its weekly grind, but the May releases cluster around two themes: an MCP toolchain (alerts to Slack and webhooks, SDK Doctor, mode selection via header) and LLM analytics BYOK providers (Together AI, Azure OpenAI). At the same time the mobile teams are filling in iOS and Android session-replay controls, rage-click detection, and survey delays that previously only the web SDK had.
The shape of PostHog's surface keeps widening rather than deepening: more LLM-vendor coverage in the analytics product, more MCP-tooling so AI agents can read and act on PostHog data, more parity across SDKs. Less obvious is which surface becomes the headliner; right now Conversations, Logs, Experiments, and Client Libraries are all shipping into a single weekly digest with comparable weight.
Expect MCP integration to keep expanding from peripheral utilities into the core insights and alerting paths, with PostHog positioning itself as the analytics endpoint AI agents read from when reasoning about product usage. Mobile SDK parity work should compress in the next month or two as the gap with the web SDK closes.
Hex is reframing the notebook as a prompt-driven app builder and an agent that reaches into your stack.
Hex started as a collaborative data notebook and is now rebuilding around its AI agent. The recent stream is dominated by generative capabilities: building data apps from a prompt, agent context drawn from repos and connected systems, and agentic visualization. The classic notebook is still there, but the headline surface is increasingly 'describe what you want' rather than 'write the cells.'
Two reinforcing moves define the direction. Hex is turning analytics artifacts into things you generate from natural language, and it is wiring its agent into the surrounding toolchain as an MCP client and through external surfaces. The bet is that the unit of work shifts from notebooks people author to apps and answers the agent assembles, with humans steering context and review.
Expect Hex to keep expanding what the agent can build and where it can pull context from, pushing generative data apps from a feature toward the default way work starts.
See more alternatives to PostHog →
See more alternatives to Hex →