← Docs|Pricing Methodology

Pricing Methodology

How we calculate costs using real cloud pricing from AWS, GCP, and Azure.

Resource Pricing

Conservative averages across AWS, GCP, and Azure

ResourcePer HourPer MonthNotes
Memory$0.01/GB$7.20/GBBased on on-demand pricing
CPU$0.03/vCPU$21.60/coreBased on on-demand pricing
Storage-$0.10/GBEBS gp3 / PD-SSD average
Load Balancer-$20.00ALB / NLB / Cloud LB base cost

Calculation Example

Let's walk through a real example of how waste is calculated:

Scenario: Over-Provisioned Pod

resources:
requests:
memory: 500Mi
cpu: 100m
limits:
memory: 2Gi # 4x over
cpu: 500m # 5x over

Memory Waste

Limit: 2048 MB
Request: 500 MB
Safe buffer (1.5x): 750 MB
Waste: 1298 MB (1.27 GB)
Cost: 1.27 GB × $7.20 = $9.14/month

CPU Waste

Limit: 500m (0.5 cores)
Request: 100m (0.1 cores)
Safe buffer (1.5x): 150m (0.15 cores)
Waste: 350m (0.35 cores)
Cost: 0.35 × $21.60 = $7.56/month

Total Waste for This Pod

$9.14 + $7.56 = $16.70/month
× 12 months = $200.40/year

Why 1.5x buffer?

We assume you need some headroom above requests for traffic spikes. A 1.5x buffer is industry standard.

Why These Prices?

Our pricing is based on on-demand, pay-as-you-go rates averaged across AWS EC2, GCP Compute Engine, and Azure Virtual Machines.

Sources

  • AWS: Based on t3/m5 instance pricing (most common for K8s)
  • GCP: Based on n1/n2 standard machine types
  • Azure: Based on D-series VMs

These are conservative estimates. Your actual costs may be higher (spot/preemptible instances could be lower).