Cloud Cost Optimization

A cloud bill
your teams can read

We give every cloud cost an owner and size each resource to what it uses, so each team can see what it spends, and why.

Thanks, we’ll be in touch soon.

{{ heroStatus }}

{{ heroSay }}

You’re in good company

A few of the companies we’ve worked with.

{{ wallSay }}

What the bill doesn’t say

A cloud bill says what was charged, not who it was for or whether it was needed. It arrives after the money is spent, often as one total for the whole company. Some of it pays for things nobody uses any more: a disk left behind when its server went, copies of data kept with no end date, a test copy still running after its project ended. None of them carries a name, so no one is asked about them.

Still charged, and each with no owner:
  • A disk from a server that’s goneOwnernone
  • Snapshots with no end dateOwnernone
  • An address nothing usesOwnernone
  • A test copy from a finished projectOwnernone

What we do

Cost work done as engineering, in your code and your accounts.

  • Every cost with an owner

    Each resource carries labels, a name and value for its product, team and environment, set by a policy, so new ones arrive labeled.

  • Shared costs, split fairly

    Clusters, databases and networks that teams share, split among them by a rule each team has seen.

  • A view each team reads

    Costs by product, team and environment, with a budget for each and an alert to its owner when spending moves from its usual pattern.

  • Sized to what’s used

    Servers, databases and containers sized from measured use, with room kept for your busiest times.

  • Off when no one needs it

    Test and staging copies stopped outside working hours, and what nobody uses removed once its owner agrees.

  • Storage that ages

    Files and snapshots moved to slower storage as they age, and deleted when your rules say. Logs and backups are kept as long as those rules ask.

  • Commitments that fit

    Agreements to pay for a set amount of use over a term, in return for a lower price, sized to the use that’s steady, renewed or let go as it changes, and checked each month for what went unused.

  • Traffic where it costs

    Data can be charged as it moves: between zones, between regions and out to the internet. We find where yours is, then place or cache it so less of it travels.

  • Cost shown before it’s spent

    Where your systems are written as code, each change that adds servers or storage shows an estimate of what it adds to the monthly cost in its review, before it’s merged.

Moving systems to the cloud, or between clouds? Cloud Migration →

Releases, security and day-to-day running? Cloud, DevOps & Security →

What each use of an AI feature costs? AI Product Engineering →

What one order costs to run

A bill that grows can be good news, if the business grows faster. So beside the total, we measure what one unit costs to run. A unit is one of whatever your business does many times: an order, a customer, a report or a search. When the cost of one stays level or falls as you grow, your systems are growing well. When it rises, the parts behind it show where.

One order followed through what it uses, in an example:

One orderAn example

  • The website, for a moment
  • A few reads and writes in the database
  • One email
  • A share of what’s shared

The cost of one order

The invoice and the cost aren’t the same

A commitment can be paid in full at the start, month by month, or part each way. Paid in full, it changes how the bill reads. The invoice shows the payment once. The cost of what runs carries it month by month, including any part your systems didn’t use.

An exampleA commitment paid in full when it’s bought

The months of the term, in order, from its start to its end.

Invoice

  • Paid when bought
  • Nothing
  • Nothing
  • Nothing
  • Nothing
  • Nothing
  • Nothing
  • Nothing

Cost

  • Used
  • Used
  • Used
  • Used
  • Used
  • Used, and part not used
  • Used, and part not used
  • Used

Paid in full, a commitment shows on your invoice once, in the month you pay for it. The cost of running each thing spreads that payment across the months it covers.

A month where less ran still carries its share. The part nothing used shows as a cost with no work behind it.

So we read both: the invoice, for what you pay and when, and the cost, for what each product and team uses, and what went unused.

Billing data from several clouds can follow one common format (the FOCUS™ specification), so a cost means the same thing wherever it ran.

FOCUS is a trademark of Joint Development Foundation Projects, LLC.

Start with one bill

We begin by reading a recent bill and what runs behind it: what each cost is for, who it belongs to, what’s still needed, and what’s paid for and not used. You get a written plan: every cost with an owner or a question, the changes in the order we’d make them, with what each one changes and asks of your team, and the first change made with you, so the way is tried before the rest.

We read your billing and usage data, and make changes only through your team’s usual review, one at a time. Each change is recorded, watched after it’s made, and reversed if it needs to be.

Work with us as a dedicated team, on a fixed price project or a mix of both. Compare engagement models →

How each is paid for: Pricing →

A first change, in an example:

First changeMade with you

Before
A test copy, running all week
After
The same copy, running in working hours
Owner
Checkout team, agreed

Questions worth asking

How much will we save?

We don’t promise a figure before we’ve read your bills and what runs behind them. After the first look, the plan sets out what each change would change in your monthly cost, estimated from your own use, so you decide with your own numbers in front of you.

Will it make our systems slower or less reliable?

Not if each change is made from measured use, with room kept for your busiest times. Nothing is resized or stopped until its use has been measured through a full cycle of your business. We make one change at a time, through your team’s usual review, watch it after it’s made, and reverse it if it needs to be.

What happens to data nobody seems to use?

Nothing, until its owner agrees. Nothing is stopped, removed or deleted without that, and data is kept or deleted as its owner decides. Where no owner can be found, it goes into the plan as a question, with what it costs to keep.

Should we buy commitments?

For use that’s steady, often yes, once each cost has an owner and what runs is sized to its use. Buying first locks in today’s use, including what you don’t need. You buy them, in your own accounts, under your provider’s terms, which we read with you. We size each one to the use that’s been steady, set out what it locks in before you buy, and check each month what went unused.

Can you bring several clouds into one view?

Yes. We bring each cloud’s costs into one view, in the same terms, so a team reads its costs the same way wherever they run.

What about the cost of AI features?

What each use of a feature costs to run is set as a limit before launch: AI Product Engineering → We bring those costs into the same view, by product and team.

Is this what’s called FinOps?

Yes. That’s the name for the wider practice: engineering, finance and business teams sharing what technology costs, the cloud included, and deciding together. We do the engineering part of it, for the cloud, with whoever owns the budget.

Who keeps it going afterward?

Your team, with us or without. We can review costs with you on a regular rhythm, as part of running your systems, or hand the work over to your team, with the view, the rules and the knowledge behind them. Cloud, DevOps & Security →

What does this work cost?

It depends on how much you run and how it’s organized today. The first call is free. Your proposal sets out the scope, the price or rate, and how you pay, before any work starts. Pricing →

Let’s run it better

Tell us what your cloud bill looks like today. We’ll suggest where to look first.

Thanks, we’ll be in touch soon.

{{ ctaStatus }}