No application or relationship exists. This record does not establish eligibility, availability, funding, recommendation, provider interest, or authorization to apply.

Provider
U.S. Space Force
Kind
Non-dilutive defense innovation
Status
active; solicitation-specific
Timing
Active opportunities shown: DoW SBIR Specific Topic 26.BX Release 4 is open July 22–August 18, 2026; PY26.2 TACFI has accepted submissions continuously since June 5, 2026.
Eligibility
SBIR applicants must be U.S.-based for-profit small businesses with no more than 500 employees and a qualifying principal investigator. STTR requires a U.S. research-institution partner and statutory work shares. TACFI is for qualifying successful Phase II projects and requires matching funds.
Access notes
The official page lists specific and later-stage opportunities, not a blanket open-topic entitlement. Phase II and Direct-to-Phase-II pathways typically require a U.S. Space Force customer, and all applications must satisfy the exact solicitation and federal registrations.
Official link checked
2026-07-25
Relationship
indexed only; no formal relationship

Potential fit and evidence boundary

Defensive resilience, logistics, communications, and assurance

Evidence boundary: Official SpaceWERX funding page reviewed. It establishes current dates, program phases, broad eligibility, and customer requirements; it does not establish a matching topic, customer, eligibility, or endorsement.

Task-specific matches

No bounded task match is recorded.

Proposed founder action—not undertaken

Apply the project's civil-and-defensive dual-use screen before topic fit: consider only defensive resilience, logistics, communications, or assurance with a precise customer need; exclude autonomous weapons and offensive integration, and seek separate authorization before any action.

Conflicts and change triggers

Conflicts: Defense mission alignment, customer sponsorship, export control, security obligations, data rights, foreign influence, and the project's prohibited-use boundary require enhanced independent review.

What would change this record? A specific defensive topic match, qualifying entity and customer evidence, revised solicitation dates, or a policy review clearing the use case would change priority.

Verify on the official provider page (opens external site in a new tab)

Substantive opportunity lead; independent review and official verification required before action · Last edited 2026-07-25 · Suggest a correction

Accountability record

How to inspect this page

Scope: Opportunity opp-spacewerx

Page citations and accountability links

Assumptions and limits

  • Official SpaceWERX funding page reviewed. It establishes current dates, program phases, broad eligibility, and customer requirements; it does not establish a matching topic, customer, eligibility, or endorsement.
  • Indexing and task matching do not establish eligibility, recommendation, availability, funding, provider interest, a relationship, or authorization to apply.

What would change this page?

A specific defensive topic match, qualifying entity and customer evidence, revised solicitation dates, or a policy review clearing the use case would change priority.

People, review, and conflicts

Prepared by
GShips Project
Editorial status
substantive editorial review; independent review pending
Editorial reviewer
GShips Project editorial synthesis
Last editorial review
2026-07-25
Independent review
pending
Independent reviewer
No independent reviewer assigned
Last independent review
No independent-review date exists
Last content edit
Not recorded separately
Official source or link verified
2026-07-25

Declared conflicts

  • Defense mission alignment, customer sponsorship, export control, security obligations, data rights, foreign influence, and the project's prohibited-use boundary require enhanced independent review.
  • The maintainer intends to explore a commercial venture based on some GShips work. No entity, outside funding, customer, sponsor, or indexed-organization relationship currently exists.

Suggest a correction to this page