Matter alternatives

When devices from different brands must work with Apple Home, Google Home, Amazon Alexa, SmartThings and Home Assistant, Matter is the standard those ecosystems share. It defines device types and their commands, a commissioning process, multi-admin so one device can belong to several ecosystems, and a certification program recorded in the Connectivity Standards Alliance's public Distributed Compliance Ledger. Control is local over Wi-Fi, Thread or Ethernet, and the Alliance says devices keep working on the local network if the internet goes down.

Its scope is the smart home. It assumes devices and controllers share one network, and it does not define data sync between apps, identity for people or organisations, or calls between software agents. As of October 2026 the current release is Matter 1.6, from June 2026.

When battery devices need a low-power mesh that speaks IP. OpenThread, Google's open-source implementation, describes Thread as an IPv6 networking protocol for low-power devices on IEEE 802.15.4, with self-healing routing, no single point of failure, and devices that can run on batteries for years. A network supports up to 32 routers and 511 end devices per router.

Thread is a network, not an application standard, so it is usually paired with Matter. It needs a border router to reach any other network, a function many smart speakers, hubs and Wi-Fi routers include. Thread 1.4 adds credential sharing between border routers from different makers.

When a product must join existing Zigbee installations, or needs sub-GHz range. Zigbee, maintained by the Connectivity Standards Alliance, is a complete stack from the mesh network to the application language, on 2.4 GHz and sub-GHz radios, with ranges of 10 to 100 metres at 2.4 GHz and 1 km or more on sub-GHz. It works locally when the internet is down.

Zigbee 4.0, announced in November 2025, is backward compatible with Zigbee 3.0, builds in Zigbee Direct so phones can onboard and control devices over Bluetooth LE without a hub, and introduced Suzi as the brand for sub-GHz Zigbee. Zigbee reaches IP networks through hubs and gateways, and Matter only through a bridge.

For lighting and building control commissioned straight from phones and tablets. The Bluetooth SIG says Bluetooth Mesh systems need no central controller and no internet or cloud platform to install and run, and that phones interact with the mesh through proxy nodes and usually act as the provisioner. Security is mandatory: all mesh messages are encrypted and authenticated.

Mesh Protocol 1.1, summarised by the SIG in September 2023, added directed forwarding for larger networks, remote provisioning, device firmware update over the mesh, and certificate-based provisioning. Bluetooth SIG Adopter membership is free; every product must complete qualification.

For simple, low-latency control between Espressif chips, such as a battery switch controlling lights, with no router or gateway. Espressif describes ESP-NOW as a connectionless Wi-Fi protocol that sends application data in vendor-specific action frames, with payloads of 250 bytes (or 1,470 bytes for version 2.0 devices), up to 20 paired peers of which up to 17 can be encrypted, and around 200 metres in open space at full power.

It is a link-level protocol, not a network: it has no IP, no application standard and no data model, and Espressif documents it only for its own chips. The espressif/esp-now component adds multi-hop control and is licensed under Apache-2.0.

When devices on an IP network should publish readings and receive commands through a central point. MQTT, an OASIS standard since version 5.0 in March 2019, is a client-server publish and subscribe protocol over TCP/IP, with three delivery guarantees (at most once, at least once and exactly once). A broker can run locally, even on a small single-board computer.

Every client needs to reach the broker, so the broker is the system's single meeting point. Licensing differs by broker as of October 2026: Eclipse Mosquitto is EPL or EDL licensed; EMQX moved to the Business Source License 1.1 from version 5.9, free for a single production node; HiveMQ Community Edition is Apache-2.0, with commercial plans from $299 a month.

When a fleet of Linux or Windows gateways reports to AWS and needs software deployed, updated and run locally. AWS describes Greengrass as an open-source edge runtime and cloud service; it deploys components that can be processes, containers or Lambda functions, runs a local MQTT broker for nearby client devices, and has a lite edition under 15 MB of RAM.

Core devices keep running offline and spool outbound messages, but client devices need the cloud for their first connection. Greengrass bills per core device that authenticates with AWS in a month, and local client devices are free. AWS IoT Greengrass vs Azure IoT Edge compares the two runtimes in detail.

When gateways report to Azure IoT Hub and software ships as Linux containers. Microsoft describes IoT Edge as a runtime that deploys, runs and monitors containerised modules, and says IoT Edge devices and their downstream devices can work offline indefinitely after one initial sync. Messages wait for the cloud for their time to live, two hours by default.

The MIT-licensed runtime is free; you pay for IoT Hub units, from $10 to $2,500 a month as of October 2026. IoT Edge 1.6 LTS is supported until November 2028, and Microsoft now points new edge-based solutions to Azure IoT Operations.

When an app needs a local database that devices sync with each other directly. Ditto stores JSON documents as CRDTs, queries them with DQL, and syncs over Bluetooth LE, LAN, AWDL, Wi-Fi Aware and Wi-Fi, relaying across devices, with Ditto Server as an optional cloud side. It lists SDKs for Swift, Kotlin, Flutter, React Native, JavaScript, .NET, C++, Java and Rust.

In its online authentication modes each new device must reach Ditto Server once before joining the mesh. The SDK is proprietary, with a Free tier and Pro and Enterprise plans priced on request.

When the participants are apps, gateways and agents rather than certified devices, and they need to coordinate whether or not they share a network. Offline Protocol is a coordination layer for physical operations: devices discover each other over Bluetooth LE, the local network or a relay, verify each other with Ed25519 identities, and exchange MLS-encrypted messages, replicated documents and service calls, relayed across up to 8 hops. The day-to-day saving is less custom integration and fewer round trips to the cloud for work that happens side by side.

It runs on iOS and Android through React Native, in Rust, in Python on Linux, macOS and Windows gateways, in Java on the JVM, in Ruby, and from any language that calls C, with early native Swift and Android packages, a preview Flutter plugin and an experimental browser build. It is not a device standard, has no certification program, and does not control Matter devices. The mesh SDK is free under AGPL-3.0-only when the app meets its obligations; closed-source and App Store apps need the commercial license.