· 06 · Operational Support

Operational Support

We stay after the project ends. Uptime is a relationship.

[ 06 ]

· What it includes

Retained operations

A named team on-call for your infrastructure — escalation path, runbooks, and SLA included.

Incident response

We join the call, work the problem, and write the post-mortem. No outsourced blame.

Capacity and cost management

Monthly reviews of performance, cost, and security posture so nothing drifts quietly.

Upgrade and patch management

Kubernetes, dependencies, OS — kept current without breaking production.

Knowledge transfer

When you're ready to bring it in-house, we make sure your team is ready.

· How we run it

Three steps. No surprises.

01

Assess

We review the current state — architecture, process, tooling, team capacity. We document what we find, not what you want to hear.

02

Plan

A scoped delivery plan with clear milestones, acceptance criteria, and what done looks like. Agreed before any work starts.

03

Operate

We ship, validate in production, and hand over with documentation. Or stay on as retained support — your choice.

· Recent outcomes

What this looks like in practice.

Scale-up engineering team

Problem

No internal ops capacity; every incident went straight to the CTO

Outcome

Retained ops engagement running 14 months; MTTD from 40 min to 4 min

Agency with complex client infra

Problem

Managing 8 client environments with 2 engineers

Outcome

Consolidated observability + shared runbooks; team capacity freed by ~30%

· Tech stack

Tools we work with.

Cloud

  • Multi-cloud
  • On-prem
  • Hybrid

IaC

  • Terraform
  • Ansible
  • Helm

Observability

  • Prometheus
  • Grafana
  • PagerDuty
  • Loki

CI/CD

  • ArgoCD
  • Gitea Actions

Security

  • CIS Benchmarks
  • Wazuh
  • Vault

Ready to scope this?

Tell us what you're working on. We'll map it to a delivery plan — not a proposal deck.

Start a project →