Summary pending. The diff below shows exactly what changed.
What changed
Struck in red is what PostHog removed; blue is what they added. Muted text is unchanged context.
BeforeAfter
Changed#1
Before: …year Email support – or Slack over $2k/mo Each product gets its own billing limit - going viral won't require…
After: …year Email support – or Slack over $2k/mo Most products get their own billing limit - going viral won't require…
Changed#2
Before: …product (resets monthly) You can set billing limits per product so you never get a surprise bill We…
After: …product (resets monthly) You can set billing limits on most products so you never get a surprise bill We…
Changed#3
Before: …for stored data (events, exceptions, replays, logs, etc.)? No, for all of our products pay for what you capture, ingest, or sync…
After: …for stored data (events, exceptions, replays, logs, etc.)? Not for most products. You pay for what you capture, ingest, or sync…
Changed#4
Before: …you capture, ingest, or sync in a given month (i.e. you only pay when each event is first received). There are no additional storage costs or fees. How long does PostHog retain data (events, recordings,…
After: …you capture, ingest, or sync in a given month, and storing it costs nothing extra. The exception is Logs custom retention: if you keep logs or traces longer than the 14-day default, each GB costs $0.05 for every month you keep it. How long does PostHog retain data (events, recordings,…
Changed#5
Before: …can set custom retention per service or per source at $0.05/GB per month retained. What happens after the data retention period elapses?…
After: …can set custom retention per service or per source. Custom retention bills for the data you keep, not this month's usage: each GB costs $0.05 for every month you keep it, until it expires. Your Logs billing limit stops ingestion but doesn't cap custom retention, and custom retention can't have a limit of its own. What happens after the data retention period elapses?…
Added#6
Before: …use. Unused free tier limits do not rollover. nothing here Can I set a billing limit? Yes, you…
After: …use. Unused free tier limits do not rollover. Logs custom retention has no free tier. It bills for the data you keep, not this month's usage. Can I set a billing limit? Yes, you…
Changed#7
Before: …Yes, you can set a billing limit for each of PostHog's products separately in your organization's billing…
After: …Yes, you can set a billing limit for most of PostHog's products separately in your organization's billing…
Added#8
Before: …products separately in your organization's billing settings . nothing here Check out our doc on billing limits and…
After: …products separately in your organization's billing settings . Logs custom retention can't have a limit, and your Logs limit doesn't cap it. Check out our doc on billing limits and…
Added#9
Before: …than what you've set as your billing limit. nothing here How is usage calculated? Usage is calculated on…
After: …than what you've set as your billing limit. The exception is Logs custom retention, which your Logs limit doesn't cap. How is usage calculated? Usage is calculated on…
Changed#10
Before: …surveys, synced rows for sources, messages for workflows, and GB ingested for logs. How can I manage my spend? You monitor…
After: …surveys, synced rows for sources, messages for workflows, GB ingested for logs, and GB-months kept for Logs custom retention. Do multiple projects share usage and free allowances? Yes. Billing is organization-wide, so usage from all your projects is combined into one bill with one free allowance. Adding projects doesn't add extra free usage. The free plan includes one project, and paid plans include more. See how to organize projects for our recommended development, staging, and production setup. How can I manage my spend? You monitor…
Added#11
Before: …and we'll only charge for what you use. nothing here If you have an accidental spike , talk…
After: …and we'll only charge for what you use. Billing limits don't cap Logs custom retention. If you have an accidental spike , talk…
Amounts removed: none; added: $0.05.
Compared with the previous archived version (#3713 to #4471). Text is normalized before comparing: dates, counters and tokens show as ‹date›, ‹count›, ‹tok›, and noise-only edits are hidden. Rewindex shows changed passages with a few words of context, not a copy of the page. View the live page (opens in new tab).
Archive proof
Rewindex commits each page capture it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
PostHog’s pricing-page navigation replaced “Self-driving product” and “Context warehouse” with “MCP” and “Self-driving” in two menus. The diff shows navigation wording only, with no pricing or plan changes.