Sustainment had a customer, a contract and software designed to help the Air Force find manufacturing suppliers. In the ordinary commercial world, this would be a promising start. In government software, it was an invitation to another waiting room. Before the application could enter service, it needed an Authority to Operate, or ATO. The accreditation effort stalled for nearly a year.
- Second Front supplies the accredited infrastructure beneath other companies’ software.
- Game Warden combines authorization support, hosting and ongoing operations.
- Sustainment’s reported 58-day result shows the value of reusing security work.
Then Sustainment changed its approach. It partnered with Second Front and used Game Warden’s inherited authorization model. The resulting IL2 accreditation took 58 days. Its internal accreditation staffing fell from ten people to three. These are figures from the companies’ published case study, but they illuminate something easy to overlook: a useful application can lose months to the machinery surrounding it.
The software was ready.
The permission was not.
Second Front occupies that awkward interval. Commercial vendors bring applications; government users bring needs and security requirements. Second Front provides a managed environment in which software can be assessed, deployed and kept running. The company sells the work between a successful demonstration and everyday use. In a market fond of dramatic hardware, its most interesting product may be a calendar with fewer wasted pages.
Stop making every supplier
build the same gate
The company’s origins are military. Its founders, former Marines Peter Dixon, Mark Butler and Nate Hughes, had seen the consequences of slow technology acquisition. Another formative figure was Enrique Oti, the founding commander of the Air Force software factory Kessel Run. In his account of building Game Warden, Oti describes repeatedly encountering the same obstacle: talented government teams still struggled to adopt readily available commercial software.
His conclusion concerned capacity. Agencies funded annually, with spending planned years ahead, were poorly positioned to expand hosting and security operations in anticipation of hundreds of arriving vendors. A commercially financed platform could build that capacity earlier. Government software factories had already advanced security automation; Second Front would apply related methods to onboarding and operating commercial applications at scale.
The mechanism is control inheritance. A supplier can use applicable protections already established by the platform rather than recreate an entire compliance environment. Game Warden also supplies the evidence and operating infrastructure around those controls. Application security work remains. The useful analogy is a tenant entering an inspected building: the shared fire system matters, but the tenant still has responsibilities inside the apartment.
Three products, one route into service
Second Front’s suite follows the software’s journey. Workshop moves security work into development, with reusable pipelines, scanning and hardened container images supplied through its Chainguard partnership. Game Warden handles accreditation support and managed hosting. Frontier extends development and delivery to remote devices, vehicles and environments where connectivity is unreliable. The sequence gives engineers a way to consider deployment before development choices become expensive to undo.
After deployment comes the less photogenic business of logs, alerts, updates and incidents. Second Front’s monitoring offering gives teams visibility into performance and security. Its ongoing support takes some infrastructure maintenance off the application builder’s desk. That makes the business a continuing platform and operating relationship, with contracted licensing and hosting, rather than a consultant handing over a compliance binder and departing.
The million-dollar decision
OpsLab offers a second view of the economics. The aviation scheduling company estimated that pursuing IL5 accreditation itself would cost $1 million and take up to two years. It would also divert staff from its product. Second Front assessed the architecture and migrated the application onto Game Warden using AWS infrastructure. The published account reports a 90-day route and use at 44 Air Force bases and two Navy bases.
That million dollars was OpsLab’s estimate of its own route, not a published Game Warden price. The distinction matters. A supplier comparing approaches should count security staff, infrastructure, ongoing maintenance and delayed revenue, alongside the platform agreement. Accreditation savings have meaning only against the work actually avoided. The case for outsourcing gets stronger when the alternative is assembling a separate team to maintain unfamiliar government infrastructure.
“Control is an illusion”
Tyler Sweatt, reflecting on his first year as CEO, 2024
A queue with venture backing
Investors have financed that ambition through a $32 million Series A in December 2022, a $40 million Series B in November 2023 and a $70 million Series C announced in September 2024. Salesforce Ventures led the last round; Battery Ventures joined existing investors. CEO Tyler Sweatt’s accompanying essay reported 475% revenue growth over eighteen months. That is company-reported growth, without an absolute revenue figure.
Second Front’s positioning rests on breadth: development, deployment and operations across civilian, defense and classified environments, with cloud-provider relationships rather than a single application of its own. There are alternatives. Palantir FedStart also hosts vendors inside an accredited environment. Teams can build their own. Leidos, meanwhile, became Second Front’s preferred services partner in August 2025, showing how an established integrator can operate beside the platform.
The route is widening. Cohere announced FedRAMP High authorization through Game Warden in under 90 days in May 2026. July brought an ATO Accelerator for Azure Government. In September, American Intelligence Corporation reported its own High-level certification through the platform in under 60 days. Each is a specific deployment story; none turns a brisk timetable into a promise for every applicant.
Borrow the machinery,
keep the responsibility
The lesson readers can copy is to establish the delivery path before promising a delivery date. Ask which controls can be inherited, what the application must change, who maintains it and which network the buyer actually uses. A platform helps when its environment fits the workload. A unique architecture, an unsupported destination or a need for extensive operational control can favor another route. Permission also does not create demand. Sustainment already had a customer. Second Front helped the software reach that customer.