The cloud becomes the default

The shift that happened quietly

Consumer networking hardware had shipped with web interfaces since the late 1990s — a router's admin panel lived at 192.168.1.1, not on a server in Oregon. The assumption was local. What changed in the early 2010s was not the technology so much as the business logic: a permanent connection to vendor infrastructure stopped being a feature and became the architecture. Cloud authentication, cloud-side logic, cloud storage of your own device data. The shift was gradual enough that most buyers did not notice it happening.

The enabling conditions arrived together. Broadband penetration in wealthy markets crossed thresholds that made a persistent outbound connection reliable enough to build on. Mobile operating systems, specifically iOS from 2007 and Android from 2008, trained consumers to expect that apps controlled things, and apps needed backends. Elastic cloud infrastructure — AWS launched its core compute service in 2006 — made running those backends cheap at any scale. The result was that by roughly 2012, a connected thermostat, camera, or hub that operated entirely on the local network looked like an engineering compromise rather than a design choice.

Nest's Learning Thermostat, launched in 2011, illustrated the direction cleanly. The device was genuinely useful and physically well-made, but its remote-access and software update paths routed through Nest's servers. That was not a secret, but it was not the headline either. The headline was the algorithm. The cloud dependency was infrastructure, invisible until it wasn't.

Argued for, not assumed

Zigbee and Z-Wave devices from the same period continued to function across hub generations because the radio layer was standardised and the device logic was local.

The Revolv hub, a multi-radio smart-home hub, shows what the commercial logic produced when taken to its endpoint. Google acquired Nest in 2014, Nest acquired Revolv shortly after, and in 2016 the Revolv service was shut down. The hardware — sold at around $300 — became inoperable. No local fallback existed because none had been designed in. The device authenticated against a server; when the server stopped answering, the device stopped working. This was not a malfunction. It was the architecture functioning as intended, just past the vendor's intended service window.

The contrast with open radio protocols is sharp. Zigbee and Z-Wave devices from the same period continued to function across hub generations because the radio layer was standardised and the device logic was local. A Zigbee sensor paired in 2013 could be re-paired to a different hub in 2023 without any involvement from the original manufacturer. The protocol outlived the product ecosystem, which is precisely what a protocol is supposed to do.

By the mid-2010s, choosing local control required affirmative effort: selecting hardware with documented local APIs, running self-hosted software like Home Assistant, and accepting that vendor support channels would treat these configurations as unsupported. The default had inverted. Cloud-first was not just the path of least resistance; it was frequently the only documented path.

The Connectivity Standards Alliance ↗ — formerly the Zigbee Alliance — and its Matter specification are a direct response to this, an industry attempt to establish an application layer that keeps some control local by design. Whether Matter shifts the default or simply adds a local option alongside the cloud path remains an open question. Early implementations still require cloud accounts for setup, which suggests the commercial incentive to retain the server relationship remains strong.

Tethered devices carry a cost that rarely appears in the purchase price: residual value ↗ collapses when the service ends, and service windows for consumer electronics are measured in years, not decades. The buyer of a $300 hub in 2013 owned the hardware. The buyer of the same hub in 2016 owned a disk with circuit boards inside it. The cloud was the default. The cloud was also the liability, and the two facts arrived in the same box.