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
NIS2 turns secure delivery into a legal duty
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.
Page reviewed Nov 14, 2026. Region and regulatory facts for Germany checked Nov 14, 2026. Rules change — confirm current obligations with your adviser.