HomeHidden OpportunitiesThe CBP Drone as First Responder RFI Is Due Dec. 18: Five-Minute...

The CBP Drone as First Responder RFI Is Due Dec. 18: Five-Minute Launch, FedRAMP Hosting, Vendor-Paid Demos, and No Identified Dock Funding

The RFI sets threshold and objective values for launch time, endurance, and range, then asks about cloud hosting and supply chain. Responses are due Dec. 18, and vendors who demonstrate pay their own way.

The CBP Drone as First Responder RFI Is a Requirements Signal With a Dec. 18 Deadline

The CBP drone as first responder RFI asks industry for small drones paired with automated docks that launch when a sensor alarm trips. U.S. Border Patrol posted it on Nov. 6, and responses are due Dec. 18 at 5:00 p.m. Eastern. If you are a BD lead or capture lead at a small business, a mid-market firm, or a new entrant that sells or integrates dock-and-drone systems, AI detection software, or fleet management, a response is the public route to putting your numbers in front of the buyer before it writes a requirement. This is currently a requirements signal, not yet a validated federal contracting opportunity: the notice says CBP “DOES NOT INTEND TO AWARD A CONTRACT ON THE BASIS OF THIS RFI.” I rate it SHAPE, not PURSUE. Respond to inform the requirement, and do not plan revenue around it.

The RFI describes a “prepositioned integrated unmanned aircraft capability designed to autonomously or remotely deploy drones in response to security threats or operational requirements.” That capability is called drone as first responder, or DFR. Border Patrol wants it to report the location and movement of people, vehicles, and contraband between ports of entry.

Field Answer
Signal Market-research RFI for paired small-drone and dock systems and services
BD implication A response helps shape thresholds and pricing questions, and no award is planned from it
Customer U.S. Border Patrol, part of CBP
Buyer Border Patrol, which is “conducting market research”; no contracting office is named
Funding Not identified for docks; the FY2027 request carries a small-drone line, and its Mobile Systems cost driver anticipates no change; the House committee recommends $10M for small-drone acquisition, with report language favoring portable systems (committee recommendation, not enacted)
Vehicle / path Not identified; the RFI mentions only a possible future solicitation
Incumbents / ecosystem None named; the RFI names no incumbent or predecessor contract
Access strategy Prime or team; the vendor form asks about OEM versus reseller status
Timing Answers to vendor questions about Nov. 20; responses Dec. 18; demos possible after review
Confidence High on the notice’s contents; Moderate on funding and field; Low on any future buy
Pursuit posture SHAPE
Upgrade triggers A set-aside, vehicle, or code added in the answers; a demo invitation; a draft solicitation; a funded DFR line
Downgrade triggers The notice archives with no follow-on; CBP folds DFR into a portable-drone buy

The notice sets this sequence:

  1. Vendor questions closed Nov. 13.
  2. CBP posts answers on or about Nov. 20.
  3. Responses are due Dec. 18.
  4. CBP may invite selected vendors to demonstrate, arranged by separate correspondence.
  5. Any solicitation would come later and has no date.

What the CBP Drone as First Responder RFI Asks For

The RFI sets a five-minute launch threshold with a three-minute objective, 30 to 60 minutes of flight, and 1 to 5 miles of control range, and asks vendors to say whether each system meets them. A threshold is the minimum acceptable value, and an objective is the target value.

Item Threshold Objective
Launch after an alert 5 minutes 3 minutes
Flight time 30 minutes 60 minutes
Control range 1 mile 5 miles
License plate read distance 100 yards 200 yards
Human detection by thermal camera 1/4 mile 1/2 mile

On the camera, CBP asks whether it offers at least 4K video and 30x optical zoom. The questions also cover wind up to 15 meters per second, temperatures from minus 20 to plus 50 degrees Celsius, and dust and rain ratings.

The launch trigger can be a tower alarm, another sensor, a software interface call, or a manual command. In the RFI’s concept, the drone sends video and location data to field agents, then returns to the dock to recharge. CBP also asks whether fleet software can manage several remote sites from one screen and support aircraft from more than one manufacturer.

CBP lists four systems as integration examples: TAK, Lattice, Trails, and ICAD. The technical request asks which of them each product connects to, so a vendor should address all four.

The Cloud and Supply Chain Questions Test Readiness Beyond Flight Performance

