Start a project

DevOps & Managed Support

DevOps and managed support for software in production

We set up the pipelines, cloud environments and monitoring your software needs, then keep it patched and running. Your team builds the roadmap instead of fighting fires, and support hours and response times are agreed in writing.

Start a project
See our work

Organisations we've built for

  • MeQrez General Hospital
  • Space Science and Geospatial Institute
  • Ahadu Bank

Best for

When DevOps and managed support are the right move

If your team's week looks like one of these, we can take that work off it.

Firefighting

Your engineers spend the week on incidents and manual fixes instead of the roadmap.

We take over the running work: deployments, monitoring, patching and the first response to incidents.

Manual releases

Releases are done by hand, by one person, and nobody wants to be the one doing them.

A deployment pipeline with automated tests and a way back, so any engineer on the team can release.

No one watching

You hear about outages from your customers before your team notices them.

Monitoring and alerts on what users feel, such as errors and slow pages, with a runbook for each alert.

Ageing setup

Servers, frameworks and dependencies are years behind, and every update feels risky.

Updates planned and applied on a schedule, security patches first, each one tested in staging before production.

What you get

What we set up and run

The work that keeps production software healthy, done every week rather than when something breaks.

CI/CD pipelines

Build, test and deployment automated for every service, with a way to roll back a bad release.

Cloud environments

Staging and production set up the same way and automated, in your own cloud accounts.

Monitoring and alerts

Uptime, errors and performance watched, with alerts that reach the person who can act on them.

Patching and upgrades

Security updates, dependency upgrades and health checks on a schedule, not when something breaks.

Every engagement includes

Work in your cloud accounts and repositories

Runbooks for releases, alerts and recovery

A monthly report on incidents, changes and risks

Support hours and response times agreed in writing

How we deliver

From firefighting to a system that runs itself

The same three steps as every project we run, starting with what breaks today.

01

Plan

We review the environments, the pipelines and the last incidents, then agree what we take over, the support hours, the response times and what we won't touch.

02

Thin slice

One service first: its pipeline, monitoring and runbook working end to end, with a demo every week. Then the next service, in order of risk.

03

Launch and handover

Runbooks, alerts and documentation in place. Then your team runs the system, or we keep running it with a report every month.

How we work

Security and data

Access to production, handled with care

Running your systems means access to them. This is how that access is controlled.

Only the access the work needs.

Each engineer gets only the access their tasks need, through accounts you control, removed when the work ends.

Patches on a schedule.

Security updates applied on an agreed schedule, critical ones first, each tested in staging before production.

Backups you've restored.

Backups set up and restored in tests at agreed intervals, so recovery is a practised step, not a hope.

How we protect your data

Sectors and technologies

Where we've built, and what we run on

Sectors

Our engineering team has built and supported systems for hospitals, banks and cooperatives, where an outage stops the work of whole departments.

Healthcare

Financial services

Logistics & mobility

Public sector & geospatial

Technologies

We work in your cloud and your tools. These are the ones our engineers use most.

Docker

Kubernetes

Jenkins

GitLab

AWS

Azure

FAQ

Questions about DevOps and managed support

What we agree in the contract, usually deployments, monitoring, security patches, dependency upgrades, backups and the first response to incidents. Each month you get a report on what happened, what changed and what we'd fix next.

Support hours and response times are agreed per contract and written down. Our team is 1–2 hours from CET, so our working day covers yours. If you need cover outside it, the proposal says exactly what we can commit to.

Yes. We start with a review of the code, the environments and the recent incidents, write the runbooks that are missing, and take over step by step. If the code is fragile, our codebase recovery work stabilises it first.

Mostly AWS and Azure, with tools such as Docker, Kubernetes, Jenkins and GitLab. Everything runs in your accounts, so you keep control of the infrastructure and the bills.

A monthly rate, set by the systems covered, the support hours and the response times you need. The written proposal after our free intro call names the rate and what it includes, so there are no surprises on the invoice.

