Annke is not one of the five companies banned by name under NDAA Section 889, but it doesn't clear federal compliance either — the brand is widely reported to source core hardware through Dahua or Dahua-affiliated OEM/ODM manufacturing, and it publishes no country-of-origin or component documentation that would let a contracting officer verify the claim either way. For a federal or SLED buyer, that undocumented gap is the practical problem, separate from the underlying hardware question.
Below we break down the legal distinction between a named-entity ban (like Dahua's) and a covered-component risk (Annke's actual exposure), what that means if Annke units are already on-site, and which documented, sell-direct alternatives cover the same roles.
What Annke actually is, and why that matters for compliance
Annke is a consumer- and prosumer-facing camera brand sold mostly through online retail. It is not one of the five companies named directly in NDAA Section 889 — that list is Hikvision, Dahua, Huawei, ZTE, and Hytera. But being absent from that list is not the same as being cleared for federal use, and this is where a lot of buyers get tripped up.
Annke has been widely reported — by industry researchers, teardown analysts, and camera-community forums — to source core hardware from Dahua or Dahua-affiliated OEM/ODM manufacturing, a pattern common across a wide swath of budget-tier surveillance brands. Per public reporting, firmware behavior, chipset lineage, and internal component labeling on various Annke product lines have been observed to track Dahua-family designs. We frame this as "widely reported" and "per public reporting" because Annke, like most brands in this tier, does not publish an audited bill of materials or a country-of-origin attestation that would let a contracting officer verify the claim independently either way.
For a federal buyer, that absence of documentation is itself the problem — separate from whatever the underlying hardware turns out to be.
The legal distinction: named entity vs. covered component
Section 889 and its implementing rule, FAR 52.204-25, actually prohibit two different things, and conflating them is where compliance mistakes happen:
- Covered telecommunications equipment or services produced by a covered entity — Hikvision, Dahua, Huawei, ZTE, or Hytera, by name. Any product branded by or manufactured as a business unit of these five is banned outright, full stop.
- Equipment that uses covered components as a substantial or essential part — meaning a product from a brand not on the named list can still be non-compliant if it relies on a banned company's chipset, video-processing module, or other essential subsystem.
Dahua-branded cameras fall squarely in the first bucket: there is no compliant Dahua model, because the ban attaches to the manufacturer itself. Annke's exposure runs through both. To the extent a given Annke unit is actually Dahua-built hardware wearing a different label — which is what public reporting suggests — that is the rebrand problem, and a rebrand of covered hardware carries the same prohibition as the named brand. Even setting the rebrand question aside, the covered-component test still applies: the question isn't "is the word Annke on the banned list" but "what's inside this unit, and can it be proven." Without a documented answer, a contracting officer can't certify the device for an 889 self-certification or a facility security assessment — functionally the same as a ban for procurement.
Why "not on the list" isn't a green light
We see this misunderstanding constantly: a facilities manager or IT lead assumes that because Annke isn't named in the statute, it's automatically fair game. That's backwards. The named-entity list defines an absolute floor — those five brands are banned regardless of any other fact. It does not define a ceiling of everything else being approved. Everything off the list still has to clear the covered-component test, and clearing it takes paperwork: a component-level country-of-origin breakdown and a supply-chain attestation confirming the chipset and firmware don't originate with a covered entity — something an assessor or auditor can rely on.
Annke does not publish that documentation, and as a budget retail brand it is not positioned to produce it on request the way a vetted federal-channel manufacturer is. For a GSA building, a DoD installation, a VA facility, or any SLED site subject to state-level 889 adoption, that gap means the device cannot be defensibly certified — the same practical outcome as failing the test outright.
If Annke cameras are already installed
If you're doing a facility walk and find Annke units on a federal or federally funded network, treat it the same way you'd treat any unverifiable covered-component risk: as a rip-and-replace candidate, prioritized by network exposure. Cameras on a segmented, air-gapped CCTV loop with no path to a sensitive network carry lower urgency than units bridged into an enterprise network or VMS with broader access. Either way, the fix isn't a firmware update or a settings change — it's physical replacement with hardware from a manufacturer that can produce the documentation Annke can't.
What to install instead
The compliant field is wide and covers every role an Annke camera fills — outdoor bullet and turret cameras, PTZ, NVR-based systems, and video doorbells — through manufacturers like Axis, Bosch, Hanwha, i-PRO, Avigilon, Pelco, and Digital Watchdog, which maintain 889 attestations and country-of-origin documentation as a matter of course for federal sales. Uniqcli sells these lines direct — no reseller markup layers, no vehicle dependency — through the Government Purchase Card, simplified acquisition under FAR Part 13, and open-market FAR purchase orders, with WAWF/PIEE invoicing for DoD buyers.
Send us your site details and current camera inventory, and we'll put together a documented compliance assessment and a quote for the replacement gear.
