.png)
Why has your CPE become so expensive? And does it really need that much memory? Every operator negotiating a hardware order this year is asking some version of those two questions, and the honest answer starts nowhere near the router: it starts in an AI datacentre.
DRAM prices have climbed hard since 2025. Memory manufacturers have shifted production capacity toward the high-bandwidth and server memory that AI accelerators consume, and industry trackers now describe a shortage expected to run through 2026 and beyond. The chips inside a home router come off the same production lines. The twist is that routers do not even use the memory AI wants: CPEs run on older-generation DDR3 and DDR4. But when a manufacturer converts a production line to newer, higher-margin memory for datacentres, the supply of legacy DRAM shrinks and its price climbs with it. That is why a pricing story from the semiconductor market is becoming an operational story for every broadband operator that buys CPE.
Memory pressure is reaching all
Until recently, memory pressure showed up where you would expect it: in the next tender, as a higher unit price or a leaner spec. The pressure is not marginal: Counterpoint Research estimates that memory, once roughly 3% of the bill of materials for ISP routers, gateways, and set-top boxes, has grown to around 20% of it, and expects prices to keep climbing through 2026 and beyond. It has now started reaching contracts that were already signed. In one of our recent European deployments, the CPE vendor cut the hardware spec after signature: the Wi-Fi controller went from 2 GB of memory to 1 GB, and the extenders went down to 512 MB.
When that happens, everything running on the device comes under review. The operator and the vendor go line by line through what the box carries and ask what can be removed to fit the new budget. The only software that is exempt is what the device cannot work without.
What survives a hardware spec review
One thing always survives: the remote management client. An operator will not ship a router it cannot manage remotely, because without remote management there is no provisioning, no firmware updates, no diagnostics, and no way to resolve a subscriber issue short of a truck roll.
That client is not something anyone installs. TR-069, also known as CWMP, is a client–server protocol in which the device's built-in client talks to an Auto Configuration Server (ACS). TR-369, also known as USP, is its modern successor, built on a Controller–Agent architecture in which a USP Controller manages the device through its native agent. Both clients ship in the device firmware from the CPE vendor. They are part of the box, not an add-on.
Everything else is negotiable.
The problem with agent-based Wi-Fi management
A large part of the Wi-Fi management market works differently. Agent-based vendors install their own proprietary software agent on the CPE, and that agent is what delivers their analytics, steering, and optimization features. The agent occupies memory, and the footprint is not trivial: one such agent weighs in at around 140 MB, which on a 512 MB extender is over a quarter of the device's entire memory.
That footprint has to be defended on every deal. It must be written into the bill of materials, priced into the hardware, and protected through every cost-reduction round, including the ones that happen after the contract is signed. A handful of Tier-1 operators treat the CPE as a container host and give memory little thought. Most operators are not in that position. On price-driven markets, memory is one of the first things cut, and every new CPE tender is written under the same cost pressure. For any vendor whose product lives as software on the router, that is a structural problem, not a one-off.
Agentless by design
AVSystem's Hybrid CPE Management Platform takes the opposite approach: it is agentless. We install nothing on the device. The CPE reports data on a schedule and responds to standard TR-069 or TR-369 requests through the management client it already ships with. Our software runs server-side, as a TR-069 ACS and TR-369 Controller in one platform, delivered either as the Unified Management Platform on the operator's own infrastructure or as Cloud ACS, the SaaS model hosted by AVSystem.
Agentless does not mean giving up the Wi-Fi experience layer, either. The Customer Experience Management Platform (CEM) turns the device and network data the platform already collects into Wi-Fi performance analytics, root cause analysis, and proactive issue detection, with nothing added to the CPE. The Wi-Fi Experience Mobile App gives subscribers self-service diagnostics, guided troubleshooting, and parental controls from one place where there is no memory budget to defend: their own phone.
Keeping the intelligence off the device has one more consequence worth naming: the data ends up in the right place. Everything the platform collects lives server-side, in standard data models rather than a proprietary agent format, ready for whatever the operator wants to build on top of it, from OSS/BSS integrations to analytics, through northbound APIs and event streams. With Cloud ACS, that home is a cloud environment managed and maintained by AVSystem; with the Unified Management Platform, it is infrastructure the operator controls outright.
The approach is lean at the protocol level too. USP's binary encoding and modern transport layers enable up to a 10x reduction in operational bandwidth compared to verbose XML-based SOAP sessions over TR-069. And it carries proven scale: AVSystem's platform runs in production deployments exceeding 30 million active CPEs.
What this means in a spec review is simple. When the hardware budget shrinks, there is nothing of ours on the device to review, renegotiate, or remove. The management plane rides on the one process that can never be cut. When the operator cuts the hardware spec, agentless management is the only option that doesn't need renegotiation.
We would, of course, recommend choosing AVSystem regardless. But in this market, the argument rather makes itself.
One side effect of the AI expansion
Shrinking CPE memory budgets are just one side effect of the AI build-out, and this won't be the last you hear from us on the subject. We will elaborate on our approach soon. In the meantime, if you want to see what device management looks like when real engineers build it around a strong customer-facing strategy, explore the Hybrid CPE Management Platform or contact us.
FAQ
What is agentless CPE management?
Agentless CPE management controls routers and extenders through the standardized management client (TR-069 or TR-369/USP) already built into the device firmware, instead of installing additional vendor software on the device. The management logic runs server-side, so it consumes no memory on the CPE beyond the standard client.
Why are CPE memory specs shrinking?
DRAM prices have risen sharply since 2025 because memory manufacturers shifted capacity toward high-bandwidth and server memory for AI datacentres. CPE vendors and operators respond by reducing the memory in new devices, and in some cases by cutting hardware specs on contracts already signed.
Does TR-069 or TR-369 require installing software on the router?
No. The TR-069 (CWMP) client and the TR-369 (USP) agent are standard components shipped in the device firmware by the CPE vendor. A TR-069 ACS or a TR-369 Controller manages the device through these built-in components without adding software to it.
Can operators offer Wi-Fi analytics and subscriber self-service without an on-device agent?
Yes. Platforms such as AVSystem's Customer Experience Management Platform analyze the device and network data already collected over TR-069 and TR-369/USP to deliver Wi-Fi performance insights and root cause analysis, while a subscriber mobile app provides self-service diagnostics and troubleshooting from the subscriber's phone rather than the CPE.
What happens to on-device software when a hardware spec is cut?
Everything on the device is reviewed against the smaller memory budget except what the device cannot operate without, such as the remote management client. Proprietary agents installed for analytics or Wi-Fi optimization must re-justify their memory footprint, and may need to be renegotiated, reduced, or dropped.