Success-based FinOps · Free assessment
Success-based FinOps: we charge on verified savings
We get read-only permissions on AWS, Azure or Google Cloud, look at what you pay for and why, and explain what to decide first. Without touching anything in your infrastructure.
If your account qualifies, the assessment is free. We only proceed to implementation if we find savings and you accept the terms in writing.
This offer starts at aggregate cloud spend of at least €8,000 per month (excluding VAT).
01 · Who it is for
Who a FinOps audit is for (and who it is not)
It is a review of how you spend on the cloud to understand what you pay for and what could be adjusted (FinOps, cloud financial management). Here we do it with read-only access and prioritise by risk.
It fits if
- Your aggregate cloud spend is at least €8,000 per month, excluding VAT, and you want to implement improvements if savings are found.
- Your cloud spend grows every month and nobody reviews it on a regular basis.
- Your spend is spread across several accounts, subscriptions or projects and nobody sees the whole picture.
- You want to decide with evidence what to touch first and what to leave as it is, without improvising in production.
Better another option if
- Your spend is below the minimum or potential savings do not justify the engagement. This offer is not designed for small accounts.
- You already have a FinOps team with its own tools and review processes in place.
- You want to cut spend without changing anything: the audit on its own does not apply changes.
Signs you need a cloud cost audit
- The cloud bill goes up every month and nobody on the team can explain why.
- You pay for resources you are not sure you use, such as test environments, loose disks or servers from old projects.
- Finance asks for figures by team or product and technology answers with estimates.
- You are offered reservations or usage commitments in exchange for a better price and do not know whether they suit you.
- Touching production to save money worries you, because you do not know what could break.
02 · Scope
What we analyse and what you receive
Rightsizing
We compare the size of servers and databases with their real CPU, memory and I/O usage over a representative period.
Reservations and usage commitments
We assess whether committing to a level of usage in exchange for a better price is worth it, and what risk you take on. Each cloud names them differently: Savings Plans and Reserved Instances (AWS), Reservations and Savings Plan (Azure), committed use discounts (Google Cloud).
Storage
We look for disks, backups and logs that pile up unused, and we review retention.
Data transfer
We review what you pay for traffic: egress to the internet and movement between availability zones or regions.
Test environments
We detect test environments left running at night and on weekends that could be switched off on a schedule.
Licences
We review software licences, such as Windows Server or SQL Server, that you could bring under your own licences (BYOL, Azure Hybrid Benefit).
Kubernetes
If you use Kubernetes, we look for pods that request more CPU and memory than they consume (oversized requests).
Cost governance
We organise spend: resource labelling (tagging), budgets and cost-anomaly alerts, so you can see who consumes what.
What you receive
- Starting monthly spend, by service and account where the data allows, and a projection for comparing options.
- Potential savings report by applicable option, with its distribution across resources and accounts, risks and conditions.
- Options without commitments and options with reservations or Savings Plans, stating duration, cost and commitment. You decide whether to commit to long-term usage.
- A review of the report with you to decide whether to proceed. The assessment does not include commands, code or steps to implement savings; execution and its documentation belong to the agreed implementation phase.
Our CTO Leafar Maina’s experience
Before Nubyron, Leafar saved €2,000 in one month on an account billed at €4,000 a month with excess infrastructure in non-production environments. On another billed at around €14,000 a month, he saved over €6,000 in a month and a half. These are examples from his previous experience, not a forecast for your account: results depend on usage and the options you accept.
03 · Process
How the process works
- Eligibility, agreement and access. We review average spend over the last three months and usage context. If eligible, we sign off the free assessment scope and success-based terms. You then give us a read-only role for costs, billing and configuration with minimum permissions. We do not ask for access to the content of your data or secrets.
- Audit and report. We present potential savings by option, resource and account where the data allows. We separate measures without commitments from those requiring reservations or Savings Plans. The report does not include implementation instructions.
- Implementation and measurement. We only implement if we find viable savings and you decide to proceed. Before changing anything, we sign off the percentage, baseline, actions and measurement. Nubyron applies approved improvements in stages and checks the results on your invoices.
- Close. We remove the access with you at the end and confirm it to you in writing.
How savings are verified
- Success means recurring savings realised and verified on the agreed invoices, attributable to approved actions and adjusted to the same workload and scope. We do not charge on estimates or project annual savings to bill them upfront.
- One-off savings, such as a refund or exceptional credit, are excluded unless specifically agreed in writing. Recurring savings are counted only in the agreed period and are not counted again as one-off savings.
- We start from the last three months of invoices and agree a baseline and its projection before implementing anything. We agree how to adjust workload, seasonality and scope changes so that lower usage is not mistaken for savings we achieved.
- Discounts you already had (credits, negotiated prices, existing reservations) are part of the baseline and do not count as savings.
- Changes in the provider’s pricing and savings you already had under way before we started do not count either.
- New commitments are only purchased if you accept them. The proposal explains how their discounts, upfront payments and implementation costs are accounted for when verifying savings.
- Each saving is tied to a specific action and checked on the bill.
04 · Security
Read-only access and security
- A read-only role for costs, billing and configuration, created by you with minimum permissions. We agree the exact role with you.
- AWS: an assumable IAM role with an external ID (ExternalId) unique to you.
- Azure: roles that read costs and resources. Google Cloud: read access to billing and resources.
- We neither need nor ask for access to the content of your data or your secrets. If we see a secret in a configuration, we do not copy it and we tell you so that you can rotate it.
- At the end, we remove the access with you and confirm it in writing.
05 · Terms
How we charge: success fees
First we check whether there are savings. Then we implement and charge on verified savings, with terms signed before starting.
Free assessment for eligible accounts
We review spend read-only and deliver a potential savings report. We first check monthly spend, scope and whether the account qualifies for this offer.
Success fees
If we find savings and proceed, we charge a percentage of realised savings verified on your invoices. The percentage and measurement period are signed off before making changes.
- The assessment is free for accepted accounts. If we find no viable savings, we close the review without proceeding to implementation or charging for the assessment.
- We do not offer success-based work for small accounts. Beyond the minimum spend, we assess whether potential savings justify the work for both parties.
- Fees are calculated on realised savings, not the potential shown in the report or your entire cloud bill.
- We use the first two complete invoices reflecting the changes as a reference. Savings may take until the second invoice to appear; dates and treatment of partial periods are agreed in writing.
- Without verified savings there are no success fees. There is no additional fixed fee for the assessment or implementation included in the success-based scope.
- Any work outside scope needs a separate proposal and your acceptance. Cloud provider charges remain your responsibility.
The percentage is set for your case before starting. We agree which invoices will be used and when payment is due: we do not bill for estimated savings.
Terms
- The offer is for accounts meeting the stated minimum spend, calculated as the average of the last three months, excluding VAT and adding the clouds in scope. Meeting the minimum does not guarantee acceptance: we also review scope and potential savings.
- Before the assessment, both parties sign its free scope and the terms for possible success-based implementation. Before implementation, actions, percentage, baseline, reference invoices, billing dates and how disputes are handled are confirmed.
- We only start implementation if we find viable savings and you agree to proceed. We do not guarantee savings in every account or promise a reduction percentage.
- We charge the agreed percentage of verified savings during the agreed period. Without verified savings there are no success fees; the accepted assessment remains free.
- The assessment phase only requires read access. Changes need specific permissions and your prior written authorisation, with an agreed window, validation and rollback.
- The initial report shows potential and options without implementation instructions. Both parties’ obligations and any implementation by your team or third parties are explicitly covered in the agreement.
- Fees exclude VAT. Cloud provider charges and usage commitments you accept remain your responsibility. We do not purchase reservations or Savings Plans without your approval.
Offer subject to a written proposal accepted by both parties. Acceptance is subject to Nubyron's validation.
06 · Limits
What falls outside
- We do not promise a savings figure: the report shows potential, and real savings come from applying and measuring.
- The audit is not a tool or an ongoing service. For regular follow-up, see Ongoing FinOps.
- We do not renegotiate contracts or discounts with your cloud provider or your reseller.
- The diagnosis uses read access only. Changes in production are made with your prior written authorisation (an email or a ticket from your responsible person is enough) and within the agreed window.
- It is not viable if we cannot read the billing data, for example with a reseller that gives no access.
- Do not send us passwords or keys through the form or by email; access is granted with a role in your account.
07 · Afterwards
From report to implementation
Savings implementation
We apply the changes from a report, ours or another firm’s, in batches and with the rollback documented.
- Batch-by-batch change plan.
- Execution with a documented rollback.
- Before-and-after evidence and an updated baseline.
- Documentation and handover. If a saving is automated in IaC, it is done together with DevOps as a Service.
Not included: Changes in production outside the agreed window or without prior written authorisation, redesigning the architecture (that is Cloud) and buying usage commitments on your behalf.
How it is engaged: In the success-based offer, included implementation is paid through the agreed percentage of verified savings. Independent or out-of-scope work needs a separate proposal before starting. Permissions are limited to what is needed and removed at the end.
Ongoing FinOps
We review your spend on a regular basis so the savings are not lost and cost stays allocated by team or product.
- A regular review with a short report, at the cadence we agree in writing.
- Tagging and allocation of spend by team or product.
- Budgets and cost-anomaly alerts.
- Tracking of potential and realised savings, always kept separate.
- A review of usage-commitment coverage. The decision to buy, renew or not renew a usage commitment (Savings Plans, Reservations), and the purchase itself, are yours. We give you a recommendation based on the information available, without promising savings.
Not included: Buying usage commitments on your behalf, renegotiating contracts, a FinOps platform of our own and coverage outside the agreed hours.
How it is engaged: A tailored quote, with scope, calendar and hours agreed in writing before we start. Continuous read-only access; when we finish, we remove it with you and confirm it in writing.
Who works with you
David González
Founder & CEO
Cloud architecture on AWS for startups and systems management.
LinkedIn of David González (opens in a new tab)
Leafar Maina
CTO
Over twenty years of experience in IT infrastructure.
LinkedIn of Leafar Maina (opens in a new tab)
Fernando Moreno
Commercial Director
Over 25 years in technology B2B sales.
LinkedIn of Fernando Moreno (opens in a new tab)
We work in cloud and DevOps, headquartered in Las Palmas de Gran Canaria with a team spread across Spain. We work remotely with B2B startups across Spain.
“We engaged Nubyron’s services and the experience has been very positive. The technical support is efficient and responds quickly to any request. They supported us throughout the application deployment process within Nexure.ai, showing great dedication and professionalism. We are very satisfied with the team’s work and the results obtained.”
“If a company needs specialized Kubernetes expertise, I would strongly recommend speaking with the Nubyron team. Their value proposition is solid and especially distinctive because of how they work.”
Nubyron is based in Las Palmas de Gran Canaria and works remotely with companies across Spain, including the Canary Islands. Direct contact with the people doing the work.
08 · FAQ
FinOps audit FAQ
What is a FinOps audit and what does it include?
We review AWS, Azure or Google Cloud spend read-only. For eligible accounts, the assessment is free and includes starting spend and potential savings by option, resource and account where the data allows. It does not include implementation instructions.
What is the difference between FinOps and cloud cost optimisation?
Cost optimisation is the concrete action, such as resizing or switching off unused resources. FinOps is the wider practice: it gives visibility, allocates spend by team or product and keeps control over time. A FinOps audit starts by looking; then you decide what to optimise.
When does a cloud cost audit make sense?
This offer starts at €8,000 per month in aggregate spend, excluding VAT and averaged over the last three months. We also assess whether potential savings justify the work. It is not designed for small accounts.
What data do you need to audit an AWS, Azure or Google Cloud bill?
The invoices or cost reports for the clouds in scope, some context on what is used and why, and read-only access to spend. We do not need change permissions or production credentials. The exact scope is agreed in writing before we start.
Do you also audit multi-cloud environments?
Yes. We can include AWS, Azure and Google Cloud and add up spend across accounts in scope to check the minimum. Providers, accounts and measurement terms are agreed in writing.
What if you find no savings?
If we find no viable savings, we do not proceed to implementation and the accepted assessment remains free. If we implement but there are no verified savings under the agreement, there are no success fees.
How much do you charge, and when?
A percentage of realised savings, agreed in writing before implementation. We use the first two complete invoices reflecting the changes as a reference, with the exact period agreed. Savings may appear from the second invoice. We do not charge on the potential shown in the report.
Do I have to buy Savings Plans or reservations?
No. The report separates options without commitments from those with usage commitments. Reservations or Savings Plans may offer more savings but are not always suitable. You decide, and we purchase nothing without your approval.
Why do we need to sign before starting?
Because the assessment is free and subsequent payment depends on how savings are measured. We specify scope, percentage, baseline, reference invoices and both parties’ obligations. If you decide not to proceed after the assessment, we do not start making changes.
What counts as success?
Recurring savings realised and verified on the agreed invoices, attributable to approved changes and adjusted to usage. One-off refunds or credits are excluded unless specifically agreed in writing. We do not charge on estimated potential or an annual projection.
How do I know the savings are real?
They are measured on the bill against a baseline agreed in writing and adjusted to usage. Each saving is tied to a specific action, and discounts you already had do not count. The methodology is the same for both parties and is set out in the proposal.
Can anything break?
Every change in production carries risk, so we prioritise by risk and effort and check with you what is safe to touch. Changes in production are made with your prior written authorisation (an email or a ticket from your responsible person is enough) and within the agreed window. There is a responsible person on your side.
First step
Request an assessment
Tell us your monthly spend, cloud providers and what concerns you about the bill. We check whether your account qualifies before starting the free assessment.
Prefer to talk for 30 minutes?(opens in a new tab)