Direct volume uses the mixed-estate mean event size. If you know your source mix, the estate builder is more accurate — the two modes differ most on Windows and cloud JSON.
Planning levers
Peak and growth size the hardware; retention sizes the storage you buy.
The other dimensions your estate implies
Counted from what you typed, plus one honest input. These lines meter on their own dimensions and have no published rate — so this page counts them and does not price them.
Your estate Live rate card
On SaaS (we host it)
Ingestion above the Cloud allowance is charged per GB/day at your rate card, averaged across the billing window — a one-day spike never shocks the bill.
Region-pinned pooled cell by default; dedicated single-tenant cells (own VPC, PrivateLink) for regulated estates — the deployment-models note is not published yet; ask us for it.
On-premise (you host it)
—
Assumptions & constants (v2 · 2026-09-01 — planning defaults, measured where marked)
| Event size (wire, raw ON / OFF) | 1,475 / 903 B measured |
| Event size (stored v2, raw ON / OFF) | 1,047 / 538 B measured |
| Per-family sizes in inventory mode | measured per source family |
| Compute | 1,500 EPS / vCPU (+2 floor, min 4) |
| RAM | 8 GB + hot-window (3.5 KB/event) + 2 GB/10k EPS |
| Disk overhead / archive compression | ×1.44 / ÷3 (gzip measured 4.3×) |
| Per-Core-node planning envelope | 10,000 avg EPS → shard into cells |
| Platform's own events | +3 % EPS |
| Boot-replay rate (RTO math) | 5,000 events/s measured (real boot, derated) |
Constants are measured on the real event + sealed segment-store path and mirror the platform's own sizing & capacity guide §12; the published reference set is listed on Resources. The formal per-node capacity target is an open engineering ratification — these defaults deliberately derate measured ceilings. Not legal advice; your compliance team owns the retention period.
Scope & Honest Limits Four planning boundaries on this calculator Expand · Full ledger →
The per-event sizes are measured, the events-per-second defaults are judgement. Two estates with identical hardware can differ widely on audit policy alone.
This gives you the volume, not the amount. The platform line’s prices are on the pricing page; the other product lines are quoted against your own figure.
One Core node is planned to about 10,000 average events per second. Past that the calculator divides the estate into identical cells.
The archive figure is compressed roughly threefold and holds the balance of your compliance period beyond what stays searchable on the node. Where it lives, and what restoring from it takes, are yours to plan.