Inside JIATF 401: The Pentagon's New Counter-Drone Marketplace

The Pentagon is building an "app store" for counter-drone solutions. Here's what it takes to get listed—and why this matters for defense tech companies.

Counter-drone sensors deployed on a Dutch Navy vessel during NATO's Bold Machina exercise
Counter-UAS sensors mounted on a Dutch Navy FRISC during NATO's Bold Machina exercise. The system uses acoustic, EO/IR, RF, and radar sensors for drone detection. NATO photo by Deacon Westervelt, Naval Postgraduate School

The Counter-Drone Problem Has Outgrown Its Solution

If you've followed defense procurement, you know the counter-drone space has been a mess. Dozens of systems, incompatible interfaces, fragmented acquisition authorities, and warfighters left cobbling together solutions in the field. The Joint Counter-small UAS Office (JCO) tried to bring order to chaos, but the threat evolved faster than the bureaucracy could adapt.

Enter Joint Interagency Task Force 401 (JIATF 401)—the Pentagon's latest attempt to solve the counter-drone puzzle. But this isn't just a rebrand. It's a fundamentally different approach, and defense tech companies need to understand what's changing.

What Is JIATF 401?

Stood up in late 2025 under the Office of the Secretary of Defense, JIATF 401 consolidates counter-UAS efforts across the joint force. Led by Brig. Gen. Matt Ross, the task force has a singular focus that cuts through the usual Pentagon complexity:

The task force operates across three lines of effort:

  1. Homeland Defense — Protecting critical infrastructure and domestic installations
  2. Warfighter Lethality — Getting effective C-UAS to deployed forces
  3. Joint Force Training — Ensuring operators can actually use what they're given

The Marketplace Concept: An App Store for Counter-Drone

Here's where it gets interesting for defense tech companies. JIATF 401 is building an online marketplace for counter-drone systems. Think of it as a curated catalog where military units can browse, compare, and procure vetted C-UAS solutions.

This isn't just a website. It's a fundamental shift in how the Pentagon matches capability to need:

  • Pre-vetted systems — Solutions in the marketplace have already passed technical and operational evaluation
  • Interoperability certified — Systems must work within the common C2 framework
  • Streamlined procurement — Units can move faster because the heavy acquisition lifting is already done
  • Continuous updates — The marketplace evolves as threats and technologies change

For vendors, getting listed in this marketplace could be the difference between scaling across DoD or remaining a pilot program forever.

The 90-Day C2 Framework

Perhaps the most ambitious element is Ross's commitment to fielding a common command-and-control framework within 90 days. The goal: any C-UAS system in the inventory should be able to plug into a shared operational picture.

This addresses a chronic problem. Today, different C-UAS systems often can't talk to each other. Operators running multiple solutions face a patchwork of displays, interfaces, and data formats. In a contested environment, that fragmentation costs time—and time costs lives.

The common C2 framework will likely define:

  • Standard data formats for track information
  • Common APIs for system integration
  • Shared operational displays and battle management tools
  • Interoperability requirements for marketplace inclusion

Understanding the Threat: Groups 1-3 UAS

JIATF 401 is focused specifically on Groups 1-3 unmanned aerial systems—drones weighing under 55 pounds. This isn't arbitrary. It's where the current threat is concentrated.

Group Weight Typical Examples
Group 1 0-20 lbs Commercial quadcopters, FPV drones
Group 2 21-55 lbs Larger ISR platforms, modified commercial
Group 3 Up to 55 lbs (with altitude limits) Tactical reconnaissance, loitering munitions

The Red Sea and Ukraine have demonstrated what these small systems can do. The USS Eisenhower's carrier strike group expended hundreds of weapons defending against drone attacks. Ukrainian forces use $500 FPV drones to destroy million-dollar vehicles. The threat is cheap, abundant, and evolving rapidly.

What This Means for Defense Tech Companies

If you're in the C-UAS space—or adjacent to it—here's what you should be doing:

1. Prepare for Marketplace Certification

Details are still emerging, but expect a formal process to get systems listed. Start documenting your technical specifications, operational testing results, and integration capabilities now.

2. Build for Interoperability

The common C2 framework will be non-negotiable. If your system is a closed box that can't share data or accept external commands, you'll be locked out. Invest in open architectures and standard interfaces.

3. Understand the Operational Context

The three lines of effort—homeland, warfighter, training—represent different operational environments with different requirements. A solution optimized for base defense may not work for a mobile unit in contested terrain. Be clear about where your system fits.

4. Engage Early

JIATF 401 is actively shaping requirements. This is the time to provide input, not after standards are locked. Participate in industry days, respond to RFIs, and build relationships with the task force staff.

5. Think Beyond Hardware

The marketplace likely needs more than just kinetic defeat systems. Think about sensors, software, training simulators, logistics support, and data analytics. The C-UAS ecosystem is broader than the effector.

The Bigger Picture: JADC2 Integration

JIATF 401 doesn't exist in isolation. The common C2 framework will eventually need to plug into the broader Joint All-Domain Command and Control (JADC2) architecture. Counter-drone isn't a standalone mission—it's part of integrated air and missile defense, base defense, and force protection.

Companies that design with this integration in mind will have an advantage. Those building proprietary silos will find themselves marginalized as the joint force demands interoperability.

What Comes Next

Watch for these developments in early 2026:

  • C2 Framework Release — The 90-day clock is ticking. Expect initial specifications and integration requirements.
  • Marketplace Launch — The first iteration of the online catalog should go live, with initial systems listed.
  • Certification Process — Formal guidance on how to get systems evaluated and approved for the marketplace.
  • Interoperability Standards — Technical specifications for data exchange and system integration.

The Pentagon is finally getting serious about solving counter-drone at scale. For defense tech companies, this represents both opportunity and risk. Those who adapt to the new framework will find a streamlined path to fielding. Those who don't will be left behind.