Solo-executable Phase I proposals · Generated 2026-05-15
| Topic | Solicitation Ask | Component | Funding | Close | Posture | Pitch & Competitive Edge |
|---|---|---|---|---|---|---|
|
ARM26BX01-NV001 ↗
In-Transit Visibility Blockchain
SAM.gov · DoW SBIR 2026 BAA
|
|
Army Phase I | ~$300K | 2026-06-03 19 days out |
Solo · framing risk
|
Reframe "blockchain" as Verifiable Transport Ledger. SHA-256 wire-level integrity makes every transfer cryptographically auditable without DLT consensus overhead. Multi-modal physical tags map exactly to QUIC connection migration — convoys move, transfers resume after halts, commanders see a Prometheus dashboard.
Edge Solves the topic's intent without paying blockchain's cost. Production code Day 1; most ITV competitors propose paper DLT.
Risk: "blockchain" keyword bias — bring credentialed DLT consultant only if necessary to defuse it.
Full Statement of Objectives (from DSIP)ObjectiveThis topic seeks to develop and optimize a real-time In-Transit Visibility (ITV) system that enables military commanders and logistical staff from Corps to Battalion level to overcome limitations in tracking and managing the movement of supplies and personnel through the integration of data from various enterprise systems and sensor technologies. The objective is to enhance command and control (C2) of logistical operations for improved situational awareness and responsiveness, enabling proactive redirection of assets, accurate arrival time predictions, and efficient resource allocation while minimizing delays, disruptions, and manual data processing. DescriptionMilitary logistics systems offer significant potential for improvement, yet their ability to fully address the complexities of modern operations is limited by disparate data sources, manual reporting processes, and a lack of real-time visibility into the movement of assets. To overcome these challenges, novel approaches that integrate decentralized distributed ledger, sensor fusion, automated data collection, and user-friendly visualization tools within the Command Post Computing Environment (CPCE) are needed to enable a robust and adaptive ITV capability. This topic focuses on advancing near real-time logistics tracking and management, with a specific emphasis on providing commanders with a comprehensive common operating picture (COP) of the location, status, and contents of all in-transit assets (Classes of Supply I-X). Proposed solutions should prioritize interoperability, modularity, and scalability, ensuring that the ITV system can be integrated across various existing military platforms (AFRL's distributed ledger technology infrastructure, CPCE, mobile handheld devices, mounted systems) and enterprise databases (TCAIMS-II, IBS, GATES, CMOS) with minimal customization. Research should explore predictive modeling algorithms, user-defined alert systems, and secure data sharing protocols to ensure reliability, resilience, and security under dynamic operational conditions. The performance metrics outlined below are intended as target thresholds, not hard requirements, and are meant to illustrate the desired technical capabilities. Proposals that meet some, but not all, of the listed metrics or that propose alternative approaches will be evaluated equally and are strongly encouraged. The goal is to cast a wide net and support a range of innovative technologies aligned with the problem space. Quantifiable Performance Requirements: Proposals should address the following measurable technical performance metrics: Location Accuracy: The system should achieve 95% accuracy in reporting the location of tracked assets under various operational environments. Update Frequency: The system should provide location updates at a minimum of every 15 minutes for ground transport and every 15 minutes for air transport. System Latency: End-to-end latency from data acquisition to display on the COP should not exceed 3 minutes. Platform Compatibility: The solution should operate effectively across CPCE, mobile handheld, and mounted computing environments, requiring no more than 10% system redesign or configuration for each platform. Deployment Time: Deployment/setup time for deploying a single tracker should not exceed 1 hour, and user training should require no more than 2 hours. Physical tags: Should be multi-modal, to include the ability to leverage satellite, cell towers, and internet. The tags should also be able to transmit encrypted data to AFRL's existing distributed ledger technology infrastructure. Distributed Ledger Technology: Should be able to tokenize assets, creating a digital twin and be able to connect with AFRL's existing distributed ledger technology and be able to create a unique chain that interoperates with AFRL's existing one. Proposal Expectations: Successful proposals should include hypothesis-driven research that combines fundamental modeling with prototype development or proof-of-concept demonstration. Teams must outline an experimental validation plan, including testing in simulated operational scenarios with representative data sets and user interactions, with clearly defined success criteria for each milestone. Cross-disciplinary approaches, integrating software engineering, data analytics, human-computer interaction, and military logistics expertise, are strongly encouraged. Phase IThis topic is accepting Phase I submissions for a cost limit of $300,000 and a 6-month period of performance. A white paper outlining how the proposer will meet the expected metrics outlined in the topic description. Phase IIA successful deliverable is a distributed ledger that should be able to tokenize assets, creating a digital twin and be able to connect with AFRL's existing distributed ledger technology and be able to create a unique chain that interoperates with AFRL's existing one. Phase III / Dual-UseSupply Chain & Asset Tracking: Enables faster, more accountable disaster relief operations. Supports interagency coordination across federal, state, and local responders. Ensures asset provenance and reduces fraud during urgent mobilizations. Strengthens public trust and delivery of mission-critical aid. Fraud Prevention in Grants/Contracts: Addresses a high-visibility government risk area: financial accountability. Improves the auditability and efficiency of public sector funds distribution. Demonstrates responsible tech innovation by stopping fraud before it scales. Applicable across FEMA disaster grants, COVID relief, education funding, or infrastructure stimulus. Reinforces the government's stewardship mission. Tamper-Proof Government Records: Mission Relevance: Ensures continuity of governance and auditability of official data in contested or degraded environments. Aligns with continuity-of-operations planning. Transportation & logistics: Used in real-time, multimodal shipment tracking and custody handoffs with automated milestone verification. Retail & e-commerce: Used in fulfillment visibility, returns fraud mitigation, and last-mile proof-of-delivery. Pharmaceuticals & healthcare: Used in compliant track-and-trace, cold-chain condition logging, and recall execution. Food & agriculture: Used in provenance tracking, contamination traceback, and sustainability/ethical sourcing attestation. Airports & industrial campuses: Used in workforce credentialing, zone access logs, and synchronized movement tracking of personnel and critical assets. KeywordsDistributed-ledger; tokenization; blockchain; encryption; in transit visibility |
|
DON26BZ01-NV022 ↗
Extremely Wide Band Digital Recording for AI/ML
SAM.gov · DoW SBIR 2026 BAA
|
|
Navy Phase I | ~$240K | 2026-06-03 19 days out |
Solo
|
Petabyte-scale tactical-edge ML pipeline. Resumable transfers + SHA-256 wire-level integrity + SIMD-accelerated hashing keep up with line-rate sensor ingest and prove every chunk arrived intact. Storage SSDs are COTS — no partner.
Edge AI training datasets are useless without bit-integrity provenance — that's exactly what Zephyr's wire-level SHA-256 does. WebTransport gives data engineers a no-agent validation console.
Full Statement of Objectives (from DSIP)ObjectiveDevelop a small and dense data recorder that can store >= 8 Petabytes of information in <= 4 u of 19-inch rack space, will be scalable and flexible in nature, and will demonstrate the interfacing to >= two different interface protocols each supporting > 400 GB/sec data transfer rates for >= 30 seconds. DescriptionIn today's environment, emphasis is put on how Artificial Intelligence/Machine Learning (AI/ML) can solve most of the Department of War's (DOW) problems as long as the AI/ML algorithms are trained correctly. This training requires vast amounts of relevant data. Unlike commercial websites where the algorithm developers can have the public train them based on security selection images, the DOW does not have vast stores of relevant data sets much less a global community to train the algorithms. Unfortunately, very few to none of the fielded program of record (POR) systems have the ability to record (at the tactical edge) relevant data products in sufficient quantity to help algorithm developers. This SBIR topic is intended to develop extremely deep sensor data recorders for implementation/fielding on tactical platforms for tactical sensors at the tactical edge. These recording devices must be able to be integrated easily into the platform's sensor suite and be able to record the relevant data products for use in future algorithm development and training. These recorders must easily adapt to various networking infrastructures (e.g., InfiniBand, NVLINK, PCIe, and or Ethernet, etc.) and support the extreme streaming bandwidths for wideband (500MHz and greater I/Q data) Radio Frequency (RF) digital data and high definition (4K or greater) streaming video. These recording devices must be scalable in nature, at a minimum take up less than or equal to 4u of face plate volume in a 19-inch rack, and record greater than 8 petabytes of storage. These devices must meet all NSA data at rest encryption requirements and be developed in a manner to easily acquire a volatility certification letter. These prototype devices will be installed on manned and unmanned platforms — they must be developed with remote and/or autonomous operations in mind. Key requirements: Less than or equal to 4u of 19-inch rack volume; class B shipboard installation EQT; >8 petabytes of data storage; NSA data-at-rest encryption; non-volatility certification; multi-network configurable; minimum two networking options each sustaining >400 GB/s; shipboard installation environmental qual; sensor data parse/tag; local + remote record/playback. Phase II work may become classified. Contractor must be U.S. owned, able to acquire secret-level FCL and personnel security clearances per NISPOM/DCSA. Phase IDevelop and provide a detailed schedule out through Phase II options, plus a detailed technical description for success. Initial deliverable: kickoff meeting detailing how they will reach the final briefing. Final briefing addresses: ≤4u of 19-inch rack volume; class B shipboard EQT; >8 PB storage; data-at-rest security; non-volatility certification; multi-network architecture; remote/local interface descriptions; UI examples and recording/library/playback schemas; cost and schedule plan. Phase I option: showcase software modules + fundamental breadboard designs; present detailed Phase II plans. Phase IIKickoff meeting with detailed development plan, separated recurring vs non-recurring costing, security and testing plans. Plans cover: technical, security, EQT, lab testing at developer + government labs (multiple network types), ship installation + at-sea testing (Phase II Option). System must meet: ≤4u rack space; >=8 PB storage; minimum two networking options each sustaining >400 GB/s; shipboard env qual; data-at-rest encryption + volatility-on-posture-change; sensor parse/tag; local + remote record/playback. Minimum 2 lab demos at developer facility + 1 integration at government lab. Phase II Option, if exercised, focuses on at-sea installation/test readiness. Phase II work likely classified. Phase III / Dual-UseAwardee describes transition to a Navy program of record (POR): how it will be used in the POR and the initial concept of what data products will be recorded. Any commercial industry needing low-cost optical processing on extremely large data sets will benefit. KeywordsDigital Recorders: Radar Interfaces; Combat Control Interfaces; Electro Optic data; Continuous Digital Intermediate Frequency; CDIF; Burst Digital Intermediate Frequency; BDIF |
|
DON26BZ01-NV013 ↗
AI-Assisted Modernization of Theater Mission Planning Center Software
SAM.gov · DoW SBIR 2026 BAA
|
|
Navy Phase I | ~$240K | 2026-06-03 19 days out |
Solo · AI-framing risk
|
Vanguard as software-modernization prime. Zephyr underpins the data layer between legacy TMPC modules and modernized tooling. Phase I AI framing: off-the-shelf AI (Claude/Copilot-class) accelerates the modernization work itself; formal AI integration goes in the Phase II roadmap.
Edge Pure software, no partner. We own the plumbing — AI vendors plug into us.
Risk: if Navy evaluators read "AI-assisted" as "AI is the deliverable," we lose. Mitigate by quoting topic language carefully in Section 2.
Full Statement of Objectives (from DSIP)ObjectiveDevelop an AI-driven toolset to automate the modernization of Theater Mission Planning Center (TMPC) software, focusing on refactoring legacy code, optimizing performance, integrating advanced cybersecurity, and ensuring compatibility with modern and next-generation mission systems. DescriptionTMPC software is built on legacy code that presents challenges in maintainability, performance optimization, cybersecurity, and integration with evolving mission systems. Current modernization efforts rely on manual refactoring, which is time-consuming, error-prone, and costly. There is a critical need for an AI-driven capability to automate code refactoring, optimize computational efficiency, and integrate cybersecurity features without disrupting TMPC's core functions. This effort will enable seamless software upgrades while maintaining backward compatibility with existing operational platforms. The proposed solution will leverage machine learning (ML) and natural language processing (NLP) to analyze, refactor, and optimize TMPC's codebase while preserving mission-critical functionalities. Additionally, AI-assisted software validation and security enhancements will ensure that modernized TMPC software meets the evolving requirements of Navy mission planning environments. Phase II work may become classified. Contractor must be U.S. owned with secret-level FCL and personnel clearances per NISPOM/DCSA (NAVAIR). Phase IConduct an analysis of TMPC's existing software architecture to identify modernization needs. Develop conceptual AI-based models for legacy code analysis, refactoring, and cybersecurity integration. Demonstrate proof-of-concept AI-driven refactoring on a representative TMPC software component. Phase I effort includes prototype plans for Phase II. Phase IIDevelop a prototype AI toolset for TMPC code modernization. Integrate cybersecurity enhancements and automated validation/testing. Conduct functional and performance testing and validation. Ensure compatibility with existing and next-generation TMPC hardware/software. Phase II work may become classified. Phase III / Dual-UseBring the AI tool from prototype to full-scale, improving the speed, security, and cost-effectiveness of software upgrades. The same technology that helps the Navy can also help the private sector fix and secure older software more easily. KeywordsAI-assisted; Legacy Code; Machine Learning; Natural Language Processing; Tomahawk; Mission Planning |
|
DAF26BX02-NV502 ↗★
Project Authentication on the Move (ATOM): Context-Aware Identity Validation
SAM.gov · DoW SBIR 2026 BAA
|
|
USAF Phase I | ~$300K | 2026-06-24 40 days · Pre-Release |
Solo
Top pick
|
Zephyr-ATOM = Hello-token primary auth + dual-alg JWT validator routing + SpiceDB context engine + WebTransport zero-install client. The topic's literal ask — "context-aware authentication framework operationally independent of static infrastructure" — is the production Zephyr auth subsystem almost word-for-word.
Edge Deployable prototype at proposal submission while competitors pitch architecture diagrams. Pure software, no partner. Production code from Day 1.
Full Statement of Objectives (from DSIP)ObjectiveThe objective of this Phase I effort is to design and demonstrate the feasibility of a dynamic, portable, and context-aware authentication framework prototype for secure identity and mission-authorization in austere, disconnected, or high-mobility environments. This Phase I effort will focus on defining the framework architecture, modeling identity-validation requirements for tactical environments, and demonstrating operational independence from static infrastructure. This solution should provide a foundation for robust, cross-domain access control adaptable to Air, Land, Sea, or Space transportation, aligned with the Department of the Air Force's (DAF) Zero Trust and expeditionary security strategies. DescriptionModern DAF operations are increasingly defined by mobility, expeditionary reach, and the necessity to operate in contested or infrastructure-sparse environments. Traditional authentication methods — such as Common Access Card (CAC) and Public Key Infrastructure (PKI) — were designed for stationary personnel within predictable, fixed-network environments. In multi-domain and joint logistics corridors, these legacy dependencies create operational friction, introduce significant access delays, and present systemic cyber vulnerabilities when connectivity to centralized identity providers is degraded or unavailable. To address this critical gap, the DAF seeks Project ATOM (Authentication on the Move): a secure, context-aware, and portable authentication framework capable of validating identity and mission-relevant authorization at the tactical edge. The solution must function independently of static, cloud-based infrastructure, enabling continuous, Zero Trust access control that moves with the warfighter or autonomous asset. Demonstrable capabilities may include: Context-Aware Authentication using multi-modal inputs (biometric, behavioral, situational); Disconnected Operation in DDIL environments without reliance on persistent backhaul; Cross-Domain Portability across Air, Land, Sea, and Space; Zero Trust Integration with policy-based access control adapting to real-time mission changes; Resilient Infrastructure (EMI tolerance, low-latency on limited hardware); Scalable Interoperability with existing DoW identity standards. Topic seeks decentralized identity validation supporting modernization in DAF Zero Trust Strategy and resilient multi-domain operations. Phase IEstablish technical feasibility of Project ATOM as a secure, context-aware, portable authentication framework for multi-domain tactical operations. Phase I focuses on designing the decentralized identity architecture, modeling access-control logic for high-mobility environments, and demonstrating core functionality in a controlled testbed. Key activities: Domain-specific requirements analysis for one chosen operational domain (Air/Land/Sea/Space); architecture development for secure identity containment + distributed trust logic + local authorization without persistent reach-back; feasibility modeling for DDIL performance; prototype preparation in controlled testbed; integration planning against DAF Zero Trust + edge-computing standards. Deliverables: CONOPS document; System Architecture & Design document; feasibility assessment with latency + security findings; Phase II transition plan with DoW Zero Trust integration roadmap. Phase IIAdvance ATOM to a high-fidelity, field-validated framework. Build hardened, field-ready prototype with secure identity containers and cross-domain portability protocols. Optimize for operational edge: low-latency authentication between human + machine agents in high-mobility scenarios (transport, dismounted maneuvers, orbital shifts). Demonstrate integration with mission-critical systems: autonomous transport, ISR nodes, logistics command platforms. Validate in high-mobility environments under signal disruption + hardware constraints + adversarial interference. Quantify KPIs: authentication confidence, system latency, resilience, automated failure-handling. Align with DAF Zero Trust Strategy. Deliverables: portable hardware-agnostic ATOM prototype; integration APIs/middleware; validation report with DDIL stress-test results; performance metrics dashboard; operational deployment roadmap with accreditation pathway; updated CONOPS across Air/Land/Sea/Space. Phase III / Dual-UseTransition ATOM into operational, enterprise-grade authentication and identity framework for Joint All-Domain Command and Control (JADC2), USTRANSCOM logistics corridors, and beyond. Military applications: JADC2 integration + Contested Logistics frameworks; logistics & transportation modernization for USTRANSCOM/DTS; expeditionary basing & autonomy via M2M authentication for autonomous fleets + sensor nodes. Commercial dual-use: commercial logistics & supply chain with always-on identity for intermodal transport; space mobility (satellite servicing, ground stations); emergency response and critical infrastructure. Transitions via DAF Portfolio Acquisition Executive (PAE) and cybersecurity acquisition authorities. Target TRL 6-7 entering Phase III; mature toward TRL 8-9 via operational integration, certification, field deployment. KeywordsAuthentication, Mobile Identity, Zero Trust, Warfighter Mobility, Portable Credentials, Autonomous Transport, Cybersecurity, Space Logistics, Expeditionary Logistics, AI-Agent Access Control |