When I first looked at PostHog’s 30,983 GitHub stars, I thought it was just another analytics tool trying to undercut the big players on price.
I was wrong.
The real story isn’t about features or costs—it’s about what you can prove, what you can control, and what happens when your analytics vendor becomes your compliance problem.
If you only read one section, read this:
Open-source changes the power dynamic. You can read the code that processes your data instead of trusting a black box. This matters for compliance, but also for avoiding vendor lock-in when you need custom analysis (GitHub repo).
Pricing models determine what you can afford to measure. PostHog and Mixpanel charge per event; Amplitude charges per user. Pick the wrong model and your bill explodes as you scale (PostHog pricing, Mixpanel pricing, Amplitude pricing).
SQL access means faster answers. PostHog lets you write SQL queries that join product events with customer data—no export pipelines required (SQL docs, Data warehouse).
HIPAA compliance requires paperwork. PostHog provides Business Associate Agreements for Cloud customers with paid add-ons (HIPAA compliance, BAA generator).
Here’s what happens with traditional analytics platforms:
Your engineering team ships event data to Mixpanel or Amplitude. Somewhere in the cloud, that data gets processed, transformed, and stored. You have no idea what’s actually happening to it.
For most companies, this is fine. You trust the vendor. They have big customers, security certifications, and nice marketing pages.
But what if you’re building healthcare software? Or handling financial data? Or just want to avoid getting locked into expensive contracts as you scale?
Open-source flips this relationship. Instead of “trust us,” it’s “verify it yourself.” You can read the code, run it on your own servers, and prove—not just claim—that your setup meets your requirements.
This isn’t theoretical. Healthcare companies use PostHog specifically because they can audit the code to prove HIPAA compliance. Try doing that with a closed-source platform.
Once you get past basic charts and dashboards, here’s where PostHog, Amplitude, and Mixpanel diverge in ways that affect your day-to-day work:
The pricing model isn’t just about cost—it determines what you can afford to measure.
PostHog: Charges $0.00005 per event after the first 1 million events free each month. Also includes 5,000 session replays free and 1 million feature flag requests free (PostHog pricing).
Mixpanel: Offers 1 million monthly events free, then $0.28 per 1,000 events after that. Growth plans include 20,000 monthly session replays free. The free tier limits you to 5 saved reports and 10,000 monthly session replays (Mixpanel pricing).
Amplitude: Uses a completely different model—Monthly Tracked Users (MTUs). Their Plus plan starts at $49/month and includes 50,000 MTUs (up to 10 million events) (Amplitude pricing).
Why this matters: If your product generates lots of events per user (think: real-time collaboration tools, live dashboards, streaming apps), event-based pricing can get expensive fast. But if you have lots of light users who barely touch your product, MTU-based pricing can also rack up costs.
There’s no universal “better” model. The right choice depends on your actual usage patterns.
One subtle difference: Mixpanel charges the same for anonymous and identified events. PostHog differentiates between them, which can matter for products with lots of pre-signup activity (PostHog vs Mixpanel).
This is where PostHog gets interesting.
Most analytics platforms give you predefined reports and dashboards. If you want to answer a custom question—say, “Which customers who upgraded last quarter are most likely to churn based on feature usage?”—you’re either: - Clicking through complex UI wizards - Exporting CSVs and joining them in Excel - Asking your data team to build a pipeline
PostHog gives you SQL. Specifically, HogQL—a SQL variant that works on your event data (HogQL docs).
Even better: you can sync external data sources (like your Stripe customers or production database) into PostHog’s data warehouse and join them directly with your event data (Data warehouse).
Here’s what that looks like in practice:
SELECT
events.distinct_id,
count() AS event_count
FROM events
INNER JOIN prod_stripe_customer
ON events.distinct_id = prod_stripe_customer.email
GROUP BY events.distinct_id
ORDER BY event_count DESCThis query joins your product events with your Stripe customer data—no export pipeline required (Data warehouse query examples).
Mixpanel offers JQL (JavaScript Query Language) for custom queries, but they’ve stated it’s “currently in maintenance mode” (JQL docs).
Amplitude takes a different approach—their platform can run directly on top of your data warehouse, so you query your warehouse, not Amplitude (PostHog vs Amplitude).
The practical difference: PostHog is warehouse-synced (brings data in), while Amplitude is warehouse-native (sits on top of your existing warehouse). Pick based on where your data lives and how your team works.
If you’re using analytics to ship product changes, you need three things: 1. Feature flags to control rollouts 2. Experiments to measure impact 3. Analytics to understand what happened
Most companies use three separate tools for this. That means three vendors, three integrations, and data that doesn’t quite line up.
PostHog bundles all three. You can flag a feature, run an experiment, and analyze results in one platform (Feature flags, Experiments).
Mixpanel positions experimentation and feature flags as “available for Enterprise plans” (Mixpanel experimentation).
Amplitude includes feature flags in their pricing tiers (Amplitude pricing).
If you ship weekly and measure everything, having one integrated loop beats juggling three tools.
Here’s what nobody tells you about analytics platforms: the gotchas aren’t in the headline features. They’re in the fine print.
Saved reports: Mixpanel’s free plan limits you to 5 saved reports (Mixpanel pricing). Once you have 10 dashboards your team actually uses, you’re paying.
Cohorts: Amplitude’s Plus plan lets you “Create up to 5 cohorts” for analysis (Amplitude Plus announcement). If your marketing team wants to analyze 8 different user segments, you’re blocked.
Data retention: This one’s sneaky. PostHog guarantees 7 years retention on paid plans and 1 year on free (PostHog pricing). Mixpanel recently updated their default retention to 2 years, effective September 1, 2025 (Mixpanel retention update).
Retention matters when you need year-over-year comparisons or compliance audits. Check the fine print before you commit.
If you’re building healthcare software, you’ve probably heard: “You can’t use Google Analytics because of HIPAA.”
That’s true. But the real question is: what can you use?
HIPAA requires three things for analytics: 1. Data minimization: Don’t collect protected health information (PHI) unless necessary 2. Business Associate Agreement (BAA): Your vendor must sign one 3. Audit trail: You need to prove what data was collected and how it was handled
Most analytics platforms fail #2. They won’t sign a BAA, or they’ll only sign for enterprise customers.
PostHog is explicit about this: they offer BAAs for Cloud customers with Boost, Scale, or Enterprise add-ons (HIPAA compliance). They even provide a BAA generator to create agreements for countersignature.
But here’s the part that matters more: because PostHog is open-source, you can read the code to verify how data is processed. For a SOC 2 or HIPAA audit, you can walk auditors through the actual implementation—not just marketing claims.
Can you do that with a closed-source platform? No.
PostHog tends to win when:
You need developer-friendly workflows. If your team writes SQL, deploys infrastructure, and wants to build custom analysis, PostHog fits naturally.
You need transparent compliance. Healthcare, fintech, and government teams can audit the code and prove their setup meets requirements.
You want one integrated stack. Analytics + session replay + feature flags + experiments in one platform beats managing four vendors.
PostHog might not be the right choice when:
Your organization is standardized on another ecosystem. If everyone uses Amplitude and your data team has years of pipelines built around it, switching has real costs.
You need very specific enterprise features. Some platforms offer advanced governance, predictive audiences, or AI-powered insights that PostHog doesn’t prioritize.
If you’re switching from Mixpanel, Amplitude, or a homegrown system, here’s the pattern that works:
Step 1: Dual-write for 2-4 weeks. Send events to both the old and new platform. This gives you time to rebuild dashboards and catch discrepancies.
Step 2: Rebuild only what matters. Don’t try to recreate every dashboard. Focus on the 5-10 charts your team actually uses to make decisions—activation funnel, retention curves, key feature adoption.
Step 3: Validate definitions carefully. Make sure event names, user identity logic, and any account/group mappings work the same way. Mismatched definitions will make you distrust the new tool.
Step 4: Cut over gradually. Once the new dashboards match the old ones, start making decisions from the new platform. Retire old tracking code incrementally, not all at once.
The goal isn’t “perfect migration.” It’s “rebuild the decisions we actually make.”
Analytics platforms look similar on feature comparison sheets. They all capture events, show charts, and promise “insights.”
The real differences show up in three places:
1. What you can prove. Open-source lets you verify claims. Closed-source asks you to trust them.
2. What you can connect. SQL access and data warehouse integration mean fewer export pipelines and faster answers.
3. What you can afford to measure. Pricing models (event-based vs MTU-based) determine whether your bill stays predictable as you scale.
If you’re in a regulated industry, building developer tools, or just tired of vendor lock-in, open-source analytics isn’t a nice-to-have. It’s the only way to prove compliance without hiring lawyers to fight your vendors.
PostHog’s 30,983 GitHub stars aren’t just about popularity. They’re about transparency—something traditional analytics vendors can’t offer no matter how good their marketing is.
Jake McMahon helps SaaS companies in regulated industries (healthcare, fintech, professional services) build product analytics that drives competitive advantage while managing compliance and cost.
Recent work includes: - Healthcare: Built compliant analytics infrastructure enabling continuous product optimization where competitors have regulatory gaps - SaaS retention: Developed predictive analytics pipelines using PostHog’s HogQL to identify at-risk customers before they churn - Cost transformation: Eliminated data engineering overhead by replacing export pipelines with direct HogQL queries
Connect: LinkedIn | Email: jake.mrwgroup@gmail.com
Every claim in this article is backed by primary sources: