📊 Analytics

Can I vibe code PostHog?

Open-source product suite: analytics, session replay, flags, experiments.

🟡Kinda — with gapsest. a weekend per slice (the full suite is not a solo build)

PostHog is open source, so you can genuinely self-host the whole thing today — that alone tempers any harder verdict. Building your own is another story, because PostHog is not one product but a suite: product analytics, session replay, feature flags, experiments, surveys, and a data warehouse. Any single slice — event analytics, or a basic feature-flag service — is a weekend you can absolutely do. Recreating the integrated platform is not, so it is a kinda: self-host the real thing, or build one slice, but do not expect to clone the suite.

The one-shot prompt
Build one well-scoped slice of PostHog for my own app rather than the whole suite — pick product analytics. Ship a tiny event beacon with a capture(event, properties) helper, an ingest API, and event storage in a hosted Postgres. Build a password-protected dashboard with unique users, top events, a funnel builder, and a weekly retention grid. As a bonus, add a minimal feature-flag endpoint that returns on or off for a given flag and user so I can gate features. Use Next.js App Router deployable to Vercel, and respect Do Not Track. Be explicit in the README that session replay, experiments, surveys, and a data warehouse are out of scope, and that PostHog itself is open source and can be self-hosted if I want the full suite.
Paste into Claude Code, Codex, or your agent of choice — then steer. Learn the moves in Prompt Engineering.
What you build

One slice done well — event analytics with funnels, or a simple feature-flag and A/B service — for your own app, not the whole suite.

What you give up
  • Session replay, which is a hard product on its own
  • The integrated suite — analytics, flags, experiments, surveys in one place
  • The data warehouse and SQL access across products
  • Scaled event ingestion and query performance
  • The plugin and integration ecosystem
Why people still pay

Even though it is open source, teams pay for PostHog Cloud to avoid operating a heavy, multi-service platform, and for the value of having analytics, replay, and flags share one dataset. The integration and the not-running-it-yourself convenience are the moat; a single self-built slice does not replace the suite.

open-source-existsplatformconvenience
Related
Actually build it

A prompt is the first move, not the whole game. Course 01 teaches you to take a prompt like this one to a shipped, working app — reviewing, correcting, and steering the agent the whole way.

Start Course 01 →