Manage Storage Throughput usage
What you are charged for
On the Platform API, throughput represents the sustained data transfer capacity of AWS-backed block storage volumes and attached persistent storage, used across all workloads.
It applies to any system using provisioned storage, including:
- Database storage engines
- Background job workers with persistent volumes
- Stateful compute workloads
- Cache layers using attached storage
- Any AWS EBS-backed or equivalent block storage system
Throughput is provisioned per workload and mapped to underlying AWS storage performance configuration.
Infrastructure models:
- Silo – dedicated AWS infrastructure per tenant (isolated compute + storage throughput)
- Bridge – shared infrastructure with logically isolated throughput allocation per tenant
- Pool – fully shared multi-tenant infrastructure with pooled throughput capacity
How charges are calculated
Storage throughput is measured in MB/s-Hours (MB/s-Hrs):
1 MB/s-Hr = 1 MB/s of provisioned throughput for 1 hour
Example:
- 10 MB/s provisioned for 5 hours = 50 MB/s-Hrs
- 200 MB/s provisioned for 10 hours = 2000 MB/s-Hrs
Charges apply only to provisioned throughput above baseline allocation, where applicable.
Usage on your invoice
Throughput usage is shown as:
- Storage Throughput MB/s-Hrs
Pricing model
Throughput pricing is derived from AWS EBS performance configuration (gp3 baseline + provisioned I/O scaling) and platform orchestration overhead.
Pricing varies by storage type. The default is gp3 (AWS General Purpose SSD).
General purpose storage (gp3)
AWS gp3 provides a baseline throughput allocation with optional provisioning above that baseline.
Typical model:
- $0.00013 per MB/s-Hr (~$0.095 per MB/s per month)
- Includes baseline throughput of 125 MB/s per workload
You are only charged for provisioned throughput exceeding the baseline.
| Plan | Included Throughput | Over-Usage Pricing Model |
|---|---|---|
| Silo | 125 MB/s | AWS gp3 rate |
| Bridge | 125 MB/s | AWS gp3 rate |
| Pool | 125 MB/s (logical) | AWS gp3 rate |
| Enterprise | Custom | Custom AWS agreement |
High performance storage (io2)
AWS io2 throughput scales with provisioned IOPS and does not have a separate throughput billing component.
- Throughput is included as part of IOPS pricing
- No additional per-MB/s charge applies
| Plan | Included Throughput | Pricing Model |
|---|---|---|
| Silo | Included in IOPS | AWS io2 rate |
| Bridge | Included in IOPS | AWS io2 rate |
| Pool | Included in IOPS | AWS io2 rate |
| Enterprise | Custom | Custom AWS agreement |
Tenancy impact on throughput
Throughput behavior depends on infrastructure model:
Silo (Dedicated)
- Dedicated AWS storage + throughput allocation
- Predictable performance under sustained load
- Highest isolation
Bridge (Hybrid)
- Shared infrastructure with isolated throughput reservations per tenant
- Balanced performance and cost efficiency
Pool (Shared)
- Fully shared throughput pool across tenants
- Dynamic allocation based on workload demand
- Optimized for cost efficiency at scale
Billing examples
Baseline throughput only
No additional throughput is provisioned beyond baseline.
| Line Item | Units | Cost |
|---|---|---|
| Compute (Silo) | 730 hours | $25 |
| Compute (Bridge) | 730 hours | $25 |
| Compute (Pool) | 730 hours | $25 |
| Storage Throughput Project 1 | 125 MB/s | $0 |
| Subtotal | $40 | |
| Credits | -$10 | |
| Total | $30 |
Additional throughput provisioned
One workload exceeds baseline and provisions additional throughput.
| Line Item | Units | Cost |
|---|---|---|
| Compute (Large Workload) | 730 hours | $111 |
| Storage Throughput Project | 200 MB/s | $7.12 |
| Subtotal | $143 | |
| Credits | -$10 | |
| Total | $133 |
Multi-workload (Silo + Pool mix)
Throughput is applied per workload instance across tenancy models.
| Line Item | Units | Cost |
|---|---|---|
| Silo Compute Workload | 730 hours | $111 |
| Pool Compute Workload | 730 hours | $111 |
| Throughput Workload 1 | 200 MB/s | $7.12 |
| Throughput Workload 2 | 200 MB/s | $7.12 |
| Subtotal | $261 | |
| Credits | -$10 | |
| Total | $251 |
Key behavior notes
- Throughput applies to all stateful workloads, not just databases
- Each workload instance has its own storage performance profile
- Silo = fixed performance, Pool = shared dynamic allocation, Bridge = hybrid reservation model
- Read replicas or additional compute instances inherit storage throughput configuration unless explicitly overridden
View usage
You can monitor throughput usage in the Platform API control plane:
Organization → Usage → Storage Performance
The dashboard includes:
- Per-project throughput allocation
- Breakdown by Silo / Bridge / Pool
- Per-workload throughput consumption
- Historical performance utilization trends
Optimize usage
- Avoid over-provisioning throughput on low-I/O workloads
- Use Pool model for bursty or unpredictable workloads
- Reserve Silo throughput only for latency-critical systems
- Tune application I/O patterns to reduce sustained bandwidth needs
- Consolidate low-traffic workloads under shared infrastructure
Exceeding quotas
When throughput usage exceeds included allocations:
- Silo / Bridge / Pool (paid without caps): billed automatically based on AWS gp3/io2 pricing models
- With spend caps enabled: throughput provisioning may be limited or throttled
All billing is ultimately derived from AWS EBS performance configuration and regional pricing structures.