posthog

Professional software vendor delivering innovative solutions on the Softono platform. Specialized in both open-source and proprietary software development.

Visit Website

Total Products

Software by posthog

Open Source

PostHog

<img alt="posthoglogo" src="https://user-images.githubusercontent.com/65415371/205059737-c8a4f836-4889-4654-902e-f302b187b6a0.png"> <a href='https://posthog.com/contributors'><img alt="GitHub contributors" src="https://img.shields.io/github/contributors/posthog/posthog"/></a> <a href='http://makeapullrequest.com'><img alt='PRs Welcome' src='https://img.shields.io/badge/PRs-welcome-brightgreen.svg?style=shields'/></a> <img alt="Docker Pulls" src="https://img.shields.io/docker/pulls/posthog/posthog"/> <a href="https://github.com/PostHog/posthog/commits/master"><img alt="GitHub commit activity" src="https://img.shields.io/github/commit-activity/m/posthog/posthog"/> </a> <a href="https://github.com/PostHog/posthog/issues?q=is%3Aissue%20state%3Aclosed"><img alt="GitHub closed issues" src="https://img.shields.io/github/issues-closed/posthog/posthog"/> </a> <a href="https://posthog.com/docs">Docs</a> - <a href="https://posthog.com/community">Community</a> - <a href="https://posthog.com/roadmap">Roadmap</a> - <a href="https://posthog.com/why">Why PostHog?</a> - <a href="https://posthog.com/changelog">Changelog</a> - <a href="https://github.com/PostHog/posthog/issues/new?assignees=&labels=bug&template=bug_report.yml">Bug reports</a> <a href="https://www.youtube.com/watch?v=1FZji2L-LmM"> <img src="https://res.cloudinary.com/dmukukwp6/image/upload/demo_thumb_68d0d8d56d" alt="PostHog Demonstration"> </a> ## PostHog is an all-in-one, open source platform for building successful products [PostHog](https://posthog.com/) provides every tool you need to build a successful product including: - [Product Analytics](https://posthog.com/product-analytics): Autocapture or manually instrument event-based analytics to understand user behavior and analyze data with visualization or SQL. - [Web Analytics](https://posthog.com/web-analytics): Monitor web traffic and user sessions with a GA-like dashboard. Easily monitor conversion, web vitals, and revenue. - [Session Replays](https://posthog.com/session-replay): Watch real user sessions of interactions with your website or mobile app to diagnose issues and understand user behavior. - [Feature Flags](https://posthog.com/feature-flags): Safely roll out features to select users or cohorts with feature flags. - [Experiments](https://posthog.com/experiments): Test changes and measure their statistical impact on goal metrics. Set up experiments with no-code too. - [Error Tracking](https://posthog.com/error-tracking): Track errors, get alerts, and resolve issues to improve your product. - [Surveys](https://posthog.com/surveys): Ask anything with our collection of no-code survey templates, or build custom surveys with our survey builder. - [Data warehouse](https://posthog.com/data-warehouse): Sync data from external tools like Stripe, Hubspot, your data warehouse, and more. Query it alongside your product data. - [Data pipelines](https://posthog.com/cdp): Run custom filters and transformations on your incoming data. Send it to 25+ tools or any webhook in real time or batch export large amounts to your warehouse. - [AI observability](https://posthog.com/docs/ai-observability): Capture traces, generations, latency, and cost for your LLM-powered app. - [Workflows](https://posthog.com/docs/workflows): Create workflows that automate actions or send messages to your users. Best of all, all of this is free to use with a [generous monthly free tier](https://posthog.com/pricing) for each product. Get started by signing up for [PostHog Cloud US](https://us.posthog.com/signup) or [PostHog Cloud EU](https://eu.posthog.com/signup). ## Table of Contents - [PostHog is an all-in-one, open source platform for building successful products](#posthog-is-an-all-in-one-open-source-platform-for-building-successful-products) - [Table of Contents](#table-of-contents) - [Getting started with PostHog](#getting-started-with-posthog) - [PostHog Cloud (Recommended)](#posthog-cloud-recommended) - [Self-hosting the open-source hobby deploy (Advanced)](#self-hosting-the-open-source-hobby-deploy-advanced) - [Setting up PostHog](#setting-up-posthog) - [Learning more about PostHog](#learning-more-about-posthog) - [Contributing](#contributing) - [Open-source vs. paid](#open-source-vs-paid) - [We’re hiring!](#were-hiring) ## Getting started with PostHog ### PostHog Cloud (Recommended) The fastest and most reliable way to get started with PostHog is signing up for free to [PostHog Cloud](https://us.posthog.com/signup) or [PostHog Cloud EU](https://eu.posthog.com/signup). Your first 1 million events, 5k recordings, 1M flag requests, 100k exceptions, and 1500 survey responses are free every month, after which you pay based on usage. ### Self-hosting the open-source hobby deploy (Advanced) If you want to self-host PostHog, you can deploy a hobby instance in one line on Linux with Docker (recommended 4GB memory): ```bash /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/posthog/posthog/HEAD/bin/deploy-hobby)" ``` Open source deployments should scale to approximately 100k events per month, after which we recommend [migrating to a PostHog Cloud](https://posthog.com/docs/migrate/migrate-to-cloud). We _do not_ provide customer support or offer guarantees for open source deployments. See our [self-hosting docs](https://posthog.com/docs/self-host), [troubleshooting guide](https://posthog.com/docs/self-host/deploy/troubleshooting), and [disclaimer](https://posthog.com/docs/self-host/open-source/disclaimer) for more info. ## Setting up PostHog Once you've got a PostHog instance, you can set it up by installing our [JavaScript web snippet](https://posthog.com/docs/getting-started/install?tab=snippet), one of [our SDKs](https://posthog.com/docs/getting-started/install?tab=sdks), or by [using our API](https://posthog.com/docs/getting-started/install?tab=api). We have SDKs and libraries for popular languages and frameworks like: | Frontend | Mobile | Backend | | ----------------------------------------------------- | --------------------------------------------------------------- | --------------------------------------------------- | | [JavaScript](https://posthog.com/docs/libraries/js) | [React Native](https://posthog.com/docs/libraries/react-native) | [Python](https://posthog.com/docs/libraries/python) | | [Next.js](https://posthog.com/docs/libraries/next-js) | [Android](https://posthog.com/docs/libraries/android) | [Node](https://posthog.com/docs/libraries/node) | | [React](https://posthog.com/docs/libraries/react) | [iOS](https://posthog.com/docs/libraries/ios) | [PHP](https://posthog.com/docs/libraries/php) | | [Vue](https://posthog.com/docs/libraries/vue-js) | [Flutter](https://posthog.com/docs/libraries/flutter) | [Ruby](https://posthog.com/docs/libraries/ruby) | Beyond this, we have docs and guides for [Go](https://posthog.com/docs/libraries/go), [.NET/C#](https://posthog.com/docs/libraries/dotnet), [Django](https://posthog.com/docs/libraries/django), [Angular](https://posthog.com/docs/libraries/angular), [WordPress](https://posthog.com/docs/libraries/wordpress), [Webflow](https://posthog.com/docs/libraries/webflow), and more. Once you've installed PostHog, see our [product docs](https://posthog.com/docs/product-os) for more information on how to set up [product analytics](https://posthog.com/docs/product-analytics/capture-events), [web analytics](https://posthog.com/docs/web-analytics/getting-started), [session replays](https://posthog.com/docs/session-replay/how-to-watch-recordings), [feature flags](https://posthog.com/docs/feature-flags/creating-feature-flags), [experiments](https://posthog.com/docs/experiments/creating-an-experiment), [error tracking](https://posthog.com/docs/error-tracking/installation#setting-up-exception-autocapture), [surveys](https://posthog.com/docs/surveys/installation), [data warehouse](https://posthog.com/docs/cdp/sources), and more. ## Learning more about PostHog Our code isn't the only thing that's open source 😳. We also open source our [company handbook](https://posthog.com/handbook) which details our [strategy](https://posthog.com/handbook/why-does-posthog-exist), [ways of working](https://posthog.com/handbook/company/culture), and [processes](https://posthog.com/handbook/team-structure). Curious about how to make the most of PostHog? We wrote a guide to [winning with PostHog](https://posthog.com/docs/new-to-posthog/getting-hogpilled) which walks you through the basics of [measuring activation](https://posthog.com/docs/new-to-posthog/activation), [tracking retention](https://posthog.com/docs/new-to-posthog/retention), and [capturing revenue](https://posthog.com/docs/new-to-posthog/revenue). ## Contributing We <3 contributions big and small: - Vote on features or get early access to beta functionality in our [roadmap](https://posthog.com/roadmap) - Open a PR (see our instructions on [developing PostHog locally](https://posthog.com/handbook/engineering/developing-locally)) - Submit a [feature request](https://github.com/PostHog/posthog/issues/new?assignees=&labels=enhancement%2C+feature&template=feature_request.yml) or [bug report](https://github.com/PostHog/posthog/issues/new?assignees=&labels=bug&template=bug_report.yml) For an overview of the codebase structure, see [monorepo layout](docs/internal/monorepo-layout.md) and [products](products/README.md). ## Open-source vs. paid This repo is available under the [MIT expat license](https://github.com/PostHog/posthog/blob/master/LICENSE), except for the `ee` directory (which has its [license here](https://github.com/PostHog/posthog/blob/master/ee/LICENSE)) if applicable. Need _absolutely 💯% FOSS_? Check out our [posthog-foss](https://github.com/PostHog/posthog-foss) repository, which is purged of all proprietary code and features. The pricing for our paid plan is completely transparent and available on [our pricing page](https://posthog.com/pricing). ## We're hiring! <img src="https://res.cloudinary.com/dmukukwp6/image/upload/v1/posthog.com/src/components/Home/images/mission-control-hog" alt="Hedgehog working on a Mission Control Center" width="350px"/> Hey! If you're reading this, you've proven yourself as a dedicated README reader. You might also make a great addition to our team. We're growing fast [and would love for you to join us](https://posthog.com/careers).

