AI and infrastructure
Storage Billing: A Snapshot Is Not the Same as Usage Over Time
By the Orvlin team · · 2 min read
Storage gb month billing: what to decide
A customer stores a large dataset for two days and deletes it before month-end. A closing snapshot shows zero, even though storage was used. Conversely, a brief upload on the last day can overstate a full-month snapshot charge.
Define GB versus GiB and how time is integrated or sampled. State how replicas, backups and retained deleted objects affect the commercial quantity. The method should match the advertised unit.
How this works in practice
Under a simplified thirty-day normalization, storing 100 GB for fifteen days represents 50 GB-months. That illustration assumes constant storage and the stated normalization; a calendar-aware or hourly policy could need a different calculation.
What can go wrong
Low-frequency sampling can miss short-lived workloads. Choose a method appropriate to product behavior and disclose meaningful limitations rather than presenting a snapshot as precise continuous measurement.
Questions for your team
- Define byte units and time normalization.
- Specify replica and backup treatment.
- Test uploads and deletions near boundaries.
- Reconcile sampled or integrated quantities.
Frequently asked questions
- Can we bill only the last day’s storage?
- You can define such a model explicitly, but it is not equivalent to measuring storage over time and can create incentives customers exploit.