Cloud costs for a start-up: how do you make them predictable?
Cloud costs consist of several items; with a simple calculation model and a few agreements you can keep them predictable.
Cloud costs become predictable once you know what items they consist of: compute, storage, data traffic and additional services. Calculate each item as units times rate, set a budget alert and review every month what deviates from your expectation.
Who is it for: Founders and small teams who use infrastructure (servers, storage, hosting) and want to get a grip on the bill.
What cost types make up a cloud bill?
This article is about cloud as infrastructure: servers, databases and object storage. For cloud as a file service for collaboration, the cost structure works differently, usually per user.
With infrastructure, you pay for what you use. A bill usually consists of four groups.
- Compute: the time servers or containers run, often depending on their size.
- Storage: the number of GB you keep, sometimes with a difference between fast and slow storage.
- Data traffic: mainly data leaving the environment, known as egress, which can weigh heavily.
- Additional services: backups, monitoring, load balancers, fixed IP addresses and support.
How do you build a calculation model without surprises?
A model does not have to be complicated. The aim is that for each item you can explain why the amount is roughly what it is. An example: storage in GB times the rate per GB, plus the number of requests times the rate per request, plus outbound traffic in GB times the rate per GB.
Fill in the units with your own estimate and then calculate with a favourable, an expected and a busy scenario. The difference between those scenarios shows which item contains the greatest uncertainty.
- For each service, note which unit is measured and what the rate per unit is.
- Estimate your usage for a quiet, a normal and a busy month.
- Calculate the three scenarios and mark the item with the widest spread.
- Set a budget alert for that item and record who receives the alert.
Which costs are often forgotten?
Unused environments are the most common cause of unnecessary costs: a test server that keeps running or storage from a finished trial. Data traffic between regions or to the internet also often only becomes visible with the first bill.
In addition, your own time counts. A cheaper service that requires a lot of management costs the team hours you would otherwise have spent on the product.
Which agreements help in a small team?
Give every environment an owner and a label for project or purpose, so you can see on the bill where costs come from. Schedule a fixed moment each month to hold the bill up against your model. In case of a deviation, first find the cause and only then the solution.
Cost types and their predictability
| Cost type | How it is built up | How do you control it |
|---|---|---|
| Compute | Run time times rate for the server size | Switch off test environments outside working hours |
| Storage | GB times rate per GB | Clear out outdated data and copies |
| Data traffic | Outbound GB times rate | Check rates in advance and cache where possible |
| Additional services | Per service and per unit | Only switch on what you use |
Who is it not ideal for?
- Teams with fixed, small usage: a fixed hosting price per period is then simpler than usage-based rates.
- Anyone without time for a monthly check: choose a provider with fixed plans or outsource the management.
- Companies with large, fluctuating volumes: a simple model is not enough and you need targeted cost monitoring.
Frequently asked questions
What is a budget alert?
A setting at the provider that warns you as soon as costs approach a limit. It does not stop spending by itself, unless you configure that separately.
Is pay-as-you-go cheaper than a fixed plan?
Not necessarily. It depends on how stable your usage is. With a stable profile, a fixed plan can turn out more predictable and more cost-effective.
When does data traffic become a problem?
When you send a lot of data to users or other systems. Ask the provider which rates apply to outbound traffic and whether there is a free allowance.
