Talk to us
WhatsApp us

Free cloud cost review: we will find the waste in your AWS or Azure bill in 5 business days. Book it

DevOps engineering · Germany

DevOps services for Berlin and German businesses

CI/CD, infrastructure as code and observability that turn releases from an event into a routine.

  • 5–6 shared hours/day with Berlin
  • Setup projects start from the EUR equivalent of USD 22,000
  • Reviewed

The short answer

LDelight sets up DevOps for Berlin and German companies on AWS and Azure, including the AWS European Sovereign Cloud. Pipelines sign and inventory what they ship, which supports the secure-development and supply-chain duties in Germany's NIS2 law, and delivery metrics are designed at team level so they do not become employee monitoring that needs works-council agreement.

Key takeaways

  • Build pipelines produce SBOMs and signed artefacts, supporting NIS2 supply-chain duties
  • Delivery metrics are measured per team and service, never per developer
  • Infrastructure code can target Frankfurt or the AWS European Sovereign Cloud
  • Five to six shared working hours with Berlin every day

Since Germany's NIS2 implementation took effect in December 2025, around 30,000 companies must apply risk-management measures that explicitly include supply-chain security, security in development and maintenance, and vulnerability handling. For an engineering organisation, much of that is a description of a good pipeline. We set pipelines up to scan dependencies and container images, generate a software bill of materials for every build, sign artefacts so only what the pipeline built can be deployed, and record which version of what is running where.

The point is not the tooling; it is being able to answer, within hours, "are we affected?" when the next widely used library vulnerability is announced. With an SBOM per release and an accurate deployment record, that is a query. Without it, it is a week of asking teams.

Metrics without monitoring people

DevOps programmes like to measure deployment frequency, lead time and change failure rate. In Germany, those numbers raise a question most consultancies skip: a system capable of tracking an individual employee's behaviour or performance needs the works council's agreement under § 87 BetrVG, whether or not anyone intends to use it that way. Dashboards that show commits or deployments per developer fall squarely into that territory.

We design delivery metrics at team and service level from the outset, document what is and is not collected, and give your works council a clear description before rollout. The engineering value is the same; the rollout does not stall six weeks in.

Sovereign or standard: decide it in code

Since January 2026 the AWS European Sovereign Cloud has been an option for German workloads: a separate partition operated by EU residents, with its own accounts and a narrower service catalogue. Some buyers will require it; many will not. We write infrastructure modules that target Frankfurt today and can be pointed at the sovereign partition later, with the unavailable services identified up front instead of discovered during a move. On Azure, the equivalent conversation centres on the EU Data Boundary and Germany West Central.

Shared hours, English delivery

We share five to six working hours with Berlin each day, so pairing and reviews happen live. We work in English. Where works-council documentation or runbooks for operations staff must be in German, a native reviewer is scoped and priced in the proposal rather than added later.

AWS and Azure regions that matter for Berlin

RegionWhereZonesWhat it means
AWS Europe (Frankfurt)
eu-central-1
Frankfurt
since 2014
3 Main AWS region for German workloads.
AWS AWS European Sovereign Cloud
eusc-de-east-1
Brandenburg
since 2026
3 Separate partition (aws-eusc), operated by EU residents; generally available since January 2026. Separate accounts, narrower catalogue.
Azure Germany West Central
germanywestcentral
Frankfurt
since 2019
3 Primary German region with availability zones.
Azure Germany North
germanynorth
Berlin
since 2019
None Restricted paired region for DR, not for general deployment.

Residency and sovereignty in Germany

German buyers ask about sovereignty more than any other market. Since January 2026 AWS offers a physically and operationally separate European Sovereign Cloud in Brandenburg; Microsoft's answer is the EU Data Boundary plus partner sovereign offers. Whether you need either is a risk decision — most workloads do not — but it must be made before the landing zone, not after.

Rules that change the work in Germany