The RFI asks whether the software can be hosted in the CBP cloud or an equivalent FedRAMP-authorized government cloud, with FedRAMP Moderate or High as the threshold. It does not say these questions will become pass-or-fail evaluation criteria in a later solicitation. Answer each one honestly.

  • Cloud hosting: whether the software platform, ground control application, and data backend can run in the CBP cloud or an equivalent government cloud.
  • Encryption and controls: FIPS 140-2 or 140-3 validation and NIST SP 800-53 controls, including secure boot and tamper detection.
  • Component origin: compliance with the National Defense Authorization Act ban on covered foreign components, with the origin of flight controllers, gimbals, radios, and batteries.
  • Blue UAS listing: whether the aircraft is on the Defense Department’s Blue UAS Cleared List.
  • Supplier eligibility: whether suppliers are domestic or from a Trade Agreements Act country.
  • Past performance: up to three contracts or projects from the past five years in DFR, automated drone, or remote-operations work for federal, state, or local agencies.
Five minutes: the launch threshold in the RFI, with a three-minute objective. Both are requested values from market research, not program commitments.

A small firm with a strong aircraft and no cloud authorization has a gap that a better camera does not close. A software firm with FedRAMP authorization and no hardware has the opposite gap. Those two firms can team.

Two of these items sit on top of rules that already apply. Federal law limits agency purchases of covered foreign drones under the American Security Drone Act, part of the FY2024 National Defense Authorization Act, and the FY2023 National Defense Authorization Act codified FedRAMP authorization for agency cloud services. The RFI’s NDAA and FedRAMP questions track those rules. Blue UAS listing and the performance thresholds are CBP’s own asks.

CBP may invite selected vendors to demonstrate launch, low-light video, lost-link behavior, rural performance, cybersecurity documentation, and sustainment. The RFI puts the cost on the vendor: demonstrations are “at no cost to the Government,” the vendor supplies all equipment, and participation earns no special consideration in a later acquisition.

No Dock Funding Is Identified, and the Budget Language Points Elsewhere

CBP’s FY2027 budget request includes a $3.0 million increase for its unmanned aircraft program. The justification ties that increase to CBP’s nine MQ-9 aircraft, which Air and Marine Operations flies, not to small drones. Border Patrol is a separate mission owner and budget line from that MQ-9 work. The request lists small drones as their own budget line and, in its Mobile Systems cost driver, anticipates no change for FY2027. No line names docks.

The House Appropriations Committee recommends $10,000,000 for small drone acquisition, in a committee report and not in an appropriation, so the final FY2027 amount may differ. Its report asks CBP to prioritize systems “carried by a single agent” and launched “without additional support personnel or dedicated launch equipment.” That language describes a portable drone. A dock-based system is fixed, powered, and sited, and I would not read the committee’s money as support for docks.

“Vendor demonstrations of products or services shall be rendered at no cost to the Government.” (CBP request for information notice, Nov. 6, 2026)

An RFI response costs staff time with no revenue line behind it. If CBP funds small drones in FY2027, the House language points toward portable systems, and a dock vendor would need to show why docks belong in the same budget line.

No DHS contract award since FY2020 describes its work with the phrases “drone as a first responder” or “drone dock.” That fits an RFI-stage requirement. It does not rule out dock hardware bought inside earlier small-drone orders, which carry generic descriptions.

Competitive Landscape: Three Vendor Types and No Named Field

CBP names no expected respondents, and the RFI’s own structure sorts them into three types.

  • Dock and aircraft makers: the vendor form asks whether the firm is the original manufacturer or a reseller, and requests technology and manufacturing readiness levels. Some of these firms already market DFR to police and fire agencies.
  • AI product firms and fleet software firms: the questions on target classification, false alarm rates, and multi-site management ask about AI models and cloud authorization.
  • Systems integrators: the tower-alarm, TAK, Lattice, Trails, and ICAD connections need someone to wire them, host the data, and support mixed-manufacturer fleets.

The RFI also asks about pricing if “a contract is available for all of DHS” and for “all Federal Agencies with related trade and law enforcement missions.” That wording suggests CBP is considering a broad vehicle. It is an inference from the questions, not a stated plan, and tiered pricing questions are also routine in market research.

What to Do Before Dec. 18

