How Are Costs Estimated

Here's how we come up with the cost estimates

We try to make our pricing examples as comparable as possible.

Please keep in mind that our pricing examples are just that: examples. They are not meant to be a definitive cost estimate for your specific use case.

There may be additional costs that we have not accounted for, and your actual costs may differ simply due to utilization, reserved instances, discounts, and other factors.

Let's be on the same page

We use the following assumptions when estimating costs:

  • A month has 30 days (720 hours) for our estimates.
  • We don't account for discounts such as reserved or spot instances.
  • We pick the region closest to either North Virginia (USA) or Frankfurt (Germany).
  • For ease of comparison, we convert all prices to USD. We use the latest rates provided by the ECB (1.0686 USD = 1 EUR as of Jun 14, 2024).

Reference configuration

While not every provider offers every resource in the following configurations, we generally try to match them as closely as possible:

VM Small - 1 vCPU, 1 GB RAM
VM Medium - 4 vCPU, 8 GB RAM
VM Large - 8 vCPU, 16 GB RAM (prefer dedicated CPU)
Block Storage 100 GB
Object Storage 1 TB
Managed PostgreSQL 2 vCPU, 4 GB RAM, 50 GB storage
Managed Redis®* 1 vCPU, 1 GB RAM
Load Balancer, TCP, 1 Node
Serverless Functions - 25M executions
What's the free allowance for egress?
Cost for 1 TB of egress beyond the free allowance

If a provider does not offer the exact configuration, we try to match to the closest available one. For example, if a provider does not offer a machine with 16 GB of RAM, but it does offer options with 14 or 24 GB of RAM, then we'll pick the 14 GB one.

VPS Instances and Managed Containers

  • x86_64 architecture, if available
  • Linux (Ubuntu)
  • No minimum ephemeral storage

Block Storage

  • At least 100 GB of SSD storage
  • At least 3,000 IOPS, if available
  • At least 100 MB/s throughput, if available
  • No snapshots

Object Storage

  • Provider's standard storage class (no infrequent access, or reduced redundancy)
  • 1 TB of data stored
  • 100 GB of data transferred in
  • 250 GB of data transferred out
  • 1,000,000 GET requests
  • 100,000 PUT or POST requests
  • 1,000 lifecycle transition requests

Managed PostgreSQL

  • 1 node, 2 vCPU, 4 GB RAM
  • At least 50 GB storage
  • No replication
  • No minimum backup retention
  • 10 GB read per month
  • 5 GB written per month

Managed Redis®*

  • 1 node, 1 vCPU, 1 GB RAM
  • 10 requests per second
  • 1 KB average request size

Load Balancers

  • TCP protocol
  • At least 1 node, 1 vCPU, 1 GB RAM
  • At least 200 Mbps throughput
  • 1,000 new connections per second
  • 1 second average connection duration
  • 1 TB data processed per month
  • 3 targets, 3 rules

Serverless Executions

  • 25M invocations
  • 150 ms of execution time
  • 512 MB of memory

Egress / Outbound Data Transfer

  • 1 TB of data transferred out per month
  • The destination region is the same as the source region (either US East or EU Central, see assumptions above)
  • Using the provider's default network class
  • No free tier allowances or discounts