What each rule is, and what it changes for DevOps engineering specifically. This is engineering guidance, not legal advice.

NIS2UmsuCG (German NIS2 implementation)

About 30,000 "important" and "particularly important" entities

In force since 6 December 2025 with no transition period. BSI registration was due by 6 March 2026; the BSI has signalled it expects full implementation by 31 July 2026.

For this engagement: The pipeline provides evidence for the supply-chain, secure-development and vulnerability-handling measures: SBOM per build, signed artefacts, dependency and image scanning, and a record of what is deployed where.

Primary source

Works council co-determination (§ 87(1) no. 6 BetrVG)

Employers with a works council

In force. Technical systems capable of monitoring employee behaviour or performance require works-council agreement.

For this engagement: Delivery and observability metrics are aggregated by team and service. Before rollout we provide a written description of the data collected so the works council can assess it, and no per-person performance view is built.

Primary source

GDPR Chapter V — transfers to India

Any controller whose personal data is accessed by our engineers in India

India has no EU adequacy decision, so remote access to personal data is a restricted transfer.

For this engagement: Platform work does not need production personal data. Where incident access could expose it, the EU SCCs are in place before access is granted, and access is time-limited and logged.

Primary source

How delivery runs from Noida into Berlin

Our team works 09:30–18:30 India Standard Time, one office, no daylight saving. Five to six shared hours across the German working day.

Your seasonOur working day, your clockShared business hours
CET (late Oct – late Mar)05:00–14:0009:00–14:00 (5 h)
CEST (late Mar – late Oct)06:00–15:0009:00–15:00 (6 h)

Berlin and Frankfurt mornings and early afternoons are shared working time. We deliver in English; German-language artefacts (works-council documentation, end-user guides) are produced with a native reviewer and scoped explicitly.

If a change touches employee monitoring — new logging, endpoint agents, observability on staff activity — your works council may have a co-determination right. We build that consultation into the plan rather than discovering it at go-live.

How the price is built

Fixed-fee assessment, then a fixed-scope setup project; optional monthly operations retainer

Setup projects start from the EUR equivalent of USD 22,000

  • Assessment with a target pipeline design mapped to your NIS2 obligations
  • Pipelines with scanning, SBOM generation, signing and approvals
  • Infrastructure as code targeting Frankfurt, the sovereign partition or Azure Germany
  • Team-level delivery metrics with a works-council description

Quoted in euros. German-language deliverables are scoped separately with a native reviewer.

Page reviewed Nov 14, 2026. Region and regulatory facts for Germany checked Nov 14, 2026. Rules change — confirm current obligations with your adviser.

Scope it with an engineer

A 30-minute technical call inside the Berlin overlap window. You leave with a written recommendation, whether or not you hire us.

Request a proposal

DevOps engineering: the full method

DevOps engineering automates the path from code to production. LDelight implements CI/CD pipelines, infrastructure as code, automated testing and…

How we run DevOps engineering

Go deeper before you call

Long-form guides written by the engineers who would run this engagement.

DevOps services for Berlin and German businesses: questions buyers ask

No single system does. NIS2 also covers governance, incident reporting, business continuity and staff training. A well-built pipeline does supply evidence for several technical measures — secure development, supply-chain security and vulnerability handling — and we map exactly which, so your compliance team can see what remains.

If they can be broken down to individual employees, they are likely to. Measured at team or service level they usually raise far fewer questions. We design them that way and give the works council a written description before anything is switched on.

Only if a customer, regulator or public-sector contract requires it. It is a separate partition with its own accounts and a smaller catalogue, so it carries real constraints. We write modules that can target it later and list the services you would lose today.

Day-to-day delivery is in English. Where documents must be in German — for the works council, a regulator or operations staff — we include a native reviewer in the proposal and price it explicitly.

Let’s scope your next project

Tell us what you are building or what is not working. You will get a technical response from a senior engineer — not a sales script — usually within one business day.