Free assessment
Part of your cloud is not serving anyone.
We tell you which part, what it costs, and in what order to remove it.
We start with 7 questions about your cloud: three minutes, nothing technical. Then you give us read-only access and, within five working days, you get a report that attributes every euro to a project, lists the resources that stop costing once removed, and puts the actions in the right order. Free, on AWS, Azure and Google Cloud.
- Free and with no commitment: no contract to sign, no surprise sales pitch.
- Read-only access only: no write permissions, no access to your data.
- At the end, half a day of work with our consultants to read it together. At our expense.
- If you are on AWS, as a partner we can discount your consumption from 8%: a saving that asks you to change nothing.
What you get
Not a dashboard to watch. A document with names, figures and an order.
The assessment is free and commits you to nothing. Your provider's console tells you how much you spent: it does not tell you who owns that spend, which part you can stop paying for this morning, and which part needs checking before anyone touches it.
Spend, attributed
Every euro assigned to a project, a team, a network. What belongs to no one stays on a visible line instead of being spread across everyone: spreading it would make every project slightly wrong and no one able to see why.
What comes back, right away
The list of resources that stop costing once removed or resized, each with its risk stated and its monthly and yearly figure. Sorted largest first, so the first three lines already pay for the read.
The order to do it in
Grouped by kind of action: nobody acts on twenty rows, they act on "delete the orphaned disks". Free moves first, then the ones needing a check. A multi-year commitment gets signed last, never first.
Beyond the obvious
Turning off the machine nobody uses is the starting point, not the work.
Anyone who opens the console finds the easy savings. The question that matters is a different one: is this resource right for the load it actually carries? The answer is not in a monthly average, and getting it wrong costs far more than it saves.
Peaks versus average
A machine averaging 6% CPU is not one to downsize if at two in the morning it runs at 95% for forty minutes. We look at the distribution and the high percentiles, not the average: cutting on the average is the fastest way to break a nightly batch.
Fit to the real load
Family and size compared with what the resource actually does: memory, network, I/O, not only CPU. A database struggling on disk inside a CPU-oversized instance costs twice and still performs badly.
Burned credits
Burstable instances living steadily above their baseline pay for credits. We measure them and keep them in a separate table, never added to the recoverable total: moving to a fixed-performance type often costs more, and calling it a saving would be a false promise.
Performance paid for twice
Volumes configured above the IOPS and throughput already included in the price, with nobody using them. It is one configuration line left over from a load test, and it is worth hundreds of euros a year per disk.
What stays on by itself
Disks attached to nothing, disks of stopped machines, public addresses allocated and never associated, gateways forgotten in a network no one uses. A stopped machine costs no compute, but its disk is paid for in full, every month.
Your rates, not list price
We do not price hours at list: we derive them from your billed cost divided by the quantities actually consumed. Anyone buying at a discount who reads list prices gets promised savings that do not exist, and then cannot find them on the invoice.
The document
Written for whoever signs, not only for whoever administers.
Every figure carries its unit, its euro equivalent at the day's reference rate, and the question it answers. No percentages without a base, no savings without the risk that comes with them.
The month and the run rate
The billed month says what you paid. The current run rate says what the fleet running right now costs per month. They are two different numbers, and confusing them is why some savings plans never add up.
The split by project
Who consumes what, attributed by tag and by network. Disks, addresses and gateways follow the machine or network they belong to, instead of landing in a pot nobody claims.
Money at risk, never added up
Items that might not be a saving sit in their own table and never enter the recoverable total. Adding them would promise a cut that does not exist, and the first invoice would prove it.
How it works
Three steps. The first takes three minutes.
We are not deciding whether you are an interesting customer. The questions tell us what to look for before we look.
Answer the questions
Which providers you use, roughly what you spend a month, who looks at costs today. Nothing technical: if you do not know the exact figure, the band is enough.
You give us a read
A read-only role over costs and inventory, or its equivalent on Azure and Google Cloud. It is there to see what exists — machines, disks, addresses, networks — not what it contains. No write permissions.
The report in five days
Five working days from access. We deliver it and read it together in the half-day of work with our consultants, at our expense. What you decide to do with it is your business.
Who does it
We wrote it on ourselves first.
The first account this assessment ran on is our own: thirty-six machines across three projects. On the first pass, at zero risk and without touching anything running, 284 dollars a month came out — 3,411 a year — in orphaned disks, disks of stopped machines and public addresses never associated.
AWS Selected Partner
Competence verified by Amazon, not a logo lifted from a marketing page. And it shows up on the invoice: on AWS consumption billed through us the discount starts at 8% and grows with volume, without touching a line of infrastructure.
Azure and Google Cloud too
The same assessment, the same report, the same five days. The service names change, the questions we answer do not. The partner discount, though, is AWS only: we have no equivalent elsewhere and we do not pretend otherwise.
Then, if you want, ongoing watch
The assessment is a photograph. With nobody watching, spend climbs back within six to twelve months: continuous monitoring is the natural sequel, and it is your choice, not an automatic one.
Privacy and access
What we ask for, and what we do not.
Read-only, on two things
Costs and inventory: machines, disks, addresses, networks, and the usage metrics the provider already collects. Without inventory half the findings disappear, because an orphaned disk has no name on an invoice.
No writes, no data
No write permissions, no access to databases, buckets or the contents of machines. We switch nothing off and resize nothing: the assessment produces a document, not a change.
Who reads the answers
The people preparing the assessment read them. We do not sell or pass on your data, and only aggregate data goes into the Osservatorio.
Deletion
You can ask for your data to be deleted at any time by writing to [email protected]. You can revoke the read-only access yourself, whenever you like, without telling us.
Contacts
Would you rather talk first?
The questionnaire is not a prerequisite for talking to us. If you would rather write or call, we answer anyway.
- [email protected]
- Phone
- +39 02 479 23365
- linkedin.com/company/oncodeit
Enterprise© 2026 Oncode S.r.l. — P.IVA IT09903240969