01 · UnderstandCloud review

Technical review of your cloud: cost, security and architecture, read-only.

A technical review of your cloud, read-only: cost, security and architecture. Accounts nobody recognises, access for people who have left and resources running that nobody uses. We give you a report with what matters on top and a prioritised plan. If your concern is the bill, start with the FinOps page.

01 · Situation

Self-check

Tick the situations that apply to your company. Your selection stays in your browser: no data is sent.

Tick those that apply to your company.

Schedule a call

02 · Why now

Dates worth keeping in mind

Dates from the EU Data Act (they may change with the digital omnibus, still in progress). Follow the source to check them.

  1. The EU Data Act already applies

    It includes rules for switching cloud provider: notice periods, portability and getting your data out.

    Source: Reglamento (UE) 2023/2854, Data Act · 12 Sep 2025
  2. Switching cloud provider, with no switching charges

    Under the EU Data Act, from that date providers can no longer charge for switching or for moving your data out. Negotiating or moving gets easier, if you know what you have.

    Source: Reglamento (UE) 2023/2854, Data Act · 12 Jan 2027

03 · What changes

What changes after the review

  • Today: You think you know what you have.

    With Nubyron: A written inventory of accounts, resources and access.

  • Today: Broad permissions for convenience.

    With Nubyron: A list of access to review, in order of risk.

  • Today: The bill gets paid without questions.

    With Nubyron: Costs that look unnecessary, for you to confirm.

  • Today: Whatever screams gets fixed.

    With Nubyron: A prioritised plan: highest risk first.

04 · What you receive

What we deliver

A fixed-scope, read-only review. This is what you take away:

  • A report with what matters on top

    In writing and without needless jargon: what there is, what risk it carries and what to fix first.

  • Availability and housekeeping risks

    What we see in the inventory and access. The detailed security review is a separate module.

  • Costs that look unnecessary

    With the cost module, for you to confirm. Potential savings, never promised.

  • A prioritised plan

    Actions in order, without commands or code: your team or whoever you choose can carry it out.

  • A session with your team

    We go through the report together and answer the questions.

05 · Packages and scope

Fixed packages

For AWS, Azure or Google Cloud. All include a report, a prioritised plan and a walkthrough session; none includes applying the changes.

  • Essential

    One account, one provider and up to 10 main services. Report in 5 business days from when read-only access is granted. It is the only level with that lead time.

  • Business

    Up to 3 accounts, 2 providers and up to 20 main services. Lead time agreed in writing before starting.

  • Advanced

    More accounts, providers or services than Business. Scope and lead time agreed in writing after a 30-minute call.

I want a review

06 · Optional modules

Cost, security and architecture

They are added to the base review if you need them. Each module has its own scope and lead time in writing, outside the 5-business-day lead time of Essential.

  • Cost module

    Analysis of spend by service and environment, with read-only access to billing. Savings are potential, never promised.

  • Security module

    Review of identities, permissions, networks and configuration, with findings ranked by severity. It is not a certification or a penetration test.

  • Architecture module

    Interviews and a review of documentation and diagrams against the provider's good practices (Well-Architected).

07 · How we work

How we work, step by step

  1. Scope in writing

    We agree which accounts and areas we look at, and which modules, before we start.

  2. Read-only access

    You create it yourselves in your own accounts. We install and change nothing.

  3. Review

    We review inventory, access and organisation, plus the modules you engaged. Any open question is resolved with you.

  4. Report and close

    We hand you the report and plan, go through them with your team, and you remove the access.

010 · FAQ

Frequently asked questions

Will you change anything in my cloud?

No. We work with read-only access that you create and control, and you remove it when we finish. Applying changes is not part of the review.

How much will we save?

We do not promise it. We point out the costs that look unnecessary, with the cost module, and you decide. It is always potential savings until it is applied and measured.

And then what?

The plan is yours: your team, another provider or we can carry it out, with a new written scope.

Do you need admin access?

No. Read-only permissions in your accounts are enough; you define them and we write them down before we start.

Is it an audit?

It is a read-only technical review of how your cloud is configured (sometimes called a technical audit). It is not a compliance audit, it certifies nothing and it includes no penetration testing.

How long does the review take?

The lead time depends on the level and is given to you in writing before we start; the entry level (Essential) has its lead time published in the levels section of this page. Business, Advanced and the modules have their lead time agreed in writing.

No 24x7 on-call or SLA · No zero-risk claims · No guaranteed savings · No testing without permission. See everything we do not promise →

Shall we talk about cloud review?

30 minutes with a technical member of the team. We review what you ticked, tell you where we would start and what can wait. No preparation is needed.

First step

Tell us about your case

Write to us about your environment and your question in general terms. We propose a written scope before any work begins.

  • A technical person repliesYour message is reviewed by a technical specialist.
  • Scope in writing before we startWhat is included, what is not and what it costs. You decide with the proposal in writing.
  • Your data, only to reply to youNo advertising unless you agree.
Send an enquiry

You are interested inCloud review

Use your work email if you can.

Describe it in your own words; no technical detail is needed. Please do not include passwords, credentials or confidential information.

Do not include passwords or client data: access is set up later, with you.

Add more context (optional)

Book a call