PostHog
PostHog/posthog
Open-source product analytics: events, session replay, flags, experiments — self-host or cloud. GitHub: PostHog/posthog (~38k stars).
GitHub repository
Overview
PostHog is the open-source project at PostHog/posthog on GitHub (https://github.com/PostHog/posthog). Open-source product analytics: events, session replay, flags, experiments — self-host or cloud. Category on LimeDock: growth. Approximate community size: ~38k GitHub stars. Repo (copy/paste): https://github.com/PostHog/posthog This LimeDock Directories page explains what it is and how teams use it in plain English — so searches for the GitHub project can land on a practical guide.
Work with LimeDock
Using this skill? LimeDock can wire it into a durable automation you own.
Skills show what's possible. LimeDock builds and runs the owned marketing, sales, and ops automations around them.
We sell owned automations for SaaS teams — live workflows that plug into Slack, CRM, and your internal platform — not just a skill list.
Link
Installation guide
Open the GitHub repository, then follow the README for your stack.
Official GitHub repository: https://github.com/PostHog/posthog GitHub path: PostHog/posthog
How to open it: 1. Copy this URL: https://github.com/PostHog/posthog 2. Clone or follow the README install for your OS / stack. 3. Start with the smallest example in their docs before production use.
How to use it
**Simple example** You can’t answer “where do users drop?” without another SaaS bill negotiation.
1. Deploy PostHog cloud or self-host. 2. Install the JS snippet. 3. Track signup → activation events. 4. Watch one replay of a confused user.
Example prompts
- “Define an activation event taxonomy in PostHog.”
- “PostHog vs Plausible for our stage?”
- “Set up a feature flag + experiment.”
Use cases and examples
- Evaluate PostHog/posthog for your stack
- Onboard a teammate to PostHog with a shared checklist
- Compare PostHog against tools you already pay for
- Capture lessons in your internal wiki after a pilot
Prerequisites
- Engineering time for events
- Privacy policy update
Tips
- Event naming conventions save you later.
- Replay is sensitive — handle access carefully.