The "Central" architecture is also the bottleneck.
HikCentral genuinely is a central VMS - that is the design. The problem is what "central" implies in 2026: a Windows server somebody has to host, every remote site funnelling back to it, and a licensing model from the perpetual-license era. Each item on its own is manageable. Together, they are why integrators look at cloud-native.
A Windows server to own and operate
HCP runs on Windows Server (2012/2016/2019/2022). The customer hosts it (or buys the Hikvision-branded Dell appliance for ~$18,933 AUD at 64ch). You patch, back up, restore and rescue it. That work compounds with every additional customer or site you add.
Remote sites need VPN or port-forward
Cameras and NVRs at each site connect back to the central server. In practice that means a VPN per site or port-forwarding through the customer's router. Network changes break everything. Integrators consistently report customers switching to cloud after IT mandated a "no open port" policy following ransomware incidents.
Perpetual per-channel + add-on modules + SMA renewal
Each channel is a perpetual licence (HIKCENTRAL-P-VSS-1CH) tied to the server install, plus separate modules for access, ANPR, facial, alarm, FocSign, AcuSeek, plus the SMA / maintenance renewal that keeps the platform getting updates and security patches. The "buy once" sticker is just the first line - stranded SKUs when sites churn, module surprises when scope grows, and the SMA cycle quietly rebuilds a subscription on top.
Cybersecurity track record
Multiple HikCentral Pro CVEs published over the last few years (see NVD search). The HCP server is typically exposed to the network for remote access - ransomware risk is the reason integrators give for moving to cloud.
NDAA Section 889 + country bans
US federal and federal-funded sites must remove Hikvision kit and the surrounding management software. Canada's federal ban became official in 2025. UK, Australia, Netherlands and Taiwan have added their own restrictions. HikCentral Connect inherits the same camera exposure.
Hikvision-camera-first
Auto-discovery, firmware management, AcuSense/ColorVu and AcuSeek surface natively for Hikvision devices only. Third-party cameras work via ONVIF but are second-class. Customers running multi-brand fleets end up with two consoles.
Same multi-site goal. Different decade.
Both products give an operator one view across many sites. The difference is the engine underneath: a central Windows server everyone connects back to, versus a cloud platform every site connects to directly.
REAL-WORLD EXAMPLE
Pharmacy chain, 80 stores: HikCentral vs TetherX
HikCentral: 80 stores each running their own Hikvision NVRs, all connecting back to a single HCP server at HQ. Per-channel perpetual licences for ~800 cameras. Windows Server patched on Patch Tuesday by HQ IT. VPN tunnels from every store to the central server. When the HQ server has an outage, all 80 stores lose management at once.
TetherX: 80 stores each connect directly to TetherX cloud. No server at HQ, no VPN tunnels, no per-channel perpetual licences. The integrator gets ~800 cameras of RMR. Add a store next month - the integrator activates the new TetherBox, adds the channels to the platform subscription, done. Drop a store - the subscription stops.
Migrate the platform first. Phase the cameras when the budget says so.
You do not need to rip out cameras on day one. The TetherX migration is sequenced so the integrator captures the recurring revenue immediately while the customer keeps using the hardware they already paid for.
Add TetherX over existing cameras
Install a TetherBox at each site (TetherBox software on an existing server or PC, or a dedicated unit - vehicle-size through to rackmount) and connect the existing Hikvision cameras to it on the site network. The TetherBox is the only thing that talks to the cloud, the cameras themselves have no direct Internet access. No re-cabling, no re-mounting, no downtime for the customer.
Decommission the Windows server
Once cameras are live in TetherX, decommission the HikCentral server. Customer reclaims a UPS slot, an IT licence and one more thing-that-can-fail.
Phase camera swaps over 12-36 months
When NDAA, end-of-life or warranty triggers a camera swap, replace with Hanwha / Axis / Avigilon. TetherX never noticed the difference; the customer never noticed the migration.
Questions integrators ask before they switch
See TetherX against another VMS
Researching options? Read the side-by-side for each VMS the channel asks about most.
Still have questions about migrating off HikCentral, licensing, supported cameras or NDAA?
Read the full FAQTry TetherX free for 30 days
Run it next to your existing HikCentral install. If TetherX does not pay back in saved site visits within the trial, walk away. No card, no commitment, extensions on request.
Start Free TrialAbout this comparison. Information about other vendors is drawn from their public product pages, datasheets, integrator forums (Reddit, vendor user groups), public CVE databases (NVD, CISA) and customer conversations - accurate to the best of our knowledge as of 21 May 2026. Pricing, features, security posture and policies change. A vendor may have shipped a fix, dropped a price, added a region or changed an architecture since this page was last reviewed.
If you believe anything here is inaccurate or out of date, please contact us and we will review and correct it. Trademarks and product names belong to their respective owners and are referenced here for identification only.