Skip to main content

Manage Disk Usage

What you are charged for​

On the Platform API, disk usage represents all persistent block storage allocated to a project.

This includes:

  • Database data files
  • Write-Ahead Logs (WAL)
  • Background job storage and internal state
  • Runtime persistent volumes used by compute workloads
  • Any attached or provisioned AWS block storage (EBS volumes)

Each project runs on AWS-backed infrastructure using one of the following tenancy models:

  • Silo – dedicated infrastructure per tenant (isolated compute + storage)
  • Bridge – shared infrastructure with logically isolated storage per tenant
  • Pool – fully shared multi-tenant infrastructure with segmented storage allocation

Disk usage is always measured at the project level, but physically maps to AWS block storage (EBS) volumes and attached storage used by both database and compute layers.

How charges are calculated​

Disk usage is billed based on provisioned AWS storage capacity, not actual data stored.

Billing is measured in Gigabyte-Hours (GB-Hrs):

1 GB-Hr = 1 GB of provisioned storage for 1 hour

Example:

  • 10 GB provisioned for 5 hours = 50 GB-Hrs
  • 20 GB provisioned for 10 hours = 200 GB-Hrs

Charges accrue continuously while storage is allocated to a running or active project.

Usage on your invoice​

Disk usage appears as:

  • Disk Usage GB-Hrs

Pricing model​

Disk pricing is based on AWS EBS storage pricing, plus Platform API overhead for:

  • Multi-tenant isolation (Pool / Bridge)
  • Dedicated provisioning (Silo)
  • Storage orchestration and lifecycle management

Pricing varies by disk type. The default is gp3 (AWS General Purpose SSD).

General purpose disks (gp3)​

AWS-based gp3 pricing (region dependent):

$0.000171 per GB-Hr ($0.125 per GB per month)

Each project includes a baseline allocation of 8 GB of provisioned storage covering minimal system and database requirements.

You are only charged for usage beyond this baseline.

PlanIncluded StorageOver-Usage Model
Silo8 GBAWS gp3 rate
Bridge8 GBAWS gp3 rate
Pool8 GB (logical)AWS gp3 rate
EnterpriseCustomCustom AWS rate

High performance disks (io2)​

AWS-based io2 pricing (region dependent):

$0.000267 per GB-Hr ($0.195 per GB per month)

io2 volumes are billed from the first provisioned gigabyte, with no included baseline.

PlanIncluded StoragePricing Model
Silo0 GBAWS io2 rate
Bridge0 GBAWS io2 rate
Pool0 GBAWS io2 rate
EnterpriseCustomCustom AWS rate

Tenancy impact on disk usage​

Disk behavior differs depending on infrastructure model:

Silo (Dedicated)​

  • Dedicated AWS volumes per tenant
  • Strong isolation of storage and compute
  • Predictable performance under load

Bridge (Hybrid)​

  • Shared infrastructure with isolated AWS volumes per tenant
  • Balanced cost and performance
  • Efficient storage pooling at infrastructure level

Pool (Shared)​

  • Fully shared storage infrastructure
  • Logical isolation enforced at platform layer
  • Optimized for cost efficiency at scale

Billing examples​

gp3 disks​

Only usage above the included baseline (8 GB per project) is billed.

Line ItemUnitsCost
Silo Compute Node730 hours$25
Bridge Compute Node730 hours$25
Pool Compute Node730 hours$25
Disk Project 18 GB$0
Disk Project 28 GB$0
Disk Project 350 GB$X.XX
Subtotal$75
Credits-$10
Total$65

io2 disks​

io2 volumes are billed from the first GB provisioned.

Line ItemUnitsCost
Silo Compute Node730 hours$25
Bridge Compute Node730 hours$25
Pool Compute Node730 hours$25
Disk Project 18 GB$X.XX
Disk Project 28 GB$X.XX
Disk Project 350 GB$X.XX
Subtotal$82.87
Credits-$10
Total$72.87

View usage​

You can monitor disk usage in the Platform API control plane:

Organization → Usage → Storage

The dashboard provides:

  • Per-project storage breakdown
  • Tenancy model breakdown (Silo / Bridge / Pool)
  • AWS-backed storage allocation metrics
  • Historical growth tracking

Disk usage breakdown​

Disk usage is categorized based on AWS storage allocation:

  • Database storage (data files)
  • Write-Ahead Log (WAL)
  • Compute-attached persistent volumes
  • System and metadata overhead

This reflects how AWS EBS volumes are actually utilized across database and runtime layers.

Optimize disk usage​

To reduce AWS storage costs:

  • Right-size provisioned storage per workload
  • Remove unused indexes and large historical data
  • Archive cold data to object storage (S3)
  • Monitor WAL growth in write-heavy systems
  • Reduce persistent volume usage in compute workloads
  • Clean up unused environments and ephemeral workloads

Exceeding quotas​

When disk usage exceeds included allocations:

  • Silo / Bridge / Pool (paid without spend caps): billed automatically at AWS EBS rates
  • Paid plans with spend caps enabled: usage may be throttled or blocked with alerts

All overages are directly tied to AWS storage pricing in the selected region, plus Platform API orchestration overhead.