← Templates · Monitoring & Analytics
P(
PostHog (self-hosted, core)
Community7 services
PostHog, the open-source product analytics platform — event tracking, feature flags and session replay without sending user data to a third party.
Deploy PostHog (self-hosted, core)
| Runs | 7 services |
|---|---|
| Stack | posthog-webposthog-workerposthog-pluginsposthog-dbposthog-redisposthog-clickhouseposthog-kafka |
| Provisioned for it | Nothing, it's self-contained |
| Verified | Not yet |
Why deploy on Railyard
Railyard provisions all 7 services in this stack together — posthog-web, posthog-worker, posthog-plugins, posthog-db, posthog-redis, posthog-clickhouse, posthog-kafka — wired to reach each other over the private network, on a server you already pay for.
Deploying PostHog (self-hosted, core) is one piece of a bigger stack you can keep building — add a database, a worker, a cache, or another app, all on the same servers you already pay for.
Good for
- Self-hosted product analytics, session replay and feature flags
- Keeping event data in-house instead of on PostHog Cloud
Good to know
- Postgres, Redis, ClickHouse and Kafka are all wired up automatically
- Runs 7 services at once including ClickHouse and a Kafka-compatible broker — size the server for it, not a toy instance. PostHog's own self-host docs ask for the equivalent of a 4 vCPU / 16GB RAM / 30GB+ disk machine
- Self-hosting is community-supported only — PostHog's paid-plan features stay Cloud-only, and there's no tagged-release upgrade path, so bumping the pinned commit SHA is a manual, deliberate step