The Register reports that Cambium is urging Enterprise customers to move to on-premises cnMaestro. However, hosting the management software locally does not immediately remove every cloud dependency: Cambium’s updated customer guidance says the existing on-premises system still relies on its Cloud Anchor service for adding and deleting devices. A version without that dependency is planned, rather than established as available.
What administration means for customers
Cambium Networks Corporation’s September 14 Form 8-K records the appointment of administrators to Cambium Networks Ltd., its indirect, wholly owned UK subsidiary, that day. The administrators will attempt to sell assets and business lines; the company anticipates that remaining entities in the subsidiary’s group will be wound up through local processes.
The same filing records an immediate reduction of 260 employees on September 11, representing 53.6 percent of the global workforce, with no severance payments offered or made. These are substantial restructuring measures, rather than a routine change to a cloud subscription.
According to The Register’s account of Cambium’s company statement, production of Wi-Fi access points, NSE firewalls and cnMatrix switches has stopped. The publication also reports that Cambium anticipates its fixed-wireless broadband business largely resuming after a relatively short pause. Those product-line details rest on The Register’s reporting here; a restart remains an expectation, not a completed recovery.
For existing installations, the immediate issue is access to the management service. ARN describes cnMaestro as the portal used to deploy, manage, configure and troubleshoot Cambium Wi-Fi, switching and SD-WAN networks. Losing that service would therefore affect administrators’ ability to operate their networks centrally.
That does not establish that every deployed device will stop forwarding traffic when cloud support ends. The documented warning concerns management availability and Enterprise-device support; it is not evidence of a universal hardware shutdown. Administrators nevertheless need to assess cloud-dependent functions separately from basic connectivity.
Two dependencies complicate the on-premises route
The migration has two distinct constraints: feature licensing and the continued availability of Cloud Anchor.
The Register reports that Cambium’s proposed on-premises route includes a 90-day trial license, after which functionality will be reduced. Cambium’s FAQ, quoted by the publication, expresses an expectation that a buyer of the Enterprise business would help extend or replace the trial. That is conditional on an acquisition and subsequent action by a buyer, so customers cannot treat it as a guaranteed licensing arrangement.
Cloud Anchor presents a separate limitation. In its customer guidance updated September 18, Cambium says on-premises cnMaestro will continue to work if Anchor is disconnected or discontinued, but administrators will no longer be able to add or delete devices.
The practical implication is that an installation could remain usable for its existing managed equipment while losing the ability to accommodate replacements or inventory changes through those operations. Moving the application to a local server therefore needs to be evaluated alongside the external services it still requires.
Cambium says it plans to release an on-premises image before Cloud Anchor shuts down that removes the Anchor dependency. The announced scope is Wi-Fi and switches only, and the company says this image will include all supported on-premises X features without requiring licenses.
That plan could address both concerns for supported installations, but it should not be confused with the currently described migration arrangement. The announcement does not establish that the image has shipped, and its stated scope does not promise an equivalent escape path for every Cambium product.
What administrators should prioritize
With October 1 approaching, the useful response is a continuity assessment followed by a controlled migration—not an assumption that every device can be moved identically.
The following are planning priorities, rather than a verified click-by-click migration procedure:
- Identify which sites and devices depend on cnMaestro Cloud, and which functions staff currently perform through it. Separate Wi-Fi and switching installations from other product categories because the planned Anchor-independent image explicitly covers only Wi-Fi and switches.
- Preserve available configuration records, device inventory and subscription information while cloud access remains available. These records provide a baseline for assessing what a replacement management setup must retain.
- Evaluate the available on-premises option against the functions each installation needs. Include the trial’s eventual feature reduction and the inability to add or delete devices if Anchor disappears.
- Validate a limited deployment before committing an entire estate. The relevant acceptance criteria are whether equipment can be managed and required workflows remain available, rather than simply whether the local management application starts.
- Track delivery of the promised Anchor-independent image separately from any proposed business sale. A planned software release and a possible buyer’s licensing assistance are different dependencies, neither of which should be assumed complete.
Exact migration commands, supported device versions and recovery procedures are not established by the available primary-source excerpts. A universal sequence for deleting devices from cloud management and re-enrolling them locally would therefore be unsafe to prescribe.
For Cambium customers, October 1 is best treated as a service-continuity risk deadline. The immediate objective is to retain control of supported equipment while cloud management remains accessible, with a clear understanding of which licensing and cloud dependencies will survive the first move on premises.