— Compliance
Built for US federal procurement.
TacLink C2's hardware-agnostic architecture is designed to give US operators a path forward as the regulatory environment tightens around non-approved drone hardware. The page below is honest about where the platform is today, where it is headed, and which claims we are not making yet.
— ASDA § 848
American Security Drone Act.
The American Security Drone Act and Section 848 of the FY2020 NDAA together restrict the use of federal funds to procure or operate covered unmanned aircraft systems produced by entities subject to influence by certain foreign governments. The covered list and the specific procurement triggers are defined in statute and refined by implementing agency guidance.
For drone teams in covered agencies (and increasingly for state and local agencies that take federal funds), the practical effect is that the aircraft on the ramp must come from approved sources. The procurement constraint extends to platforms across DoD, DOJ, DHS, DOE, and a growing list of grant-funded state and local programs.
TacLink C2's position is straightforward: the software is hardware-agnostic. Operators choose the flight hardware. TacLink C2 has no dependency on, and does not require, hardware from restricted-country entities to function. Operators flying NDAA-aligned hardware (Blue UAS-listed platforms, US-built airframes on Pixhawk-class autopilots, and similar) can do so without workaround.
— Pathway
Working toward Green UAS software recognition.
To be precise: TacLink C2 is not currently AUVSI Green UAS software-listed, and the team has not yet completed the formal submission process. Stating otherwise would be misleading and we are not going to do that.
What we will say is that the architecture is being built with the recognition criteria in view: software supply chain hygiene, data handling discipline, hardware-agnostic execution, and a deployment model compatible with the constraints serious operators work under.
When we have a concrete certification roadmap with named milestones, we will publish it on this page. Until then, treat any claim of alignment as aspirational rather than certified.
— Hardware
Fly what you are allowed to fly.
Because TacLink C2 is hardware-agnostic, an NDAA-constrained operator can run the same workflow on the same software as an unconstrained operator. The difference is the airframe under it.
Categories that NDAA-aligned operators can expect to support include Pixhawk-family autopilots (Cube Orange, Cube Orange+, Pixhawk 6X and related), domestic airframes built around those autopilots, and Blue UAS-listed platforms that expose a MAVLink interface. The current tested matrix lives at /compatibility and is updated as new hardware is brought up on the bench.
For unconstrained operators, the same software runs the rest of the ecosystem, including DJI and Autel platforms where they are permitted. The compatibility matrix is honest about which path each piece of hardware sits on.
— Data
Operator-controlled data.
Flight telemetry, mission files, and logs are written to the operator's machine. There is no mandatory cloud sync, no mandatory telemetry offshoring, and no tier of the product where data control is taken away from the operator.
For agency operators with data residency or chain-of-custody obligations, this is the architecture you want: the platform does not move your data unless you explicitly choose to move it. Background on the broader handling model is on the Trust Center hub.
— Procurement
For program managers and procurement.
If you are evaluating TacLink C2 for a program, an RFI, or a pilot deployment, we want to hear from you early. The platform is pre-launch and we are actively shaping the roadmap around real procurement requirements.
The fastest path is contact. Tell us which agency, which use case, and which procurement vehicle you are working under, and we will respond directly.
— Early access