Patches and dependency upgrades follow an agreed schedule, with the urgent ones out of cycle. If an incident happens, we respond within the contracted time, restore service first, and send a written review of the cause and the fix afterwards.

Only the engineers who need it, through accounts you control. We work under a data processing agreement, and every engineer can sign an NDA if you want one. Access is removed when the work ends.

Yes. We agree who handles what, for example we run the pipelines and patching while your team builds the product, and we document everything so either side can pick it up. Our team lead plans and runs our engineers' work.

What we agree in the contract, usually deployments, monitoring, security patches, dependency upgrades, backups and the first response to incidents. Each month you get a report on what happened, what changed and what we'd fix next.

Support hours and response times are agreed per contract and written down. Our team is 1–2 hours from CET, so our working day covers yours. If you need cover outside it, the proposal says exactly what we can commit to.

Yes. We start with a review of the code, the environments and the recent incidents, write the runbooks that are missing, and take over step by step. If the code is fragile, our codebase recovery work stabilises it first.

Mostly AWS and Azure, with tools such as Docker, Kubernetes, Jenkins and GitLab. Everything runs in your accounts, so you keep control of the infrastructure and the bills.

A monthly rate, set by the systems covered, the support hours and the response times you need. The written proposal after our free intro call names the rate and what it includes, so there are no surprises on the invoice.

Patches and dependency upgrades follow an agreed schedule, with the urgent ones out of cycle. If an incident happens, we respond within the contracted time, restore service first, and send a written review of the cause and the fix afterwards.

Only the engineers who need it, through accounts you control. We work under a data processing agreement, and every engineer can sign an NDA if you want one. Access is removed when the work ends.

Yes. We agree who handles what, for example we run the pipelines and patching while your team builds the product, and we document everything so either side can pick it up. Our team lead plans and runs our engineers' work.

What we agree in the contract, usually deployments, monitoring, security patches, dependency upgrades, backups and the first response to incidents. Each month you get a report on what happened, what changed and what we'd fix next.

Support hours and response times are agreed per contract and written down. Our team is 1–2 hours from CET, so our working day covers yours. If you need cover outside it, the proposal says exactly what we can commit to.

Yes. We start with a review of the code, the environments and the recent incidents, write the runbooks that are missing, and take over step by step. If the code is fragile, our codebase recovery work stabilises it first.

Mostly AWS and Azure, with tools such as Docker, Kubernetes, Jenkins and GitLab. Everything runs in your accounts, so you keep control of the infrastructure and the bills.

A monthly rate, set by the systems covered, the support hours and the response times you need. The written proposal after our free intro call names the rate and what it includes, so there are no surprises on the invoice.

Patches and dependency upgrades follow an agreed schedule, with the urgent ones out of cycle. If an incident happens, we respond within the contracted time, restore service first, and send a written review of the cause and the fix afterwards.

Only the engineers who need it, through accounts you control. We work under a data processing agreement, and every engineer can sign an NDA if you want one. Access is removed when the work ends.

Yes. We agree who handles what, for example we run the pipelines and patching while your team builds the product, and we document everything so either side can pick it up. Our team lead plans and runs our engineers' work.

Related services

Often combined with

Rescue & run

Codebase Recovery & Stabilisation

If the code itself is fragile, we stabilise it first, then refactor it safely.

View service →

Quality & security

QA & Test Automation

Automated tests in the pipeline, so a failing test stops a bad release.

View service →

Quality & security

Application Security Testing

Penetration tests for web, mobile and APIs, to find what monitoring can't.

View service →

Have a project in mind?

We reply within one working day.

Start a project

or book a 30-min call (opens in a new tab)

FlightLabs is a Berlin-based software engineering company that builds, tests, secures and runs production software and AI for European companies, with its engineering team in Addis Ababa, 1–2 hours from Central European Time.

hello@flightlabs.ioBerlin, GermanyEngineering team: Addis Ababa, Ethiopia
LinkedIn (opens in a new tab)

Services

Industries

Company

In partnership with eTech S.C.