Usage and GB-hours
How account-wide runtime is sampled, calculated, warned, and reset.
Autodisc uses one runtime bank per account and billing period. Projects and services draw from the same bank.
Calculation
For each metering interval:
GB-hours = reserved memory in GB × elapsed hoursTwo 512 MB services running for one hour use approximately 1 GB-hour together. A 256 MB service running continuously for 30 days uses approximately 180 GB-hours.
Sampling guarantees
- Samples are aggregated by canonical account identity.
- Each interval has an idempotency key; duplicate delivery cannot increment usage twice.
- Concurrent services are aggregated into the same account counter.
- Long or missing intervals are capped to avoid fabricating unbounded usage.
- A new billing period starts a new counter.
Warnings and exhaustion
The usage state machine supports warnings, exhaustion, pausing, upgrade, resume, and period reset. When an account reaches its included bank, Autodisc can pause non-critical runtime. Upgrading or entering a new period allows eligible workloads to resume.
Configuration and persistent data are not deleted solely because a free account exhausts or idles its compute. Export, delete, billing, and recovery paths should remain available.
See Plans and included usage for current banks.