Product Analytics Feature Flags

34.9K Github Stars

Open Source

posthog.com

<img alt="posthoglogo" src="https://user-images.githubusercontent.com/65415371/205059737-c8a4f836-4889-4654-902e-f302b187b6a0.png"> # PostHog.com - Website, docs, blog, and handbook <a href='http://makeapullrequest.com'><img alt='PRs Welcome' src='https://img.shields.io/badge/PRs-welcome-brightgreen.svg?style=shields'/></a> <img alt="GitHub contributors" src="https://img.shields.io/github/contributors/posthog/posthog.com"/> <a href='https://posthog.com/community'><img alt="Join Community" src="https://img.shields.io/badge/community-join-blue"/></a> <img alt="GitHub commit activity" src="https://img.shields.io/github/commit-activity/m/posthog/posthog.com"/> <img alt="GitHub closed pull requests" src="https://img.shields.io/github/issues-pr-closed/posthog/posthog.com"/> <a href="https://app.posthog.com/home#supportModal">Support</a> - <a href="https://posthog.com/roadmap">Roadmap</a> - <a href="https://github.com/PostHog/posthog.com/issues/new">Open an issue</a> - <a href="https://github.com/PostHog/posthog.com/blob/master/STYLEGUIDE.md">Style guide</a> This is the repository for the PostHog website. We treat it like a product. It contains: - All of our written content and visuals including product features, manuals, docs, blogs, case studies, tutorials, and the handbook - Features like questions and answers (using [Squeak!](https://github.com/PostHog/squeak)), job listings (using [Ashby](https://www.ashbyhq.com/customers/posthog-customer-story)), pricing calculator, roadmap, API docs, and more - All the components, templates, logic, and styling to make this work, look pretty, and spark joy ## Table of contents - [Quick start](#quick-start) - [Advanced setup](#advanced-setup) - [Contributing](#contributing) ## Quick start > `AGENTS.md` is equipped with instructions for the most fundamental parts of running the app. > > If you find places where current documentation is lacking, email [email protected] with the subject, "AGENTS.md". 1. **Pre-installation** Install [Node](https://nodejs.org/en/download/) (version 22) - if you installed Node using nvm, you can run `nvm use` to automatically switch to the correct version. Install `pnpm`. The easiest way to do this is via `corepack use pnpm@latest-10`. 2. **Start developing** Clone the repo and navigate into your new site’s directory: ```bash git clone [email protected]:PostHog/posthog.com.git && cd posthog.com/ ``` If you're using an Apple Silicon Mac (M1 or later) you'll need to run the following commands: ```bash rm -rf ./node_modules brew install vips ``` Then install the site dependencies, and start it up: ```bash pnpm install pnpm start ``` > **Tip:** Seeing a discrepancy between local development and staging/production? Preview the production build locally by running `gatsby build && gatsby serve` 3. **Open the source code and start editing!** Your site is now running at `http://localhost:8001`! > **Note:** You'll also see a second link: `http://localhost:8001/___graphql`. This is a tool you can use to experiment with querying your data. Learn more about using this tool in the [Gatsby tutorial](https://www.gatsbyjs.org/tutorial/part-five/#introducing-graphiql). See full instructions on [developing PostHog.com locally in our manual](https://posthog.com/handbook/engineering/posthog-com/developing-the-website). ## Advanced setup ### Debugging errors on start 1. Pull the latest changes from `master` 2. Run `pnpm clean && mkdir .cache & pnpm start` or delete `node_modules` and `.cache` 3. Make sure you're not in an activated flox environment for a different project 4. Check builds are passing in [deployment to Vercel](https://github.com/PostHog/posthog.com/deployments) ### Working on `/docs/api`? The site will load the API schema from US Cloud by default. You can override this to use your local PostHog instance with an env var: ``` POSTHOG_OPEN_API_SPEC_URL="http://127.0.0.1:8000/api/schema/" pnpm start ``` ### Want Ashby job listings or GitHub contributors to load? You’ll need to set environment variables for these. [See (private) instructions](https://github.com/PostHog/company-internal/blob/master/website-api-keys.md) for this. ### Developing the posts section To see your local version of the posts section, `/posts` needs to be visited directly (`http://localhost:8001/posts`) ### Cloudflare PR previews [PR previews](https://github.com/PostHog/posthog.com/blob/master/.github/workflows/deploy-preview.yml) build with **`GATSBY_MINIMAL=true`** (same idea as `pnpm build:minimal`). **Post listing pages** such as `/tutorials`, `/blog`, and `/posts` are **not** generated, so those URLs may break in the preview. **Open the direct URL** to your doc or post (e.g. `/tutorials/your-slug`) to review changes. Listings and search stay aligned with production after merge to `master`. More detail: [Developing the website → PR preview deployments](https://posthog.com/handbook/engineering/posthog-com/developing-the-website#pr-preview-deployments-cloudflare-pages). ### Developing the merch store Additional environment variables are needed to develop the merch store: - `SHOPIFY_APP_PASSWORD` - `GATSBY_MYSHOPIFY_URL` - `GATSBY_SHOPIFY_STOREFRONT_TOKEN` Currently, these environment variables are excluded from Vercel preview builds to disable merch store node creation and speed up build times on non-merch related PRs. ### Dynamic open graph images To develop a dynamic open graph image: 1. Run `pnpm build` with both the `ASHBY_API_KEY` and `GITHUB_API_KEY` set. 1. In `gatsby/onPostBuild.ts`, temporarily comment out the following: ``` if (process.env.VERCEL_GIT_COMMIT_REF !== 'master') return ``` 1. Find the generated open graph image in `public/og-images/` ## Contributing We <3 contributions big and small. In priority order (although everything is appreciated) with the most helpful first: - Ask a [question in our community](https://posthog.com/questions) - Submit [bug reports and give us feedback in the app](https://app.posthog.com/home#supportModal)! - Vote on features or get early access to beta functionality in our [roadmap](https://posthog.com/roadmap) - Open a PR - Read [our instructions above](#quick-start) on developing PostHog.com locally - Read more [detailed instructions in our manual](https://posthog.com/handbook/engineering/posthog-com/developing-the-website) - For basic edits, go to the file in GitHub and click the edit button (pencil icon) - Open [an issue](https://github.com/PostHog/posthog.com/issues/new) or [content idea](https://github.com/PostHog/posthog.com/issues/new?assignees=andyvan-ph&labels=content&template=blog-post-idea-template.md&title=%7BContent+type%7D+-+%7Btitle%7D)

Frontend Templates Web Servers

1K Github Stars