Defense tech and dual-use startups in DACH have grown quickly, and many face the same engineering capacity constraints as other scaleups. Before any work moves to a team outside the EU, one question has to be answered first: does sharing the relevant technology or software with that team amount to an export that requires authorisation? Under Regulation (EU) 2021/821, the answer can be yes even if nothing physical crosses a border. Transmitting software or technology by electronic means to a destination outside the EU customs territory is an export, and so is making it available electronically to persons outside the EU. For engineering work with India, this means each work package needs an export control classification before it is assigned. Some work can go without authorisation, some only with a licence, and some should not go at all.

Why the question is becoming urgent

Demand is expanding quickly. Germany's 2026 federal budget allocates 82.69 billion euros to the regular defence budget and a further 25.51 billion euros from the Bundeswehr special fund, around 108 billion euros in total, and the Federal Ministry of Defence aims to reach NATO's target of 3.5 percent of GDP by 2029. Engineering capacity has not grown at the same pace: Bitkom counted 79,000 unfilled IT positions in Germany in 2026, and 47 percent of companies named insufficient German language skills as a main hiring barrier. The threat picture argues for discipline at the same time. In Bitkom's 2025 economic protection study, about 87 percent of German companies reported being affected by data theft, espionage or sabotage, with total damage of 289.2 billion euros. The rules are moving too. A package of measures from the Federal Ministry for Economic Affairs, in force since 1 February 2026, added new and updated general authorisations (AGGs), including one for technology and software transfers under the European Defence Fund and simpler rules for storing data on servers in certain European countries. Several of these simplifications concern European cooperation. For work packages destined for India, check the current AGG scope with BAFA rather than assume coverage.

The legal building blocks

  • Export includes intangible transfer. Article 2(2) of Regulation 2021/821 defines export to include the transmission of software or technology by electronic media, including email, file transfer and making it available in electronic form to persons outside the EU. Oral transmission of technology over voice media is also covered.
  • Listed items. Annex I lists controlled dual-use items, including software and technology for their development, production or use. Exporting listed items requires authorisation.
  • Catch-all. Article 4 requires authorisation for unlisted items where the exporter has been informed by the authority, or is aware, that they are or may be intended for certain uses, including weapons of mass destruction or military end-use in an embargoed destination.
  • Technical assistance. Article 8 and the German Außenwirtschaftsverordnung (§§ 49 ff. AWV) control certain technical assistance, which includes support related to development, delivered in person, electronically or verbally.
  • Military goods. Goods, software and technology on the German export list (Ausfuhrliste, Teil I Abschnitt A) are controlled under the Außenwirtschaftsgesetz and AWV, with the Federal Office for Economic Affairs and Export Control (BAFA) as licensing authority. Weapons of war are additionally subject to the Kriegswaffenkontrollgesetz.
  • Exemptions. Information in the public domain and basic scientific research are generally not controlled.

India is not covered by the Union General Export Authorisation EU001, which applies to a short list of destinations such as the United States, Japan, the UK and Switzerland. India is a participating state of the Wassenaar Arrangement, which can be relevant to licensing practice, but it does not remove the licensing requirement for listed items.

A traffic-light framework

The practical approach is to classify each repository, document set and work package before an external team gets access.

CategoryExamplesApproach
Green: not controlledGeneric web front ends, internal tooling, CI infrastructure, commercial data pipelines without controlled algorithms, open-source contributionsCan be offshored. Document the classification
Amber: controlled dual-use, licensableTechnology for listed sensors, certain cryptography, navigation or imaging components, depending on parametersOnly with a BAFA licence or after a documented determination that no licence is needed. Strict access segmentation
Red: military or classifiedSoftware or technology on Ausfuhrliste Teil I Abschnitt A, weapons-related development, anything classified VS-NfD or higherDo not offshore. Classified material requires the national security clearance framework, which is generally not available for teams abroad

Dual-use companies frequently have a mix of all three in one monorepo. That is the core operational problem. If a remote engineer can clone the whole repository, the whole repository has effectively been made available.

Designing the work so the green zone is large

Companies that use external engineering successfully in this sector tend to do it by architecture, not by exception handling:

  1. Split repositories by classification. Controlled algorithms and parameters live in separate repositories with separate access control. Shared interfaces are defined so that green components do not need to see amber or red internals.
  2. Use stubs and simulators. Green-zone engineers develop against interface stubs and synthetic data, not real sensor characteristics or performance parameters.
  3. Classify documentation too. Design documents, test reports and issue tracker entries can contain controlled technology. Tickets visible to the external team must not contain controlled parameters.
  4. Watch the communication channels. A video call in which an engineer explains a controlled algorithm can be a transfer of technology. Brief your internal engineers on what they may discuss.
  5. Keep build and deployment for controlled components internal. CI pipelines that compile amber or red code should run in your environment, with the external team seeing only the results relevant to their components.

Internal compliance programme

The Commission Recommendation (EU) 2019/1318 describes the elements of an internal compliance programme for dual-use trade controls: management commitment, risk assessment, export screening procedures, training, record keeping, audits and physical and information security. For a company working with an external team, the following additions are useful:

  • Classification of each repository and document space, reviewed when content changes.
  • Access matrix linking named external engineers to approved classification levels.
  • End-use and end-user statements from the service provider.
  • Screening of individuals and the service provider against EU sanctions lists.
  • Records of every licence determination and of the technology actually shared.

If your products contain technology of US origin, US re-export rules may apply in addition to EU and German law. That needs a separate assessment.

Questions to answer before signing

  1. Has every work package been classified by someone qualified, typically your export control officer (Ausfuhrverantwortlicher)?
  2. Can the green work be done without access to amber or red repositories?
  3. Where amber work is planned, has a licence been applied for, and is the timeline acceptable?
  4. Are communication rules for internal engineers documented?
  5. Does the contract with the provider include end-use commitments, access restrictions and audit rights?

For an external pod in this vertical, the natural scope is green-zone work and the engineering that makes the separation possible: repository restructuring, interface stubs, simulators and CI. Amber work should only be considered once the client has completed its licence determination. Our general security controls are on the security page.

This article is general information and not legal advice. Export control classification is fact-specific; consult your export control officer, BAFA guidance or a qualified lawyer before sharing any technology.

Export control does not have to block external capacity in defence and dual-use engineering, but it does decide its shape. niogod™ scopes such engagements as Werkvertrag deliverables in the green zone, with a German-speaking Projektleiter who aligns each work package with your export control officer before it is assigned. If a dual-use programme is on your roadmap for 2027, that classification conversation is worth having early.

Talk to niogod™

Planning engineering capacity in DACH? Book a 30-minute consultation with the niogod™ team.

Book consultation
← All insights