Consider the six months before the software. In GitLab’s account of Sigma Defense, establishing a software factory once took about that long and roughly $4 million. A shared environment brought setup down to three to five days and about $400,000. The obstacle was repeated infrastructure and isolated teams. That is a useful entry into a defense company whose work begins where separate systems have to meet.
- Connects military sensors, networks, and mission software.
- Sells communications equipment, integration, and shared software infrastructure.
- Builds for ships, forward bases, and unreliable connections.
A U-2 problem that kept growing
Scott Ritchie and Thor James founded Sigma in 2006. Both had served in the Air Force; Ritchie retired after 22 years as a chief master sergeant. The original assignment was wonderfully specific: support the U-2 aircraft’s data-link satellite relay program. Reconnaissance had produced information. Somebody still had to get it somewhere useful.
In Ritchie’s account of the early business, that work expanded into unmanned aircraft, the Predator Squadron Operations Center, and full-motion video for intelligence users. The recurring problem traveled well. A new platform could improve collection while leaving the handoff to analysts and operators stubbornly complicated. Sigma followed the handoff.
The cost of starting again
The software-factory experience exposed the same organizational habit. Each project assembled its own tools and environment. Sigma worked with the Navy’s PEO Digital on Black Pearl, a shared development platform built around GitLab. The figures describe that case, rather than a universal software price.
“Collaboration was a fundamental problem.”Josh Metheney · Sigma Defense engineering director
In February 2024, Sigma introduced Sigma Software Studio, taking the shared-platform approach to a wider government market. Its proposition is practical: give development teams maintained infrastructure and built-in security so they can spend more time on applications. Navy and Marine Corps authorization adds something commercial developers rarely have to sell: permission to operate in the intended environment.
Software needs a route to the field
Software Studio addresses production. Olympus addresses movement. Sigma describes four connected Olympus components: Software Factory, Cloud, Hub, and Edge. They cover building applications, governing their distribution, placing distribution nodes nearer operations, and running applications on tactical devices. The distinction matters when the person using the software cannot count on a continuous connection to a distant cloud.
One application’s journey, from development to the operator. Simplified architecture.
Stingray handles another part of the journey. The tactical relay combines communications hardware and software to distribute video and sensor information, support two-way sensor control, and move data over line-of-sight and beyond-line-of-sight links. This is the equipment behind an apparently simple request: let the right people see the feed.
The customer is usually an institution. Sigma serves U.S. military branches, special operations organizations, and other government agencies, with work supporting forces overseas. A software-factory leader needs a repeatable development environment. A communications team needs a working link. A commander needs information that survives the trip between them.
There is concrete fleet work behind the platform language. Sigma’s Forge case study describes its SOLUTE team helping modernize the Navy’s Integrated Combat System through software architecture, automated testing, and shared development infrastructure. It reports delivery of Event Reconstruction Software to destroyers DDG 81 and DDG 123. Replaying tactical data at an operator’s console is a specific use for all that infrastructure.
Buying the missing capabilities
Sagewind Capital invested in January 2021, with the founders retaining significant equity. Sigma then expanded by acquisition. SOLUTE brought software engineering, cyber, cloud architecture, and Black Pearl experience in 2022. Juno Technologies added maritime IT integration and fleet-support expertise in February 2024. EWA followed that April, bringing electronic warfare, threat simulation, and testing.
Aries Defense joined in October 2025 with products linking cameras, drones, and unattended sensors to tactical networks. The next day, Sigma announced a partnership combining Kägwerks’ DOCK-Ultra computing hardware with Olympus. Read together, these deals suggest an integration strategy: acquire or partner for the capabilities needed along the information path. That is an interpretation of the portfolio, rather than proof that every integration is complete.
A contract is a promise with conditions
The business mixes equipment, engineering and sustainment work, and DevSecOps as a service. Its place in the market is between specialized technology suppliers and large systems integrators. Software Studio also competes with a customer’s decision to build and maintain its own development infrastructure. Sigma’s argument is that customers can reuse more of the foundation.
The money requires careful reading. In its February 2026 CANES announcement, Sigma described a SOLUTE award supporting Navy networks: a $42 million three-year base and options that could take the total to $102 million across seven years. That potential total is a contract value, not annual revenue. It buys technical and programmatic services, software engineering, integration, testing, and fleet-readiness support.
The people and the next test
Sigma’s military experience also appears in its workforce. Its 2024 HIREVets Platinum award recognized veteran employment practices; current company material describes almost half the team as veterans. That background can help engineers recognize operational constraints before a product reaches users. Experience still has to translate into tested software and working equipment.
Two 2026 developments sharpen the next test. In June, Sigma announced NSA Commercial Solutions for Classified Trusted Integrator status. In July, it was selected for a six-month SUNet 2.0 prototype supporting secure collaboration and AI development. The prototype is an evaluation step, with potential follow-on production. Selection does not establish a completed rollout.
There is a lesson here for organizations far from defense: stop rebuilding common infrastructure, and test the handoffs early. The conditions matter. Interfaces must fit, security approvals must cover the environment, and disconnected devices still need a communications path to receive fresh information. A platform cannot repeal those constraints. Sigma’s opportunity is to make more of the connecting work repeatable.