Durability & Repair
A product that needs a server has an ending somebody else controls
When core functions depend on a manufacturer's infrastructure, the hardware's life is bounded by a commercial decision. That dependency is usually visible before purchase.

Treat the sections below as a sequence. With server dependency in hardware, getting the early decisions right makes the later ones much easier.
Before you start
- Cloud dependency creates an end-of-life outside your control.
- Local control modes are the practical mitigation.
- Support commitments are increasingly published.
Where the dependency sits
Some connected products use a server only for convenience features such as remote access and notifications, and work fully without one. Others route core functions through the manufacturer's infrastructure, so that even local commands travel to a server and back. The second arrangement is cheaper to develop and easier to update, and it makes the hardware unusable if the service stops.
Account requirements at setup are a strong clue, since a device demanding registration before basic operation is usually server-mediated. The distinction is discoverable before purchase from manuals, community documentation and the behaviour reported when the internet is unavailable.
Why services end
Companies are acquired, restructured or closed, and supporting an old product line carries ongoing cost with no revenue attached. Security obligations make old software expensive to maintain, since unpatched services become liabilities rather than assets.
Certificate expiry alone can disable a device, because a product unable to validate a connection may simply refuse to work. Subscription models shift the calculation further, since a lapsed subscription can reduce a functioning device to a limited one. None of this requires bad faith, and it happens routinely to products from well-regarded companies.
Reading a support commitment
Some manufacturers now publish a minimum support period, stating a date until which updates and services will continue. Regulation in several regions has begun to require such statements for connected products, particularly around security updates. A published end date is more useful than a vague assurance, even when the date is nearer than you would like.
The measurable part is this: check whether the commitment covers the service as well as security updates, since these are frequently separated. Where no commitment is published, the honest assumption is that support lasts as long as the product is commercially interesting.
Mitigations that actually work
Local control, whether through an open protocol, a local application programming interface or a physical control, is the single most valuable feature. Standards-based protocols allow a device to be adopted by third-party systems, which outlives any one manufacturer's application.
Open firmware communities exist for some categories and can extend a product's life considerably, though they carry their own risks. Exportable data means a service ending does not take your history with it, which matters for anything that records over years.
A physical control that works when the network is down is worth more than any number of application features.
The categories where this bites hardest
Home automation, security cameras, doorbells and thermostats are heavily affected because their value depends on remote access. Vehicles and appliances increasingly include connected features, sometimes gating basic functions behind an application. Fitness and health devices tie data to services, and the data is often the reason the device was bought at all.
In the small print, media devices lose services when licensing arrangements change, which can remove functions that existed at purchase. In each case the hardware may remain perfectly serviceable while the product stops doing what it was bought for.
Model numbers change quietly, and a review from last year may describe a different machine.
Questions to ask before buying
Ask what the device does with no internet connection, and look for a clear answer in documentation rather than in marketing copy. Ask whether an open protocol or local interface is supported, and whether third-party systems already integrate it.
The measurable part is this: ask whether the manufacturer publishes a support end date, and treat the presence of one as a mark of seriousness. Weigh the convenience of the connected feature against the possibility of losing it, and price the hardware accordingly. This site does not monitor service shutdowns, so community documentation and news of discontinued services are the sources to follow.
The takeaway
Ask what the thing does with the internet unplugged, because that is what you are actually buying.
The question is rarely which is best. It is which is enough.
Questions readers ask
What happens if the manufacturer shuts the service down?
It depends where the dependency sits. Devices with local control usually keep working with reduced features, while server-mediated devices can stop working entirely.
Is a published support end date a bad sign?
Usually the opposite. A stated date lets you price the product against a known life, which is better than an unstated commitment that ends without notice.
Also by Deepa Mohan
- Fasteners tell you what the designer expected you to openDurability & Repair
- Corrosion happens where two metals meetDurability & Repair
- Own-label goods and the factory behind the badgeWhat You Pay For
- The parts are the smallest part of what you payWhat You Pay For





