03 · MaintainDevOps and support in agreed hours

Reliable releases and infrastructure as code under your control.

Pipelines only their author understands, Terraform nobody has run for months and manual changes in production. We run your CI/CD and infrastructure as code in agreed hours, in your accounts and documented: reliable releases under your control.

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 and the CA/Browser Forum. 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. SSL/TLS certificates capped at 100 days

    And 47 days from 15 March 2029. If renewal is not in the pipeline, it will expire in production.

    Source: CA/Browser Forum, Baseline Requirements · 15 Mar 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 we run it

  • Today: Whoever knows deploys.

    With Nubyron: Versioned pipelines anyone on the team can run.

  • Today: Manual changes in production.

    With Nubyron: Infrastructure as code, with state and credentials in your accounts.

  • Today: One failure and fingers crossed.

    With Nubyron: Repeatable deployment and rollback when technically possible.

  • Today: Alerts nobody looks at.

    With Nubyron: Useful alerts, a change log and a monthly summary.

04 · What you receive

What we deliver

A monthly plan, in agreed hours and in your accounts. This is what gets done:

  • Pipelines with a way back

    Versioned CI/CD in your repositories, with repeatable deployment and rollback when technically possible.

  • Infrastructure as code

    Terraform or OpenTofu in your repositories, with state and credentials in your accounts.

  • Maintenance and useful alerts

    Incidents handled in the agreed hours, with a change log and a monthly summary.

  • Security in the pipeline

    Basic DevSecOps controls: secrets out of the code and dependencies checked.

  • Guides to carry on without us

    Step by step, so your team depends on nobody, us included.

05 · How we work

How we work, step by step

  1. Scope and hours in writing

    We agree priorities, working hours and how the service is engaged before we start.

  2. Minimum access

    We access with individual identities and minimum permissions, and you can remove them whenever you want.

  3. Work in your tools

    We work in your repositories and channels. Changes in production, with your prior written authorisation.

  4. Summary and exit

    Every month, a one-page summary. Everything is documented so you can leave whenever you want.

07 · Further reading

Recommended reading

08 · FAQ

Frequently asked questions

What happens outside the agreed hours?

There is no on-call cover or SLA, and we say so from the start. We leave alerts and guides so your team, or an on-call provider, can act.

Do you use our tools or yours?

Yours, in your repositories and accounts. If something should change, we propose it in writing.

And if we want to stop?

Everything is in your accounts and documented. There is an exit plan from day one.

What happens outside the agreed hours?

There is no coverage and no on-call service, and no SLA: we make this clear from the outset. We do not guarantee response times; we prioritise each request with you within the agreed hours. We leave alerts and guides so your team, or an on-call provider, can act.

Who owns the code and the infrastructure?

You do: accounts, repositories and documentation stay in your company’s name. If you want to leave the service, we remove our access with you and you keep the pipelines, the code and the guides.

Which tools and clouds do you work with?

On AWS, Azure and Google Cloud, with the usual tools (for example Terraform or OpenTofu, GitHub Actions or GitLab CI, Argo CD). We start from what you already use.

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 DevOps and support in agreed hours?

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 inDevOps and support in agreed hours

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