Cloud billing stops at the machine
AWS Cost Explorer and Azure Cost Management bill you per resource. On a box with sixty virtual hosts they see one line item, not sixty customers.
For teams running infrastructure for other people
Know what each client
actually costs you.
ContCost allocates the cost of shared servers, containers, databases, storage and support hours to the clients who consume them — so you can price contracts on real numbers instead of on a feeling.
Your bill says one server.
Your business has sixty clients.
Every tool on the market can tell you what a resource costs. None of them can tell you which client is eating it.
Kubernetes tools need Kubernetes
Kubecost and OpenCost allocate beautifully — per pod, per namespace, per label. Most agency infrastructure is virtual hosts, containers and shared databases, so none of it applies.
Agency tools count people, not machines
Time and resource planning tools allocate human hours. The disk, the database and the bandwidth that client has been quietly growing for three years appear nowhere.
So the client paying €30 a month while consuming like one paying €300 stays invisible — until renewal, when you discover the contract has been losing money for two years.
How it works
Boxes and numbers, with the right criterion. Three steps, and the third is the one you actually want.
-
1
Send your resources
Push them through the API, let the agent report them, or type them into the console. A virtual host, a container, a database, gigabytes of backup, a support ticket — anything you can count is a resource, monetary or not.
-
2
Attach costs and allocate
Give each resource its cost, then allocate it by customer, project or phase with the criterion you choose — evenly, by consumption, by weight. You decide the rule; ContCost applies it consistently.
-
3
See margins, then forecast
Cost views per client show where the money actually goes. Build scenarios before you commit to a price, schedule reports, and get alerted when a client's consumption starts drifting away from what they pay.
Things people allocate with it
- Virtual hosts
- Containers
- Databases
- Storage & backup
- Bandwidth
- Licences
- Support hours
- Anything you can count
Who it's for
One thing in common: you run infrastructure that several clients share, and nobody can tell you the cost per client.
Web agencies with managed hosting
When contracts come up for renewal
Ten to a hundred sites on a handful of servers. You know the total bill and the total revenue, never the margin on the individual client.
MSPs and hosting resellers
When moving off list pricing
You want to price on what a client really consumes, and to show them the numbers when the price goes up.
Multi-tenant SaaS teams
When one tenant starts hurting
Aggregate margin looks fine. Margin per tenant is the number that tells you which plan is mispriced and which account to renegotiate.
Small providers and local data centres
When costs rise and clients ask why
Energy, hardware and licences move. Passing that on is a conversation you win with allocation you can defend.
Where ContCost is today
Straight answer, because you would find out anyway. ContCost started in 2020 as a cost console and has been running since as an internal tool at Glacom, tracking time and cost per customer, project and phase across our own shared infrastructure — dozens of client sites on a handful of servers. We are opening it up to the people who kept asking us how we do it.
That means early access, not a self-serve signup: we set it up with you, on your infrastructure, and we are shaping pricing with the first users. If you want polish and a credit-card form, wait a bit. If you want the number for your clients this quarter, write to us.
Tell us what you run
How many clients, on what kind of infrastructure, and the number you wish you had. We answer to everyone.
- Telephone +44 7835 323770
- WhatsApp +44 78353 23770