Documentation
How far back you can look
Ninety days is where one store ends and another begins. Which plan reaches how far, and why the boundary is there.
Ninety days is not a pricing decision dressed up as a technical one. It is where one store ends and another begins.
The hot window is answered by Analytics Engine: fast, cheap, and capped at ninety days of retention. Anything older is read from an Iceberg table in R2 over R2 SQL — exact, unsampled, real SQL — but slower, and billed by the bytes a query scans. The tiers follow that boundary rather than inventing one.
By plan
- Free
- 30 days
- Pro
- 90 days
- Scale
- 365 days — beyond ninety, queries run over the R2 lake.
The comparison period counts too
Every view compares the period you chose against the one before it. That is the product — a number on its own is not a finding.
It also doubles the window a query needs. A ninety-day range compares against days 91 to 180, which the hot store no longer holds, so the range that looks like it fits is exactly the one that does not. Reads are routed on the full span, comparison included.
Nothing is deleted
Every event is streamed into the lake as it arrives, on every plan including Free. Retention limits how far back you can query, not how much was kept — moving up a plan widens the window over data that was already there, and moving down narrows it without discarding anything.
Worth knowing
Ingest is never throttled, on any plan. A traffic spike is not a reason to stop counting, and a plan boundary is a reading limit rather than a writing one.
Realtime is the one view that never uses the lake. Active now always comes from the hot store, whatever the plan.