Change history

PostHog limit changes

Current and previous observations remain linked to their official sources. Detection date and effective date are kept separate when known.

Verified Aug 22, 20260 verified changes

Verified history

No verified historical change is recorded yet.
This means HyperObserve has not found sufficient first-party evidence for a dated before-and-after event. It does not mean PostHog has never changed. Undated values are kept in the current baseline below instead of being presented as history.

Current monitored baseline

HyperObserve currently monitors 4 scoped observations for PostHog. The baseline covers monthly analytics events, monthly recordings, monthly flag requests, monthly warehouse rows. Each value retains its plan, product, endpoint, region, account, or runtime qualifier so a future change can be compared against the correct scope.

ConstraintCurrent valueScopeVerified source
monthly analytics eventsUsage beyond the free allocation follows volume pricing.1 million events per monthCloud free tierPostHogAug 22, 2026
monthly recordingsReplay is metered separately from product analytics events.5,000 recordings per monthCloud free tierPostHogAug 22, 2026
monthly flag requestsFeature flag requests have their own usage meter.1 million requests per monthCloud free tierPostHogAug 22, 2026
monthly warehouse rowsWarehouse rows are metered separately from events, replays, and flag requests.1 million rows per monthCloud free tierPostHogAug 22, 2026

Tracked constraints and impact

Product analytics, replay, feature flag, and warehouse monthly free tiers. A change is recorded only when it alters a constraint developers can act on, such as capacity planning, request shaping, model selection, deployment configuration, storage design, retry behavior, or account budgeting.

How a change is verified

  1. Compare the current first-party statement with the previously stored observation, including the exact plan, model, runtime, endpoint, region, and account scope.
  2. Separate a true product change from documentation clarification, temporary capacity, configurable account state, or a limit that applies to a different execution path.
  3. Preserve the old and new values, official source, effective date when disclosed, detection date, and practical impact. If those elements cannot be supported, no historical event is published.

Official sources monitored

These first-party documents support the current PostHog baseline. HyperObserve links directly to them so you can confirm the live wording before making a production decision.

PostHog usage-based pricing

Product analytics, replay, feature flag, and warehouse free tiers

Related

Continue researching PostHog