PostHog

The USER layer is 100 HackerNews comments with a heavy founder/engineer skew — and notably, the most-upvoted material is thread drift: a long Slack-vs-forums debate sparked by PostHog building its own community platform (chat 'loses' previously answered questions, isn't Google-searchable, is noisy; forums better for async troubleshooting). One commenter warns the in-house build means 're-inventing login/regi, user management, moderation, threads... with the bugs that come with it' — time not spent on core product. On the product itself, the single most substantive technical critique comes from the engineer who 'scaled Heap': query-performance scaling was 'perpetually' Heap's growth limit, and PostHog's lack of multi-tenancy is a 'huge disadvantage' because a single customer's query can't borrow compute from a cluster sized for everyone. Adoption drivers named explicitly: data ownership/privacy (GDPR), cost, and control — echoed by RudderStack's founder citing 'Control, Cost & Privacy (Data-Ownership)'. Criticism of the open-core model: one top comment calls it 'a lazy business model'; another notes classic build-vs-buy friction makes monetizing open-source users hard, though GitLab/Sentry/Mattermost are cited as proof it can work. PostHog founders are visibly active in threads — admitting at launch that backend grouping exists but 'the UI isn't quite there yet' for team-level analytics, positioning Metabase/Tableau integration for deep BI, and explaining docs-embedded Q&A as part of a website-as-sales-team strategy (they do no sales). Skepticism also targets the launch speed claim ('backend, frontend, integrations, docs, SDKs... in 4 weeks? That is nuts'). Net: technically credible and well-liked for its open-source/self-host stance, with genuine unresolved doubts about enterprise-scale performance, early feature gaps, and open-core sustainability.

No aggregate ratings were found for this product during the last harvest.