02 · ChangeCloud architecture

A well-ordered cloud architecture, as code and documented.

Production and testing mixed together, manual changes in the console and a diagram that does not reflect reality. We design a well-ordered cloud architecture, leave it as code and documented, and explain the reasoning behind every decision.

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 EU regulations. The cyber resilience ones apply if you make or sell software. Follow each source to check them.

  1. Cyber Resilience: reporting exploited vulnerabilities

    If you sell software or products with digital elements in the EU, you must report actively exploited vulnerabilities. Without a pipeline that knows what is inside, that is hard.

    Source: Reglamento (UE) 2024/2847, Cyber Resilience Act · 11 Sep 2026
  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
  3. Cyber Resilience: full obligations

    Security by design, vulnerability handling and updates across the product’s life. It is built into the process, not bolted on at the end.

    Source: Reglamento (UE) 2024/2847, Cyber Resilience Act · 11 Dec 2027

03 · What changes

What changes when the architecture is code

  • Today: Manual changes with no record.

    With Nubyron: Infrastructure as code, reviewed and versioned.

  • Today: Everything in the same place.

    With Nubyron: Separate environments: development, testing and production.

  • Today: “It was done that way just because”.

    With Nubyron: Every decision written down, with alternatives and consequences.

  • Today: Only one person understands it.

    With Nubyron: Documentation so your team can maintain it.

04 · What you receive

What we deliver

A fixed project, handed over to your team. This is what you take away:

  • The design, with the why

    Diagrams that match reality and every decision recorded so nobody has to guess it.

  • Infrastructure as code

    For example with Terraform, with the landing zone included and in your repositories.

  • Separate environments

    A proposal for development, testing and production isolated from each other.

  • Security by design

    Minimum access and environment separation designed in from the start, not bolted on.

  • Documentation and handover

    So your team understands it, maintains it and grows it.

05 · How we work

How we work, step by step

  1. We understand the business

    We start from how your product works and your current environment, not from a template.

  2. We design

    Architecture, diagrams and decisions with their reasoning.

  3. We define it as code

    The infrastructure ends up as IaC so it is repeatable.

  4. We hand over

    We explain the design to your team and answer questions.

07 · Further reading

Recommended reading

08 · FAQ

Frequently asked questions

Do we have to rebuild everything?

Not necessarily. We start from what you have and propose what to rebuild, what to move to code and what to leave as it is, with the why in writing.

Will my team be able to maintain it?

That is the goal: code in your repositories, documentation and handover. If you want, we can support you afterwards with DevOps in agreed hours.

On which cloud?

The one you use: AWS, Azure or Google Cloud. If you have not decided yet, we start with an advisory session.

Do you only design, or also build?

It is set in the scope: design only, design and build, or supporting your team while it builds.

Does it include security or operations?

Security comes in as a design principle (separate environments, minimum permissions), not as a certification or a review of what is already deployed: that is the cloud review. Running the environment is agreed separately, during agreed hours and with no on-call cover.

Can you start from what we already have?

Yes. We start from your current environment and propose improving it in phases, without forcing you to rebuild everything.

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 architecture?

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 architecture

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