Skip to content

Commit 896e408

Browse files
authored
Add 'Why?' section to README
Added a section explaining the benefits of using this service as an alternative to self-hosting PostHog.
1 parent 46bba78 commit 896e408

1 file changed

Lines changed: 6 additions & 0 deletions

File tree

README.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,12 @@
44

55
An Axum-based PostHog compatible ingestion layer that forwards events to a Cloudflare Pipeline HTTP stream. The service supports the `/capture` and `/identify` endpoints so existing PostHog SDKs can drop-in with minimal configuration changes.
66

7+
## Why?
8+
9+
Posthog is a nice to use web & product analytics platform. However, self hosting Posthog is prohibitively complex so most users seem to rely on the cloud offering. This is an alternative for cost-conscious data folks & businesses interested in a low maintainence way to ingest web & product analytics directly into a managed data lake.
10+
11+
A [hobby deployment of Posthog](https://github.com/PostHog/posthog/blob/master/docker-compose.hobby.yml) includes: postgres, redis, redis7, clickhouse, zookeeper, kafka, worker, web, plugins, proxy, objectstorage, seaweedfs, asyncmigrationscheck, temporal, elasticsearch, temporal-admin-tools, temporal-ui, temporal-django-worker, cyclotron-janitor, capture, replay-capture, property-defs-rs, livestream, feature-flags, cymbal
12+
713
## Getting started
814

915
### Prerequisites

0 commit comments

Comments
 (0)