PostHog bundles product analytics, session recording, feature flags, A/B testing, and surveys into one open-source platform. Here’s whether it’s actually worth using as a solo founder.
Research-based overview. This article synthesizes public documentation, pricing pages, and user reports. We have not built a production application with every tool we cover; where first-person testing exists, it’s called out explicitly. How we research.
PostHog is an open-source product analytics platform that has quietly become one of the most comprehensive tools in the analytics space. It started in 2020 as a self-hosted alternative to Mixpanel, but in the years since, it has expanded into a full product intelligence suite that includes event analytics, session recording, feature flags, A/B testing, and user surveys — all in a single product.
The core premise is simple: instead of stitching together five or six different tools to understand how users interact with your product, you install one JavaScript snippet and get everything from a single dashboard. For a solo SaaS founder who does not have time to evaluate, integrate, and maintain multiple analytics vendors, that consolidation is enormously valuable.
PostHog is built on ClickHouse, a columnar database designed for analytical queries. This means it can process millions of events and return query results in seconds, even on the cloud-hosted version. For context, a typical solo SaaS product with 1,000 active users generates roughly 50,000–200,000 events per month. PostHog handles this volume effortlessly, and its free tier covers the first 1 million events per month — so you are unlikely to pay anything until your product has significant traction.
The open-source aspect matters for two reasons. First, you can self-host PostHog on your own infrastructure if you have strict data residency requirements or simply prefer to control your data. Second, the open-source codebase means the product evolves rapidly with contributions from a large community, and you can inspect exactly how your data is being processed. There is no black box.
PostHog is headquartered in the UK and has raised over $75 million in funding. It is not a side project or an indie tool — it is a well-funded, actively maintained platform with a team of over 50 engineers. That stability matters when you are choosing analytics infrastructure that your product will depend on for years.
PostHog has a long feature list, but as a solo founder, you will use roughly six of its capabilities on a regular basis. Here is what each one does and why it matters for your workflow.
This is the foundation. Event analytics tracks every action users take in your application — page views, button clicks, form submissions, API calls, feature usage. You define events either through code (by calling posthog.capture('event_name')) or through PostHog’s autocapture feature, which automatically tracks clicks, page views, and form submissions without any additional code.
Autocapture is particularly valuable for solo founders because it means you start collecting data from the moment you install PostHog, without having to plan your event taxonomy in advance. You can retroactively analyze any interaction that happened in the past, as long as PostHog was installed when it occurred. This is a fundamentally different approach from tools like Mixpanel, which only track events you explicitly define in code.
The event analytics dashboard lets you create trend charts, breakdowns by property, and retention curves. The queries are flexible — you can filter by any event property, group by user properties, and set custom date ranges. For a solo founder, the three most important queries are: daily active users over time, feature adoption rates (what percentage of users have used feature X), and retention (what percentage of users come back after day 1, 7, 30).
Funnels show you where users drop off in a multi-step process. The classic example is a signup funnel: landing page → signup form → email verification → onboarding → first key action. PostHog shows you the conversion rate at each step and highlights where the biggest drop-offs occur.
For a SaaS product, funnels answer the single most important growth question: where are you losing users? If 60% of signups never complete onboarding, that is a more urgent problem than any new feature you could build. PostHog’s funnel visualization makes these drop-offs impossible to ignore.
You can also compare funnels between user segments. For example: do users who arrive from Google convert at a different rate than users who arrive from Twitter? Do users on the free plan complete onboarding faster than users on a trial? These comparisons are trivial to set up in PostHog and can reveal insights that fundamentally change your growth strategy.
Session recording captures video replays of real user sessions in your application. You can watch exactly what a user saw, where they clicked, where they hesitated, and where they got confused. This is the single most underrated analytics feature for solo founders.
Numbers tell you what happened. Session recordings tell you why. When your funnel shows a 40% drop-off at the onboarding step, watching five session recordings of users who dropped off will usually reveal the exact friction point — a confusing form field, a misleading button label, a loading state that looks like an error. You cannot get this level of insight from event data alone.
PostHog’s session recording is built into the same platform as the event analytics, which means you can click from a funnel drop-off directly into the session recordings of users who dropped off at that specific step. This integration between quantitative data (funnels) and qualitative data (recordings) is remarkably powerful and is something neither Mixpanel nor Amplitude offers natively.
My workflow: every Monday morning, I watch 10 session recordings from the previous week — 5 from users who completed onboarding and 5 from users who did not. This 30-minute ritual consistently produces more actionable insights than any dashboard or metric.
Feature flags let you ship code to production without making it visible to all users. You deploy the code behind a flag, enable it for a subset of users (yourself, beta testers, users on a specific plan), and then gradually roll it out to everyone once you are confident it works.
For a solo founder, feature flags solve the deployment anxiety problem. Instead of deploying a new feature and hoping nothing breaks for all users simultaneously, you deploy it behind a flag and enable it only for yourself first. You use the product with the new feature, verify it works, and then gradually expand access. If something goes wrong, you disable the flag instantly — no rollback, no hotfix, no downtime.
PostHog’s feature flags also enable percentage-based rollouts (enable for 10% of users, then 25%, then 50%, then 100%) and targeting by user properties (enable for users on the Pro plan only, or for users in a specific country). This level of control is essential for managing risk as a solo founder who cannot afford to break the product for all users at once.
PostHog’s A/B testing is built on top of feature flags. You create an experiment with two or more variants, define a target metric (signup conversion rate, feature adoption, revenue per user), and PostHog splits traffic between the variants and tracks the results with statistical significance calculations.
Most solo founders do not run enough A/B tests. The reason is friction — setting up an experiment in a standalone A/B testing tool requires integrating another SDK, defining events in two places, and reconciling data between systems. PostHog eliminates that friction because the A/B testing uses the same events, the same user properties, and the same dashboard as everything else. Setting up a new experiment takes five minutes, not five hours.
The experiments I recommend every solo founder run: pricing page variants (different price points, different feature matrices), onboarding flow variants (shorter vs longer, with vs without a product tour), and CTA copy variants on the landing page. These three experiments, run sequentially, can easily double your conversion rate over the course of a few months.
PostHog recently added in-app surveys, which let you ask users questions directly inside your product. You can target surveys to specific user segments — new users, power users, users who just cancelled — and collect qualitative feedback without sending them to a separate survey tool like Typeform.
The surveys that matter most for solo founders: a one-question NPS survey (How likely are you to recommend this product?), a churn survey triggered when a user cancels (Why are you leaving?), and a feature request survey shown to power users (What feature would make this product more valuable to you?). These three surveys, running continuously, give you a constant stream of qualitative data that complements the quantitative data from event analytics.
PostHog’s pricing is usage-based and genuinely generous for small products. Here is what you get at each tier:
To put this in practical terms: a SaaS product with 2,000 active users generating 500,000 events per month will pay $0 on PostHog. A product with 10,000 active users generating 3 million events per month will pay roughly $60–80/month. You have to achieve significant scale before PostHog costs become material.
Compare this to Mixpanel, which starts at $28/month for its Growth plan and charges based on tracked users (not events), or Amplitude, which charges based on event volume with a free tier limited to 10 million events per month but with significant feature restrictions. PostHog’s free tier is more generous than either competitor when you account for the breadth of features included.
The key insight about PostHog’s pricing is that it scales linearly with your product’s success. When you are pre-revenue and have 100 users, you pay nothing. When you have 10,000 paying users and real revenue, you pay a modest amount that is easily justified by the insights you get. There is no cliff where the price jumps from free to expensive overnight.
The three major product analytics platforms in 2026 are PostHog, Mixpanel, and Amplitude. Here is how they compare across the dimensions that matter for solo SaaS founders:
| Feature | PostHog | Mixpanel | Amplitude |
|---|---|---|---|
| Event analytics | Full + autocapture | Full | Full |
| Session recording | Built-in | Not available | Via integration |
| Feature flags | Built-in | Not available | Limited |
| A/B testing | Built-in | Not available | Built-in |
| Surveys | Built-in | Not available | Not available |
| Open source | Yes — MIT license | No | No |
| Self-host option | Yes | No | No |
| Free tier | 1M events/mo | 20M events/mo | 10M events/mo |
| Paid pricing | Usage-based, ~$0.00031/event | From $28/mo | From $49/mo (Plus) |
| Best for | Solo founders who want everything in one tool | Teams focused purely on event analytics | Larger teams with dedicated product analysts |
PostHog vs Mixpanel. Mixpanel is a strong product analytics tool with an excellent query interface and deep funnel analysis. However, it does not offer session recording, feature flags, A/B testing, or surveys. If you choose Mixpanel, you will need to add Hotjar or FullStory for session recording ($30–80/month), LaunchDarkly for feature flags ($10/month), and a separate A/B testing tool. For a solo founder, that is three additional integrations to manage and three additional monthly bills to pay. PostHog gives you all of those capabilities in a single installation.
Mixpanel’s advantage is that its event analytics interface is more polished and its query builder is slightly more intuitive. If you only need event analytics and nothing else, Mixpanel is an excellent choice. But most solo founders need the full suite, and PostHog delivers it in one package.
PostHog vs Amplitude. Amplitude is the analytics tool of choice for larger product teams. It has powerful cohort analysis, excellent data visualization, and deep integration with data warehouses. It also offers A/B testing through its Experiment product, but that requires a separate paid plan.
Amplitude’s free tier (Starter) is generous with 10 million events per month, but it limits you to basic analytics features. The Plus plan at $49/month unlocks more advanced capabilities but still does not include session recording or feature flags. For a solo founder, Amplitude is more tool than you need, priced higher than you want, and missing capabilities (session recording, feature flags, surveys) that PostHog includes for free.
The bottom line on comparisons: PostHog is not the best at any single capability, but it is the best at being a single tool that covers everything a solo SaaS founder needs. The consolidation advantage — one SDK, one dashboard, one bill — is worth more than marginal improvements in any individual feature.
Installing PostHog in a Next.js SaaS application takes roughly 15 minutes. Here is the complete process.
Step 1: Create a PostHog account. Go to posthog.com, sign up with your email, and create a new project. PostHog will generate a project API key — you will need this in the next step. The entire signup process takes about two minutes.
Step 2: Install the package. Run npm install posthog-js in your Next.js project. This is the only dependency you need. PostHog’s JavaScript SDK is lightweight (roughly 25KB gzipped) and does not noticeably impact page load performance.
Step 3: Initialize PostHog. Create a PostHog provider component that initializes the client with your API key. In a Next.js App Router application, this goes in your root layout. The initialization enables autocapture by default, which means PostHog immediately starts tracking page views, clicks, and form submissions without any additional configuration.
Step 4: Identify users. When a user logs in, call posthog.identify(userId) with their unique ID and any properties you want to track (email, plan, signup date). This links their anonymous pre-login activity with their authenticated post-login activity, giving you a complete picture of each user’s journey from first visit to paying customer.
Step 5: Add custom events. While autocapture covers basic interactions, you will want to track specific product events that map to your business metrics. Common examples for a SaaS: subscription_started, feature_used, invite_sent, export_completed. Each of these is a single line of code: posthog.capture('event_name', { properties }).
That is the entire setup. Five steps, 15 minutes, and you have full product analytics with session recording, feature flags, and A/B testing capabilities. The first data will appear in your PostHog dashboard within minutes of deploying the code.
One tip that saves significant time later: set up a PostHog actions dashboard on day one with these four metrics: daily active users, new signups, feature adoption (for your three most important features), and week-one retention. Having these four metrics visible from launch gives you a baseline to measure everything against.
PostHog replaces five separate tools (analytics, session recording, feature flags, A/B testing, surveys) with a single platform that has a genuinely generous free tier. The setup takes 15 minutes, the free tier covers up to 1 million events per month, and the breadth of features means you never need to evaluate another analytics vendor until you are well past the solo founder stage. If you are building a SaaS product in 2026 and you have not set up analytics yet, PostHog is the clear starting point.
The only scenario where I would not recommend PostHog is if you have an extremely specific need that another tool handles better — for example, if you need enterprise-grade cohort analysis and your team has a dedicated data analyst, Amplitude may be a better fit. But for the typical solo founder who needs solid analytics, session recordings, and the ability to run experiments, PostHog covers all of it with zero configuration overhead.
Try PostHog free at posthog.com →The stack, prompts, pricing, and mistakes to avoid — for solo founders building with AI.