--- title: "Germany Now Owns the Source Code of Its Combat-Drone Mission Software. What the Helsing MissionOSBw Handover Means for AI Procurement" slug: "germany-owns-helsing-missionosbw-source-code-software-ownership" author: "ibl.ai" date: "2026-11-07 10:00:00" category: "Premium" topics: "Helsing, MissionOSBw, BAAINBw, CFSN, Bundeswehr, government-owned source code, sovereign AI, Government Open Source Software, Modular Open Systems Approach, MOSA, vendor lock-in, defense AI procurement, AI source code ownership" summary: "Helsing handed Germany's procurement agency the full source code, documentation and SDK for MissionOSBw, with ownership staying with the German state. What was transferred, what is still unclear, and the procurement lesson for any agency buying AI." banner: "" thumbnail: "" linkedin: | On November 4, Helsing handed Germany's military procurement agency, BAAINBw, the source code for MissionOSBw, the mission operating system for Germany's future combat drones. Documentation and an SDK came with it, and ownership stays with the German state. Reuters called the arrangement unusual. In defense, prime contractors often keep control of key software, interfaces and IP. The design point matters as much as the handover. MissionOSBw follows a modular open systems approach, so modules from different suppliers can be added or replaced, and the Bundeswehr can have the software developed further by itself or by other companies. That is the right question for any agency buying AI: when the contract ends, who holds the code, and who else is allowed to work on it? #iblai #SovereignAI #GovTech #AIProcurement #DefenseTech --- ## The Short Answer **Helsing handed Germany's procurement agency the source code, documentation and SDK for MissionOSBw, its combat-drone mission software, and the German state keeps ownership. The lesson for any agency buying AI is to hold the code and the right to let others work on it. On ibl.ai you own all the code and the data, so that question is settled at signing.** [Reuters reported](https://www.yahoo.com/news/articles/helsing-hands-germany-ownership-combat-092406282.html) the handover on November 4, 2026, and the German defense outlet [ESUT](https://esut.de/2026/11/meldungen/76551/helsing-bundeswehr-quellcode-kampf/) carried the details the same day. ## What did Helsing hand over to the German government? Helsing, the German defense AI company, gave BAAINBw, the Bundeswehr's procurement office, the first version of MissionOSBw: the complete source code, technical documentation and a software development kit for building new applications and mission modules. Per Reuters, ownership of the software remains with the German state. ESUT reports that it is provided as Government Open Source Software, meaning the code belongs to the state, though neither report publishes the license terms. Helsing's CTO Robert Fink called the handover an important milestone for the Air Force and the Bundeswehr, and "software defined defence in practice", per ESUT. ## What is MissionOSBw and how does it fit Germany's CFSN program? MissionOSBw is a mission operating system for future combat drones and other air warfare systems. It is a core part of the Combat Fighter System of Systems Nucleus, or CFSN, which pairs crewed fighters with uncrewed companion aircraft. The Bundestag's budget committee approved CFSN in July 2026. Industry documents reported by Politico put its value at about €580 million, according to Reuters. CFSN covers two experimental uncrewed combat aircraft, two ground control stations, autonomy software and a government-owned reference architecture. A consortium led by Helsing includes Hensoldt, Rohde & Schwarz, MBDA and Diehl Defence. ## Why is government ownership of defense software unusual? Government ownership is unusual because prime contractors in defense often keep control of key software and intellectual property, and Reuters described this arrangement in exactly those terms. The state then depends on that one company for every upgrade. Europe has lived the cost of that. Reuters set the handover against the long disputes between Dassault Aviation and Airbus Defence and Space over leadership and work share on FCAS, the Franco-German-Spanish future combat air program. We could not confirm the claim, made in some social posts, that this is the first Western defense program to separate AI software ownership from the contractor. Reuters calls it unusual, not first. ## Is owning the source code enough to avoid vendor lock-in? Owning the code is necessary but not sufficient. The second half is whether anyone else can work on it. MissionOSBw follows the Modular Open Systems Approach, so components talk through defined interfaces and can be replaced separately. ESUT reports the Bundeswehr can develop the software further itself or have other companies do so, using the SDK and documentation. That is what turns ownership into leverage at the next contract. ESUT also notes the benefit depends on how consistently the open interfaces are implemented. Code without documentation, or interfaces only one vendor understands, is ownership on paper. ## What should any agency take from the MissionOSBw handover when buying AI? The procurement lesson travels well beyond defense: write ownership into the contract before the work starts. Germany's handover came with the first version of the software, not after years of dependency. Four questions settle it. Who holds the source code? Is there documentation and an SDK good enough for another team to extend it? Can the agency choose and change the model underneath? And can it run everything inside its own perimeter? Our analysis of [Canada's Cohere stake](/blog/sovereign-ai-code-ownership-vs-government-equity) makes the same point from the other side: equity in an AI company does not give any one agency control of its AI. Holding the code does. ## How does ibl.ai give agencies ownership of their AI software? On ibl.ai you own all the code and the data, the platform runs model-agnostic across any LLM, there is no per-seat pricing, and you can deploy anywhere, from your own cloud to GovCloud or a fully air-gapped network. Agencies receive the platform's source code, so their own engineers or any contractor they choose can extend it. Access is governed by [roles and RBAC](/docs/os/organization-settings/roles), and every action lands in an [audit log](/docs/os/analytics/audit). ibl.ai is family-owned and operated from New York, NY, and our engineers build alongside the agency's team rather than holding the code back as leverage. *Sources: the handover, ownership terms, CFSN value and FCAS context from [Reuters via Yahoo News](https://www.yahoo.com/news/articles/helsing-hands-germany-ownership-combat-092406282.html), November 4, 2026; Government Open Source Software status, MOSA, further development rights, CFSN contents, committee approval and the Robert Fink quote (our translation) from [ESUT](https://esut.de/2026/11/meldungen/76551/helsing-bundeswehr-quellcode-kampf/). The brief called this the first Western defense program to separate AI software ownership from the contractor; no source we found says so, and Reuters calls it unusual.* ## Why does owning the AI stack matter? **ibl.ai is the agentic AI platform where you own all the code and the data. You self-host the entire stack inside your own perimeter, run it model-agnostic across any LLM and switch anytime, and pay by usage with no per-seat pricing — so you can deploy anywhere: your cloud, on-premise, GovCloud, or fully air-gapped.** - **You own all the code and the data.** Full source code under a perpetual license, running on your infrastructure. Not API access to someone else's platform — the stack itself is yours. - **Model-agnostic.** Run any LLM — Claude, GPT, Gemini, Llama, Command, or your own fine-tune — and switch providers without rewriting the platform. - **No per-seat pricing.** Usage-based billing against a budget cap you set. Cost tracks what your organization actually uses, not how many people you employ. - **Deploy anywhere.** Your cloud, your VPC, on-premise, GovCloud, or a fully air-gapped network with no outbound connectivity. 1.6M+ users across 400+ organizations run the platform this way, including NVIDIA, MIT, and Syracuse University. ibl.ai is family-owned and operated from New York, NY — a U.S.-headquartered, domestically-owned long-term partner, not a vendor that sells licenses and moves on.