Teams pay because analytics has to keep collecting and stay trustworthy while the product changes underneath it. The bill buys bot filtering, identity resolution, late-arriving data, retention, query cost, and someone else getting paged when ingestion stops. The charts are the cheap part.
REPLACEMENT BRIEF
analytics
Can AI replace PostHog?
EDITORIAL ANSWERNOT REALLYCurated prompt
Collect first-party pageviews and custom events from your own sites, keep the raw rows yourself, and answer a handful of product questions from a local dashboard.
See the closest workaround →AT A GLANCE
- price
- varies
- replaceable scope
- single-product first-party analytics
- build time
- closest consolation build: one sitting
what AI can build
Collect first-party pageviews and custom events from your own sites, keep the raw rows yourself, and answer a handful of product questions from a local dashboard.
First-party collection and a dashboard that answers your top five questions is one sitting of work, and PostHog's free tier covers a million events a month before you pay anything. What the bill buys past that is the rest of the platform: session replay, feature flags, SQL over years of events, and ingestion that stays correct while your event schema drifts underneath it.
The prompt was editor-reviewed; no completed build is recorded.
The honest tradeoff
who should keep paying
what you lose
xsession replay
xfeature flags and experiments
xidentity stitching across devices
xSQL over years of events
xingestion that stays up without you watching it
Start with existing software
prior art · use these instead of building, if you'd rather
EVIDENCE LEDGER
What this page can prove
The verdict judges replaceability. The evidence level records what DeepFeather actually checked.
evidence level
Curated promptThe prompt was editor-reviewed; no completed build is recorded.
Usage based · usage-based
known limits · session replay; feature flags and experiments
closest workaround promptsecondary workaround · reviewed prompt · not run
the prompt
Curated promptBuild me a self-hosted web analytics box to replace PostHog. Requirements:
- One Node 22 + Express process with better-sqlite3, serving the collector and the
dashboard on port 8787. No frontend framework, no build step, no Docker.
- A tracker.js I paste on my sites: pageviews on load and history change, plus
window.track('signup', { plan: 'pro' }), POSTed to /e on my own domain so
collection stays first-party.
- One SQLite events table: site, event, path, referrer, UTM fields, country from the
proxy header, device class, and a JSON properties blob.
- Count visitors by a daily-rotating salted hash of IP plus user agent, salt in .env.
No cookie, never the raw IP. That is the whole privacy design, keep it.
- Dashboard at / with a date range picker: visitors and pageviews by day, top pages,
referrers, countries, any event split by one property, and a three-step funnel.
- Nightly rollup into a daily-summary table, raw events pruned past the retention
window in .env, /export.csv for the raw rows.
- Basic auth on the dashboard, collector open. No accounts, no telemetry, my box
holds the only copy.
- Out of scope: session replay, feature flags, and stitching one person across
devices. Do not build a plugin system or a warehouse connector.
- README: the snippet to paste, where the SQLite file lives, and how to back it up.Copy or open in an agent
The prompt stays readable first. Choose a launch option when you are ready.
$ open in your agent (prompt prefilled, you press enter) or copy it raw
BUILD FEEDBACK
Did you try this build?
Report the outcome. Submissions enter a manual evidence queue and never auto-upgrade the verdict.
related verdicts
Want next week’s replacements?
New verdicts + most-wanted, weekly. Free. One-click out.
Share this verdict
questions
Can AI replace PostHog?
Not really. PostHog's value is not just interface code — data pipeline reliability and analytical depth. See the honest breakdown above.
How much does PostHog cost?
PostHog's pricing is usage-based or varies by plan. Use the linked pricing source for the current amount; the catalog last checked it on 2026-07-31.
What do I lose by replacing PostHog?
Honestly: session replay; feature flags and experiments; identity stitching across devices; SQL over years of events; ingestion that stays up without you watching it. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to PostHog?
Yes — Umami (Popular open-source privacy-focused web analytics platform.). Using prior art is also a valid exit; the prompt is for when you want it exactly your way.