Border Patrol asks for three forms and a rough order of magnitude price split into dock, aircraft, and services. Each vendor type has a different first step.

  • Dock and drone makers: decide by Dec. 4, two weeks before the deadline, whether you can answer the component-origin and Blue UAS questions truthfully, then complete the vendor data form, the technical request, and one summary page per system.
  • AI product firms and fleet software firms: state your FedRAMP authorization level first, then your hosting approach, and find a hardware partner whose aircraft answer the component-origin question cleanly.
  • Integrators: answer the tower-alarm, TAK, Lattice, Trails, and ICAD questions and offer to host mixed-manufacturer fleets.
  • Commercial-first entrants selling DFR to police and fire agencies: pull your three strongest past-performance references and check them against the five-year window.
  • Confirm your federal contractor registration is active and your unique entity ID and CAGE code are ready for the vendor data form.
  • Mark your business size and socioeconomic status on the form. The RFI states no set-aside, and CBP asks for the information anyway.
  • Gather your NDAA component origin list for flight controllers, gimbals, radios, and batteries.
  • Write down your FedRAMP authorization level or the path and date to reach it.
  • Draft rough order of magnitude prices for the dock, the aircraft, and services, and decide whether to give quantity discounts.
Border Patrol wants your numbers by Dec. 18. Respond if your system is fielded and your component-origin, Blue UAS, and FedRAMP answers are favorable. Team if one or two of them are missing. Watch if none are favorable.

I would revisit the posture after CBP’s Nov. 20 answers or a demo invitation. If the notice archives on Jan. 2, 2027 with no follow-on, or CBP folds docks into a portable-drone buy, the priority drops.

FAQ

Is the CBP drone as first responder RFI a contract opportunity?

Not yet. It is market research, and the notice states that CBP does not intend to award a contract from it. It becomes an opportunity only if a funded solicitation follows.

Who owns the budget for drone docks at Border Patrol?

Border Patrol sponsors the RFI, and no dock budget owner is named. CBP’s request carries a small-drone program line and a separate drone-countermeasure line, and neither names docks. Air and Marine Operations, which flies the MQ-9s, is a different environment from Border Patrol.

Can a small business respond if it is not an original manufacturer?

Yes. The vendor form asks whether the firm is the original manufacturer or a reseller. The RFI does not restrict respondents by size or status and asks each firm to report them. The notice lists no NAICS code, so no size standard applies yet.

Do I need FedRAMP authorization to respond?

No. The RFI asks for your authorization level and sets FedRAMP Moderate or High as its hosting threshold, and it does not condition a response on it. A hardware maker can name its software partner and that partner’s authorization, or state its own path and timeline.

What happens after the Dec. 18 deadline?

CBP may invite selected vendors to demonstrate at their own cost, and demonstration carries no special consideration in a later award. Any solicitation would be posted separately and has no date.

What would move this from shaping to pursuit?

Any of these would: a set-aside, vehicle, or classification code in CBP’s answers, a demo invitation, a draft solicitation, or an appropriation that names docks.

The Contract Opportunity Atlas

Two issues a week.. Free.

Two issues a week. Data-driven intelligence for small tech firms selling to the federal government. Free.

Subscribe to Contract Opportunity Atlas

Get federal technology, AI, procurement, and GovCon insights delivered to your inbox.

Shahid Shah
Shahid Shah
Shahid specializes in bringing world-class CTO, CISO, and EiR expertise to startups, business units and companies on a part-time (fractional) basis. With a rich background in regulated, safety-critical industries like Med Devices, Digital Health, and Gov 2.0, he possess a unique understanding of complex, high-demand products and services. He is a C-suite native that can easily blend in with technical and engineering teams that need to deliver revenue-generating solutions to the marketplace. He has served as an Entrepreneur in Residence when a market seems lucrative but it's unclear how to build and launch products and services for such opportunities. Shahid has years of leadership experience as a co-founding startup CTO for multiple venture-backed companies, business unit CTO and EiR, and public company CTO helping transform product teams from marginal to high performance. His software/hardware engineering and cybersecurity body of knowledge is up to date because he rolls up his sleeves to create code when appropriate & dive into system architecture and design when required. He also conduct technology due diligence exercises for corporate acquisition or product integration requirements.
RELATED ARTICLES

Most Popular

CATEGORIES