AI Video Surveillance for Defense in the United States
VMukti delivers NDAA Section 889 safe AI video surveillance and ICCC platforms for U.S. federal defence installations, DoD contractors, and federally-funded defence integrators. The platform ships with software-bill-of-materials attestation, FAR 52.204-25 representation, AWS GovCloud / Azure Government landing-zone runbooks, DoD IL4 / IL5 deployment guidance, and a camera onboarding policy that refuses prohibited brands at the firmware-signature level. Visual Bot autonomous agents handle base perimeter intrusion, vehicle-borne IED indicators, and PPE on the flight line; ArcisGPT supports investigative search across base-wide camera estates with role-segregated access and a tamper-evident audit log. Used by federal integrators serving Army, Navy, Air Force, Marine Corps, and Space Force programs of record.
- NDAA Section 889 safe with SBOM
- FAR 52.204-25 attestation flow
- DoD IL4 / IL5 deployment guidance
- PIV / CAC identity federation
- AWS GovCloud / Azure Government
- STQC / ISO 27001 audited core
Built for procurement teams at
- Federal defence integrators
- DoD program offices (Army, Navy, Air Force, USMC, USSF)
- Defence Logistics Agency procurement
- Service component commands
- Defence-aligned critical-infrastructure operators
Use cases — Defense in United States
Base perimeter and gate control
Edge AI tripwire, ANPR, and vehicle classification at gates. Watchlists sync from DoD law-enforcement systems; alerts integrate with the base defence operations centre dispatch workflow.
Flight line and ramp safety
PPE detection, foreign-object debris, and unauthorised-vehicle ingress on flight lines and ramps. Edge inference at the recording site keeps the alert path live during WAN-isolation drills.
Insider-threat investigation
ArcisGPT runs natural-language queries across the base camera estate with role-segregated access and immutable audit log. Replaces hour-of-tape review with seconds-of-query for investigative leads.
Logistics and ammunition handling
Computer-vision audit of magazine-area access, two-person rule enforcement, and chain-of-custody for sensitive shipments. Audit log exportable to DoD inspector-general workflows.
Customer references
Published case studies are limited because most Defense deployments in United States run under non-disclosure. Procurement teams can request RFP-ready reference packs covering the deployments listed below.
- Federal civilian agency — NDAA-safe perimeter modernisation across 6 sites (under NDA).
- Defence-aligned critical-infrastructure operator — flight-line PPE + ANPR rollout.
Read next
United States compliance FAQs
How does VMukti prove NDAA Section 889 compliance?
VMukti provides three artefacts buyers can include in a 889 procurement file: (1) a signed vendor attestation that the VMukti platform contains no software, firmware, or services from prohibited entities (Hikvision, Dahua, Hytera, Huawei, ZTE) or their subsidiaries; (2) a software bill of materials (SBOM) for the cloud control plane and on-premise components; (3) a camera-compatibility matrix flagged for 889 status so the customer can see exactly which OEMs are admissible. Attestation is refreshed at each contract renewal and on material platform changes.
Does VMukti work on AWS GovCloud?
Yes. VMukti deploys into AWS GovCloud (US-East and US-West) and Azure Government for customers whose workloads must run inside FedRAMP / DoD-aligned cloud boundaries. The same software image runs in commercial and government cloud regions; the difference is the cloud provider account, IAM federation, and the operational support model. For DoD IL4 / IL5 use cases the deployment topology is reviewed with the customer's AO.
Is VMukti on the GSA schedule?
VMukti is currently sold into US federal and federally-funded projects through certified system-integrator partners with GSA Schedule 70 and SEWP V vehicles. Direct GSA listing is on the FY2026 roadmap; in the interim, government customers procure via integrator partners with appropriate set-aside vehicles. Contact our US team for the current partner list.
Can existing prohibited cameras be re-used after switching to a 889-safe VMS?
No. NDAA Section 889 prohibits not only the procurement of covered equipment but also its use as a substantial or essential component of a federally-funded system. A 889-safe deployment requires removing or replacing prohibited cameras (Hikvision, Dahua, Huawei, Hytera, ZTE, and their OEM rebrands) from the surveillance network — switching VMS alone does not achieve compliance. VMukti supports a phased migration where prohibited cameras are quarantined on an isolated VLAN, recorded for legal-hold purposes, and progressively swapped for vetted brands.
Which cameras does VMukti onboard in 889-safe mode?
The 889-safe deployment mode restricts onboarding to vetted brands: Axis Communications, Hanwha Vision, Bosch Security, i-PRO, Sony, Pelco, Mobotix, Honeywell, Motorola Avigilon, FLIR / Teledyne, and approved domestic US manufacturers. The VMS rejects onboarding attempts from MAC OUIs and firmware signatures tied to prohibited OEMs, even when the device claims ONVIF compatibility. Customers can request whitelist additions for any non-prohibited OEM not in the default list.
What documentation does a federal or state buyer need to defend a 889-safe purchase?
Procurement files typically need: (1) signed FAR 52.204-25 representation from the prime vendor; (2) software bill of materials covering the VMS and bundled components; (3) the camera compatibility matrix with 889 status; (4) a description of network segmentation between the surveillance VLAN and any covered equipment that remains for legitimate non-prohibited purposes; (5) the contract clause flowing the 889 obligation down to integrator and managed-service subcontractors. VMukti supplies (1)-(3) on request and assists integrator partners with (4)-(5).
Ready to evaluate VMukti for Defense in United States?
Speak to a procurement specialist who has shipped this exact industry × country combination. RFP responses returned within 5 business days; demo environments stood up in 48 hours.