29 August 2026

What Per-Gigabyte Billing Does to Your Coverage

When the invoice scales with what you collect, teams quietly stop collecting. The gap always shows up during an incident.

Ask a security team what they stopped logging last year and you will usually get an answer. Debug output from the firewall. DHCP. Switch counters at full resolution. Nobody decided these were unimportant. They were expensive. That is what volume-based pricing does. It puts a meter on the one behaviour you want to encourage. Every engineer who proposes broader collection is also proposing a bigger invoice, and they know it before they open their mouth. The filtering happens early, quietly, and nobody writes it down. Then an incident arrives, and the window you need is the window somebody trimmed eight months ago to hit a budget. We price per institution. Collect everything your estate produces and the number does not move. This is not generosity, it is the only model that makes sense for a platform that runs on your own hardware. There is no metered service on our side to pay for. The honest caveat: storage is not free just because the licence is. More retention means more disk, and we will size that with you rather than let it surprise you. But disk is a known quantity your team can plan for, and it does not require a procurement cycle to change. If your current tool has taught your engineers to think twice before logging something, that is worth noticing. It is a habit that costs nothing until the day it costs everything.
procurement logging