Segment vs PostHog
This is not a like-for-like comparison, and pretending otherwise is how teams pick wrong. Segment is a dedicated customer data platform: collect once, fan out to 700+ tools. PostHog is a product analytics platform — dashboards, funnels, session replay, feature flags — that grew a data pipeline alongside them. The question isn't which is better, it's which half of Segment you actually use.
Pick PostHog if you also pay for a separate analytics tool, if 1M events/mo free beats Segment's 1,000 MTUs by an order of magnitude in your case, or if you want analytics, replay, flags and the pipeline behind one MIT-licensed platform. Stay on Segment if the CDP is your marketing team's activation layer — identity resolution, audiences and the long tail of ad destinations are where PostHog's pipeline stops. Many teams end up running PostHog for product analytics and a Segment-shaped pipeline like RudderStack for fan-out.
Side by side
Segment vs PostHog at a glance
| Twilio Segment | PostHog | |
|---|---|---|
| What it is | Dedicated CDP | Product analytics platform + CDP pipelines |
| Billing unit | MTU — monthly tracked users | events |
| Free tier | 1,000 MTU · 2 sources | 1M events/mo · 5K replays · 1M flag requests |
| Pipeline cost | $120/mo Team (10,000 MTU) | $0.000062/event · transformations free |
| Destinations | 700+ | a focused set + webhooks/batch export |
| Managed sources | unlimited from Team | 20+ (Stripe, HubSpot, Salesforce, Snowflake, BigQuery…) |
| Analytics included | ✗ send it to a tool | ✓ dashboards, funnels, replay, flags, A/B |
| Identity resolution | Unify (Business tier) | basic person merging |
| Audiences / activation | Engage Foundations | ✗ not a marketing CDP |
| Self-host | ✗ not possible | ✓ MIT · no commercial support |
| Best for | Marketing activation, widest catalog | Product teams, biggest free tier, one platform |
Sources: Segment pricing · PostHog pricing · PostHog CDP docs · PostHog licence. Compiled July 2026.
Where PostHog wins
The free tier isn't a demo
1 million events a month, every month, plus 5,000 session replays, 1 million feature-flag requests and 100,000 exception events. Segment's free plan is 1,000 MTUs and two sources — a web app with an iOS and Android client has already run out of sources before it sends anything. For a startup or a side project, that gap decides the evaluation on its own.
One platform instead of four bills
The honest comparison isn't Segment against PostHog; it's Segment plus your analytics tool plus your replay tool plus your flag service, against PostHog. Teams that migrate usually aren't chasing a cheaper CDP — they're collapsing a stack. Transformations being free with no volume limit also removes the "we'll clean it up later" tax that metered transformation pricing creates.
MIT, genuinely
PostHog's licence is MIT. No production restrictions, no licence keys, no "source-available" asterisk — unlike RudderStack's Elastic License 2.0 or Snowplow's SLULA. If your requirement is a licence your legal team won't argue with, this is the shortest conversation in the category.
Events, not visitors
Like every alternative here, PostHog meters events, so anonymous traffic costs you what it actually sends rather than a full tracked user each.
Where Segment still wins
PostHog's pipeline is real, but it is not a marketing CDP and PostHog doesn't claim it is. Segment's Unify builds identity graphs across devices, channels and cloud sources; PostHog does person merging. Segment's Engage Foundations builds audiences with computed traits and pushes them to ad platforms and CRMs; PostHog has cohorts aimed at product analysis. And the destination catalogs aren't comparable — 700+ against a focused list. If your growth team lives in Segment audiences, PostHog replaces your analytics bill, not your CDP.
Segment also carries the governance and compliance package a mature data org eventually needs: Protocols tracking plans and schema enforcement, Replay, HIPAA eligibility, EU data residency via Regional Segment, and consent tooling. PostHog covers parts of this — and its self-host option answers data-residency questions differently — but the enterprise checklist is where Segment's Business tier earns its price.
The setup most teams land on
Not either/or. A common 2026 shape: PostHog for product analytics, replay and flags on its free or Scale tier, and a Segment-spec pipeline — RudderStack, Jitsu, or Segment itself if the catalog is load-bearing — for collection and fan-out to marketing tools. PostHog can sit downstream as a destination, so you keep one tracking implementation. Before assuming you need both, check whether your Segment destinations are genuinely marketing tools or just "analytics we already replaced."
Common questions
Segment vs PostHog — FAQ
Can PostHog replace Segment entirely?
It can replace the collection and fan-out half. PostHog ingests events from its own SDKs, pulls from 20+ managed sources such as Stripe, HubSpot, Salesforce, Snowflake and BigQuery, transforms events, and forwards them to real-time destinations or batch-exports them to your warehouse or object storage. What it doesn't replace is the marketing-CDP half: deep identity resolution across devices and channels, audience building with the trait logic marketers expect, and the long tail of activation destinations. If Segment is your growth team's audience tool, PostHog is a partial swap; if Segment is your engineering team's event bus, it's a full one.
How much does PostHog cost compared to Segment?
PostHog's free tier is 1 million events a month, against Segment's 1,000 monthly tracked users and 2 sources — for a small product that difference alone decides the evaluation. Beyond the free tier PostHog charges per event: data pipeline destinations and batch exports run $0.000062 per event, while transformations are free with no volume limit. Segment charges per tracked user: Team is $120/month for 10,000 MTUs with overage at $12 per extra 1,000. Because the units differ, the only honest comparison is to take one real month of your own traffic, count distinct users and total events, and price both.
Is self-hosting PostHog realistic?
It's possible and legally unencumbered — PostHog is MIT-licensed and ships a Docker Compose deployment — but PostHog itself steers people to its cloud and offers no commercial support for self-hosted installations. Running it in production means operating ClickHouse and Kafka yourself, including upgrades, scaling and backups. Choose it when data residency or air-gapping is a hard requirement, not to save money; for most teams the free cloud tier is the cheaper path. Segment, by contrast, can't be self-hosted at any price.