Quick answer
PostHog documents monthly warehouse rows as 1 million rows per month. Warehouse rows are metered separately from events, replays, and flag requests.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| monthly warehouse rowsWarehouse rows are metered separately from events, replays, and flag requests. | 1 million rows per month | Cloud free tier | PostHogAug 22, 2026 |
Why does this limit matter?
A broad high-frequency source sync can consume rows without improving the queries that matter.
This value is scoped to Cloud free tier; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Estimate rows by source, table, sync interval, and incremental strategy.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- Pricing and the name of the warehouse product can evolve; verify the current official table.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related