PARRY LABS / GOVERNMENT OPPORTUNITY INTELLIGENCE — researched October 9, 2026

The Army has created a route for outside NGC2 applications. Parry Labs should qualify STRATIA and VIW at the integration boundary.

Government target: U.S. Army CPE C2IN, PM C2 Applications, Product Manager Application Store and Pipeline (PdM ASaP). Why now: the Army’s October 7 initial application awards confirm NGC2 scaling; its published ASaP program is designed to onboard third-party software. Hypothesis: Parry’s STRATIA or Virtual Integration Workspace could support application integration and validation across tactical edge platforms, but the Army may view these as middleware/dev tools rather than an eligible warfighting application.

Verified program movement

The Army’s official ASaP page explicitly promises software onboarding, SDKs, APIs, sandbox, security testing, CI/CD and an application storefront for commercial, government and Soldier developers.
On October 7, 2026, the Army announced initial NGC2 application contract awards for I Corps; this is evidence of active delivery, not proof of an open STRATIA contract.
The NGC2 Army Connect developer portal lists Lattice and Foundry SDKs and describes a continually evolving full-stack ecosystem, with additional SDKs to follow.
Parry’s published product catalog describes STRATIA as integration software, VIW as a virtual test/validation environment and Edge Compute as deployable hardware.

Specific technical fit

STRATIA: test whether its modular software services can contribute deployable adapter/container/application functions conforming to Army SDK, cybersecurity and data semantics.
VIW: ask whether any third-party digital-integration/testing environment is required upstream of ASaP’s government-managed pipeline. A process overlap could make VIW irrelevant as a procured product.
Edge Compute: only an indirect opportunity if the Army’s infrastructure office or integration contractors are evaluating compatible tactical edge hardware; ASaP itself is principally a software path.
Existing partnerships matter: Parry has publicly announced a GDLS five-year software enterprise agreement and AeroVironment P550 integration. Do not treat those existing relationships as new leads.

Who to contact and where

PM C2 Applications / PdM ASaP: official Army organization page and ASaP program page are the correct program routing path. No verified named ASaP government product lead or public direct email was established from those pages.
ACC-APG NGC2 industry mailbox: usarmy.apg.acc.mbx.army-c2-solutions@army.mil in the NGC2 CSO notice. Ask for current third-party application onboarding and the ASaP technical authority; this is contracting routing, not an engineering owner.
Eric J. Roberts: eric.j.roberts48.civ@army.mil is the notice’s published escalation/issues contact. Assignment to ASaP itself is unverified; use the general mailbox first.

Concrete engagement strategy

Prepare an unclassified STRATIA/VIW architecture map that identifies an actual API adapter, edge workload or integration-validation use case, plus documented security/deployment traits. Avoid a generic enterprise-software pitch.
Ask PdM ASaP which SDKs, onboarding procedures, software classes and sandbox criteria apply, and whether integration middleware/tooling is eligible—or whether Parry must partner with an accepted application provider.
Request a technical intake for a narrowly scoped demonstration such as integrating one sensor/mission application into a compliant NGC2 test workflow; first verify feasibility and data access restrictions.
Do not seek to submit to the July 2026 Scalable Software Applications call: the Army explicitly says that call closed August 6. The parent CSO remaining open does not permit unsolicited proposals.

Suggested routing message

Subject: NGC2 PdM ASaP — third-party mission-software integration qualification

Hello NGC2 industry team — Parry Labs develops STRATIA mission-integration software and the VIW test environment for modular defense platforms. We reviewed the Army’s Application Store and Pipeline initiative and would like to identify the appropriate technical owner to determine whether application interoperability tooling or deployable mission-service adapters can be qualified for the NGC2 ecosystem. Could you direct us to the published ASaP onboarding process, SDK/security requirements and technical contact?

Decision-making questions

Is STRATIA’s function an application, middleware, test utility or infrastructure service under ASaP?
What actual SDK/data-model/security accreditation applies to third-party service adapters?
Does Army ASaP have a funded need for digital engineering tools or only onboard applications provided at the vendor’s expense?
What technical demonstration would validate unique value versus incumbent government/Anduril/Palantir/Raft capabilities?

Confidence, risks and sources

High confidence: ongoing NGC2 scaling, published third-party application onboarding, Parry’s products. Moderate: technical relevance of integration software. Unknown: purchasing need for STRATIA/VIW, program architecture rights, validated contact, actual work package, contract and value. The pilot is a discovery route, not a verified procurement.