DARPA published a Request for Information on June 16, 2026 seeking industry input on technologies and operating concepts capable of restoring critical space services on "tactical timelines of hours to weeks" following hostile action, debris strikes, or anti-satellite weapon attacks. Responses are due July 8, 2026. The RFI, posted to SAM.gov, is market research only — no solicitation or contract award is attached.
Background
U.S. military space infrastructure has grown increasingly contested. The Victus Nox mission demonstrated a 24-hour launch notice capability for a tactical satellite, proving that rapid reconstitution is achievable at small scale — Firefly Aerospace completed that responsive space demonstration. DARPA's new initiative builds directly on that baseline and on the Space Force's Tactically Responsive Space (TacRS) program, which has worked for years to compress the months-long timelines traditionally required to design, build, launch, and operate a replacement satellite.
The RFI asks industry what it would take to actually reconstitute lost capability — not just survive the loss of it. By framing the problem around restoring services to "minimum levels or higher," DARPA is signaling that its interest extends beyond hardware redundancy to operational recovery: the ability to stand up replacement capability before an adversary can exploit the gap created by a lost asset.
Key Details
The RFI organizes its inquiry across five broad areas: space vehicles, satellite payloads, launch vehicles, space vehicle-to-launch vehicle integration, and concepts of operations. Within those areas, DARPA identified specific technology priorities:
- Reconfigurable and software-defined payloads that can be repurposed after launch
- Rapid satellite manufacturing and assembly, including on-orbit approaches
- Multifunctional and multirole satellite architectures
- Very low Earth orbit (VLEO) operations, which offer shorter revisit times at low altitudes
- Alternative positioning, navigation, and timing (PNT) solutions that do not depend on GPS
- Spacecraft survivability and resiliency enhancements
- Supply chain optimization to accelerate hardware availability for surge production
The concepts of operations category is notable because it asks industry not just for hardware answers but for ideas about how reconstitution missions would actually be planned and executed under combat conditions — a gap that hardware-centric acquisition programs rarely address at the RFI stage.
DARPA did not publish any estimated program value or follow-on procurement timeline alongside the RFI. The agency characterized the effort as an exploration of what the industrial base can credibly offer before defining a formal program structure.
What It Means for Contractors
The RFI signals a significant near-term business development window for companies across the space industrial base — from traditional primes to small commercial launch providers and satellite bus manufacturers.
Software-defined payload developers stand to benefit most directly. The RFI's emphasis on reconfigurability aligns with a broader Pentagon shift away from single-mission satellites toward platforms whose function can be updated after launch, reducing the cost and time of reconstitution from months to potentially days. Companies with demonstrated software-defined radio or payload-agnostic bus architectures have the clearest on-ramp to a follow-on program.
Commercial launch providers face a more competitive entry point. DARPA's interest in rapid launch integration — compressing the schedule between a reconstitution decision and an operational satellite on-orbit — favors providers with demonstrated quick-response launch manifests. The Victus Nox demonstration used Firefly Aerospace; the RFI does not name any incumbent and explicitly invites alternative approaches.
For integrators and defense primes, the concepts of operations category creates an opening that hardware-only competitors cannot easily fill. Companies that can combine system architecture, mission planning software, and operational concepts in a single response position themselves as potential prime contractors if DARPA converts the RFI into a Broad Agency Announcement or Other Transaction Authority solicitation.
Supply chain optimization — one of the listed technology areas — reflects a persistent problem DARPA explicitly wants industry to solve: lead times for radiation-hardened components, precision optics, and specialized electronics remain measured in years, not months. Contractors with established space-grade component supply networks or alternative commercial-off-the-shelf hardening approaches have a concrete competitive differentiator to present in their July 8 responses.
No protest risk attaches to an RFI at this stage. Contractors should treat the response as a positioning document for the follow-on solicitation rather than a bid, and prioritize demonstrating proven capability over aspirational roadmaps.
What It Means for Contractors
DARPA RFIs carry no funding and no commitment, but they are the agency's primary mechanism for scoping a technology landscape before drafting a Broad Agency Announcement. Companies that respond with credible capability demonstrations position themselves as known quantities when the follow-on solicitation drops — typically 6 to 18 months after an RFI closes. The rapid reconstitution problem space is broad enough that responses from satellite bus manufacturers, launch providers, ground segment integrators, and software-defined radio firms all fall within scope.
The emphasis on hours-not-days reconstitution narrows the field to firms with genuine on-demand launch access or pre-positioned satellite bus stockpiles. Traditional procurement cycles cannot meet that timeline. Companies working with responsive launch vehicles — including small-lift commercial providers — and those developing satellite buses designed for rapid integration and checkout should treat this RFI as a direct solicitation for their core value proposition. The RFI response is best framed around demonstrated timelines from existing programs rather than projected future capability.
For software and ground segment firms, the reconstitution problem extends beyond hardware. Command-and-control software that can transition tasking from a degraded constellation to a freshly launched replacement within hours is an equally critical gap. Firms with battle-tested ground software architectures used in operational LEO constellations should emphasize automated handoff, dynamic tasking reassignment, and resilience to partial outages in their RFI responses.
- Submit by the RFI deadline even with partial solutions. DARPA program managers use RFI responses to calibrate what the market can actually deliver. A partial-capability submission that honestly defines the current state and a credible development path is more useful — and more memorable — than a non-response.
- Prioritize relationship-building with the program office. DARPA BAAs are structured to fund a portfolio of performers, not a single prime. Early technical exchanges with the program manager before a BAA drops increase the probability that your approach influences how the eventual solicitation is scoped.
