Optional continuity: we run your cloud with a named technical team member.

Your team in control

Optional support, with an exit plan

You can hire support for as long as you need it. We work in your accounts, document changes and agree how to hand operations over to your team or whoever you choose. Continuity does not require dependence on us: hours, scope, closure and handover are set out in writing.

01 · Who it is for

Who DevOps as a Service is for (and who it is not)

03 · Scope

What the service includes

• We run your cloud with a named technical team member, on a block of hours or a monthly plan with defined hours (plans from 20 hours).
• We aim for releases to be repeatable and not to depend on someone watching them (CI/CD), with a way back where technically possible.
• We describe your infrastructure in files inside your repositories, instead of in somebody’s memory (IaC, with Terraform or OpenTofu).
• The infrastructure state and the deployment credentials live in your company’s accounts, not in ours.
• We use containers and Kubernetes only when they pay off, and if they do not, we tell you.
• We set up monitoring and actionable alerts, with less noise and more signal about what fails (observability: metrics and logs).
• We check that your backups run as agreed and we test a restore at the frequency we agree.
• We write step-by-step guides to handle common incidents without depending on a single person (runbooks).
• We look after the security basics of releases: secrets outside the code, minimum permissions and agreed access.

Four blocks of work

• CI/CD and delivery automation

  We aim for releases to be repeatable and not to depend on someone watching them.

  • Versioned pipelines in your repository.
  • Repeatable deployment, with a way back where technically possible.
  • Secrets kept out of the code and basic dependency and image scanning.
  • Documentation of the flow.

  Not included: Rewriting your application, and licences for paid tools, which are yours to bear.

• Infrastructure as code and GitOps

  We move your infrastructure out of one person’s memory and into reviewable files.

  • IaC with Terraform or OpenTofu in your repositories.
  • State and credentials in your accounts.
  • Incremental import of the resources that already exist.
  • Pull request review and, where Kubernetes already exists, GitOps (for example, Argo CD or Flux).

  Not included: Designing the target architecture or a landing zone (that is Cloud) and rebuilding a whole environment without a plan. Architecture and landing zone in Cloud

• Observability and reliability (SRE)

  So you can see what really fails and reduce repeated incidents.

  • Metrics, logs and dashboards.
  • Actionable alerts, with less noise.
  • Step-by-step guides (runbooks) for common incidents.
  • A review after each relevant incident, to stop it recurring.

  Not included: On-call or coverage outside the agreed hours, security monitoring (SOC), and an observability platform licensed at Nubyron’s expense.

• Operations and maintenance during agreed hours

  A named person makes sure your platform stays up to date.

  • A maintenance plan with planned patches and upgrades.
  • Operation of an existing Kubernetes cluster, within the agreed scope.
  • Backup restore tests at the frequency we agree.
  • A change log and a one-page monthly summary.

  Not included: Coverage outside the agreed hours, changes in production outside the agreed window or without prior written authorisation, end-user support and administration of your business applications.

What you get

• Automated, repeatable releases, with a way back where technically possible.
• Versioned infrastructure in your repositories, with the state and the deployment credentials in your accounts.
• Useful alerts and dashboards that show what really fails, with less noise.
• Step-by-step guides (runbooks) and documentation of the changes we make so your team can carry on without us.

05 · Engagement

Format: block of hours or monthly plan

• Everything is quoted to fit your case: you receive the scope and the quote in writing before we start.
• For recurring operation, the proposal sets out the scope, hours and schedule in writing; extra hours are agreed before they are used.
• A block of hours is only used for one-off jobs, and all the rules are set out in writing in the proposal.
• Cloud provider costs and the costs of tools you use in your account are yours to bear.

What falls outside

• Outside the agreed hours there is no coverage or on-call service, neither optional nor as an extra.
• We do not develop or modify your application code; we work on the infrastructure and on releases.
• We offer no availability commitments with penalties and no resolution times.
• We do not take responsibility for your platform’s availability outside the agreed hours, nor do we promise an availability level.
• We do not design a full disaster recovery plan, which is a separate project, nor do we replace your continuity policy.
• It does not include security audits, penetration testing (pentesting), certifications or regulatory compliance.
• We do not permanently replace an in-house position: if you need to hire, we will tell you.

07 · Team

Who works with you