Consider the peculiar predicament of a fighter jet. It is an elaborate computer with wings, yet putting fresh software on it can be surprisingly difficult. The application might be finished. The engineers might be ready. Between their laptops and the aircraft sits a thicket of security controls, incompatible environments, and connections that cannot be assumed to exist.
- Defense Unicorns delivers software to military systems, including offline ones.
- Its tools package dependencies, secure the runtime, and help manage updates.
- Free foundations lead to paid enterprise products, fleet tools, and support.
Defense Unicorns has made that uncomfortable interval its business. Its customers include the Army, Navy, Air Force, and Space Force, along with the integrators serving them. The product is infrastructure: the machinery that helps someone else’s application reach its destination and keep working there.
A fighter jet with an update problem
In March 2026, the company and the Air Force Sustainment Center Software Directorate reported installing and upgrading software in minutes inside an F-22 open mission system compute enclave. That is a precise achievement. It concerns a particular computing environment aboard the aircraft, with fleet-wide operational use described as a future step.
The distinction matters because military technology stories tend to jump straight from demonstration to destiny. Here, the interesting part is smaller and more useful. An approved software payload could move onto a suitable onboard environment without every update becoming a bespoke integration exercise.
“UDS enabled the rapid deployment of a critical capability and the flexibility to adjust.”
Lt Col Gregory “LAB” Bieler
March 2026 F-22 announcement
The founders knew the terrain. Rob Slaughter, Jeff McCoy, and Andrew Greene came through the defense software factory ecosystem before founding the company in 2021. Their experience included efforts such as SpaceCAMP and Platform One. They had encountered the distance between writing useful code and delivering useful capability.
Pack the internet before you leave
Ordinary software installation often borrows things from elsewhere: a container image, a package, a repository. In a disconnected network, that apparently minor errand becomes a dead end. OpenSSF’s discussion of air-gapped development describes quieter failures too: expired tokens, blocked registries, unreachable vulnerability feeds. Connectivity is a dependency hiding in plain sight.
Zarf, the company’s open-source packaging tool, gathers the files and dependencies an application needs before it travels. The package can then be transferred into an isolated environment and installed there. Picture packing for a trip where there will be no shops. Forgetting one small item can defeat an otherwise excellent itinerary.
- 01 / GatherApplication + dependencies
- 02 / PackagePrepare for approved transfer
- 03 / DeployInstall beyond the internet
A Navy SBIR account traces early Air Force research, feasibility work with the Naval Postgraduate School, and subsequent applications for submarine software delivery. That progression gives the idea some weight. The packaging problem crossed service boundaries because the missing connection was not unique to one aircraft or vessel.
UDS, now marketed as Unified Defense Stack, builds a wider system around delivery. UDS Enterprise supplies a hardened runtime and shared services. UDS Fleet addresses distributed systems at the tactical edge. UDS Registry stores and distributes software artifacts with signatures, component inventories, and vulnerability information. Pepr automates Kubernetes resource behavior. Each deals with a different part of keeping software usable after the developer presses release.
Free foundations. Paid responsibility.
The business model begins with an open foundation. UDS Base is free under AGPL-3.0; commercial Enterprise and Fleet offerings add capabilities, hardened images, compliance artifacts, and support. Zarf was contributed to OpenSSF. Buyers can inspect and use foundational code, while paying Defense Unicorns to take on more of the integration and maintenance burden.
That places the company among enterprise infrastructure suppliers, with a defense-specific delivery problem at its center. Alternatives include maintaining an internal stack or adopting a broader Kubernetes platform. The practical comparison is how much assembly, security work, and disconnected operation the customer’s own engineers must handle.
There is a commercial wrinkle worth noticing. Paid licenses are priced per unique environment, defined through infrastructure, Kubernetes distribution, classification or impact level, and geographic location. Individual ships, aircraft, and vehicles can matter to that calculation. Buyers need an inventory of deployment environments before they can sensibly compare quotes.
For a program office, that means the starting question is concrete: where must this application run, and who will keep it running? An enterprise team can use the platform to standardize cloud and on-premises deployment. A team managing dispersed systems needs visibility and update controls across those destinations. A software vendor can package an application for the environments its government customer requires. The attraction is repeatability: spending less effort rebuilding the surrounding delivery machinery each time a useful application finds another mission.
The minutes need a footnote
Defense Unicorns announced a $35 million Series A in March 2024, co-led by Ansa Capital and Sapphire Ventures. In January 2026 came a $136 million Series B led by Bain Capital, at a valuation above $1 billion. The name had acquired a financial punchline.
Its March 2025 SAIC partnership offered another route to customers: embedding UDS in an established integrator’s delivery ecosystem. In September 2026, the company announced a single-award procurement vehicle with a $350 million ceiling. That permits orders; it does not establish $350 million in sales. The same announcement reported use across more than 100 mission systems and organizations.
Nor does packaging erase the physical and institutional limits. Target systems need compatible computing environments. Transfers still require approved procedures. Compliance evidence supports an authorization decision; software does not award itself permission to operate. In July 2026, the Navy’s shipboard evaluation announcement described the next testing phase, a useful reminder that adoption involves stages.
What to steal from the air gap
For an ordinary engineering team, the most useful lesson is wonderfully unglamorous: rehearse the deployment with the network conditions your users actually have. Inventory dependencies. Package deliberately. Automate repeatable checks. Decide who owns updates after installation. These habits travel well beyond defense.
The company’s wager is that delivery deserves its own engineering discipline. A submarine makes the argument easy to understand. You can have excellent software, talented developers, and an urgent need. If the installer is still waiting for the internet, none of them gets the last word.