Cloud-native DevOps & SRE consulting (AWS, GCP, Azure): ship faster, run calmer

We build delivery and operations in the public cloud (AWS, Google Cloud, Azure): CI/CD pipelines, infrastructure as code with Terraform, Kubernetes on EKS, GKE or AKS, monitoring and a fixed routine for incidents. It is for software companies that are staying in the cloud. The result: releases without manual steps, and a restore whose duration has been measured.

Request an intro call

Fixed-scope entry offer

Disaster Recovery Drill

For whom: Companies that have backups but have never measured how long a restore actually takes. A common trigger: a customer's security questionnaire asks for restore tests, or a recent outage was a close call.

Scope

  • One agreed system, one exercise: either a restore from your existing backups or a planned failover.
  • Typically a database and the application that uses it, on Kubernetes, on virtual machines, or on AWS, GCP or Azure.
  • Before we start, we agree with you what "back in service" means, when the clock starts and stops, and where the drill runs: in a separate environment or, with your sign-off, on the live system.
  • We run the drill together with your team and log every step with a timestamp.
  • Delivered remotely.

DeliverableA written report: what was restored, the measured times, the gaps we ran into, and a prioritised list of fixes. If you have set a recovery time objective, the measured time is set against it.

Prerequisites

  • Backups or replicas of the system already exist. The drill tests what is there.
  • Someone on your team who knows the system is available during the drill.
  • Access to the systems involved, for the drill.
  • For a drill on the live system: a maintenance window you have approved.

Not included

  • Further systems or a second exercise (for example a failover on top of the restore). We quote those separately.
  • Fixing the gaps we find. That is a project of its own, with us or without us.
  • Setting up backups where none exist yet.
  • A commitment on how fast your system will be back in a real incident. The drill measures where you stand today.
  • An assessment of whether NIS2 or the Cyber Resilience Act applies to your company. Whether and how NIS2 applies to you is a question for your legal advisers; we implement the technical measures.

Request this offerfrybad.de/en/contact/?thema=devops-sre&angebot=ernstfall-probe

Where teams usually start

  • The cloud bill grows faster than the product. Nobody can say exactly which service costs what, or which of it you actually need.
  • Releases depend on one person. Some deployments are still manual, and the person who knows how is on holiday.
  • Incidents without a routine. Alerts fire, but it is unclear who responds, what comes first and what changes afterwards.
  • A customer asks about restore tests. The security questionnaire wants to know when you last rehearsed a restore and how long it took.

How we work

  1. Assessment.

    Cloud accounts, pipelines, infrastructure, costs and alerts: what runs where, who knows it, where it hurts. You get a short written finding with the biggest levers.

  2. Plan.

    What comes first, ordered by effort and impact. You get a sequence you can take to your own management.

  3. Build.

    Infrastructure as code with Terraform; pipelines that build, test and roll out versioned releases; monitoring with alerts someone can act on; runbooks for the most common incidents. All of it in your repositories, together with your team.

  4. Handover or operations.

    A walkthrough, runbooks and a measured restore rehearsal. After that you run it yourselves, or we support you within the hours agreed in the contract.

What we run ourselves

Our own platform does not run in a public cloud. We run our own hardware in a data centre in Munich. The way we work is the same one we bring to the cloud:

We rehearse restores and failovers, and we measure them. Two measurements from running our product Fortlauf:

The Disaster Recovery Drill above runs the same measurement on a system of your choice, on AWS, GCP or Azure too. More on location and backups: Where your data lives.

If your own hardware would cost less than the cloud bill: Kubernetes platforms, built and run. If security needs checking first: Kubernetes and cloud security audits.

Stack

  • Every change to infrastructure and applications is a commit; Flux keeps the clusters in line with the Git repository.
  • CI on our self-hosted GitLab builds every image, scans it for known vulnerabilities and gives it a version.
  • New versions run on a test cluster first, and only then in production.
  • Secrets sit in the repository, encrypted with SOPS and age.
  • Monitoring with VictoriaMetrics, Grafana and Loki.

Restore rehearsal on 30 Aug 2026: we restored both of Fortlauf's production databases (product data and sign-in) to coordinated points in time, in a separate test environment. Both were back in service 3 min 22 s after the restore configuration was applied; a repeat run the same day took about 3 min 30 s. Not included: the time to decide and prepare, and files kept outside the databases.

Measured

Planned database failover on 4 Oct 2026: we switched Fortlauf's product database to another replica while the service was running. The database cluster was fully back in service 19 s after the switch; writes paused for about 8 to 9 s, and no external request received a server error in that time. Not included: an unplanned outage.

Measured

Case studies

Logistics SaaS for plant and transport logistics

Case study: scaling a logistics SaaS for a major customer launch

A logistics SaaS platform onboarded a major customer with around 50,000 users. We took platform SRE responsibility for the edge gateway, database and eventing, re-set resource allocation and autoscaling on Kubernetes (EKS), added missing database indexes and detected customer-facing errors automatically from the edge logs. Result: p95 request time down by about 80 %, error rate within the agreed error budget, a platform SRE team established.

Passenger information at a large transport operator

Case study: release tests for passenger information, automated

End-to-end tests of an event-driven data platform (Kafka, Spring Boot): test orchestration rebuilt from plain GitLab CI jobs to Argo Workflows, release environments provisioned via Crossplane on Kubernetes, the test runner refactored.

Our own product

Case study: running a SaaS on our own infrastructure

Fortlauf is our product. We built it, and we run it on our own hardware. In production since July 2026: tenant isolation in the database, immutable document storage, delivery by GitOps, measured recovery.

Who you will talk to

One fixed contact from the intro call to the handover.

Send a message

What we do not do

  • No on-call cover. Operations run in agreed hours.
  • No staff placement at a day rate without an agreed outcome.
  • No savings percentage before we have seen your bill.

Frequently asked questions

Do you provide on-call cover?

No. On-call cover is not part of our offers. We run operations in agreed hours and set up alerts and runbooks so your team can respond itself.

Will you work with our existing Terraform and CI?

Yes. We carry on in your repositories and with your tools rather than starting from scratch. Anything that should be replaced is in the written finding, with the reason.

Public cloud, or your own hardware after all?

It depends on your load. Sharp peaks, short projects and heavy use of managed services favour the cloud; steady base load and large data volumes tend to favour your own hardware. We work it through with your numbers. What a platform on your own hardware looks like: Kubernetes platforms, built and run.

Can you cut our cloud costs?

We show you where the money goes and which changes would reduce it, each with its effort. We only put a percentage on savings once we know your bill and your load.

How do we measure success?

With figures we agree at the start and then record: how often you ship, how long a change takes to reach production, how often a release is rolled back, how long a restore takes and what the cloud costs per month. At the end we measure the same figures again.

Insights

Want to talk about your delivery and operations?

Tell us where you run today, what bothers you and by when it should be better.