What we heard
Neighboring units lacked a shared drone picture.
One commander described disconnected feeds. His drones could see only others from the same maker, and sharing positions took manual steps.
Cross-platform orchestration for unmanned systems
Orchestration across domains
Uncrewed aircraft, ground units, and vessels often cannot see each other, and neighboring units do not share one picture. We are a pre-seed team finding out where a shared layer helps, and where existing tools already do the job.
The model
Five related coordination layers. Different operators, different requirements. We start with the first two.
Where we start
A candidate first step, pending further customer validation. Air and ground come first. Existing tools remain the interface.
01 · Possible input
02 · Our hypothesis
03 · Possible output
Subject to access, interface, and approval.
If validated, we test three things
Demo coming soon
Customer discovery
Before building anything, we held 50 structured conversations with people who operate, command, and buy military uncrewed systems. We asked how the work gets done today, not whether they liked our idea.
Every conversation was unclassified and unattributed.
What we heard
One commander described disconnected feeds. His drones could see only others from the same maker, and sharing positions took manual steps.
The counterexample
A former operator told us his team felt far less pain seeing and deconflicting. Connecting systems was still friction.
So the question changed: where do existing tools still fall short? We have not yet validated the burden of tasking mixed fleets.
Who we need to hear from
You fly or command mixed fleets today. Tell us what you still work around by hand.
You own the systems and the data. Tell us where a bridge is welcome, and where it is not.
You know who funds a fix. Tell us what a credible path looks like.
Team
Engineering capability, operator insight, and firsthand defense software procurement.

Engineering
Aerospace PhD. Flight simulation and controls.
SBIR and STTR experience.

Operations
Retired U.S. Army AH-64 Apache pilot.
Mission planning and airspace coordination.
Operations

Acquisition
Procured Army software.
Managed more than 3,500 software licenses.
The public record
Public solicitations, standards, and unit lessons that describe the coordination problem. We cite them as context. None is a customer, a sponsor, or an endorsement.
DIU asked industry for the automated coordination of hundreds or thousands of uncrewed assets across multiple domains, and for more resilient command and control.
An open Army call for controllers that work across small drones, launched effects, and ground robots inside its command-and-control network. Notice W58RGZ-26-S-C001-0009.
The Army asked industry for tools to manage airspace crowded with drones, crewed aircraft, and loitering munitions, including real-time deconfliction.
The Army is buying commercial command-and-control applications on an open architecture, and says its call for new ones continues.
The Army’s uncrewed aircraft office publishes interface standards so systems can interoperate. More than 100 organizations take part in the working group.
The Army asks drone vendors how they will adopt its common vehicle-control software, as a foundation for interoperability.
A brigade describes deconflicting thousands of small drones with crewed helicopters in low-altitude airspace.
The Army’s lessons-learned center says each maneuver brigade will soon employ hundreds of drones, and that crewed, uncrewed, and fired systems must be integrated.
Units that fielded new drones reported airspace management as a near-universal concern.
GAO found the military services pursuing command-and-control projects largely in isolation. Report GAO-25-106454.
Every source above was opened and checked on 10 Nov 2026. Links open in a new tab.
The ask
Does Connect + See fill a persistent gap that existing platforms will not close?
Operators, integration owners, requirements leaders, and acquisition offices.
brianarevalo@berkeley.eduOne urgent mission → one accountable buyer → one test worth running