PostHog moves warehouse from ClickHouse to per-org DuckDB instances

PostHog moved its managed warehouse off a shared multi-tenant ClickHouse cluster to a dedicated DuckDB instance per organization. Data lives in S3 via DuckLake, instances spin up on demand and sleep when idle, and a Postgres wire endpoint handles connections. Event analytics stays on ClickHouse.

• Each organization gets a dedicated DuckDB worker with no shared query queue
• Storage uses Parquet in S3 via DuckLake with a transactional SQL catalog
• The feature is in beta behind a waitlist with no published benchmarks
• Event analytics remains on the shared ClickHouse cluster