Most telecare systems on the market today are built around a specific manufacturer’s hardware. You buy their pendants, their sensors, their base units — and, crucially, their software to manage it all. It works fine, until you need to add a device that manufacturer doesn’t make, switch to a cheaper supplier, or connect your telecare system to something else entirely, like a housing management platform or a hospital’s remote monitoring tools. 

That’s when the lock-in becomes obvious. Because the whole system was built device-first, swapping any part of it means ripping out and replacing the lot. You’re not just buying hardware — you’re committing to one company’s roadmap, one company’s pricing, and one company’s pace of innovation, indefinitely. 

This is the model Amparo’s solutions are built on. Rather than manufacturing our own proprietary hardware and locking customers into it, our platform is designed to work with devices from any manufacturer, connected through open, standards-based protocols — including BS 8684, the UK’s new Technology Enabled Care (TEC) standard introduced in January 2025. If a device speaks a recognised protocol, it can join the platform.

For local authorities, alarm receiving centres, and care providers facing the UK’s analogue switch-off — which completes in January 2027 — this distinction isn’t academic. It’s the difference between a genuine long-term upgrade and a short-term fix that locks you into the same problem a few years from now. 

Three things are worth thinking through as you evaluate options: 

•  You keep control of your own roadmap. With a protocol-based platform, you’re never stuck waiting for one manufacturer to release a device you need, or paying whatever they decide to charge because you have no alternative. You can add, swap, or mix devices as your needs change or as better technology comes to market. 
• Interoperability stops being a project. Care technology increasingly needs to connect across services — telecare, housing, healthcare, building management. A platform built on open protocols is designed for this from the outset, rather than requiring costly integration work every time you want two systems to talk to each other. 
• Standards compliance is built in, not bolted on. Following an open standard like BS 8684 isn’t just good practice; it’s increasingly what commissioners and regulators expect. A platform that’s aligned with the standard from the ground up gives you a stronger footing for procurement and audit than one that’s been retrofitted to comply.