Offline Protocol vs Matter
Matter and Offline Protocol both keep work local, for different participants. Matter, from the Connectivity Standards Alliance, is the standard that lets certified devices from different brands, such as lights, locks, thermostats and EV chargers, work with Apple Home, Google Home, Alexa and SmartThings over one home network. Offline Protocol is the coordination layer for physical operations: the apps, gateways and agents at a site discover each other, verify identity, share data and call nearby capabilities directly, which means less custom integration, fewer round trips to the cloud and fewer manual handoffs. In short, Matter standardises how a controller talks to a certified device; Offline Protocol coordinates the people, apps and machines working around those devices.
Covers itPartly, or with conditionsNot part of it Matter leads on the first four rows, Offline Protocol on the last four. Taken from each one's own documentation; the table below carries the specifics.
TL;DR
Matter and Offline Protocol are rarely a straight choice, because they standardise different things.
- Choose Matter when you make or buy devices, such as lights, locks, sensors, appliances or EV chargers, that should work with any major smart home ecosystem, certified and controlled locally.
- Choose Offline Protocol when phones, tablets, gateways and software agents at a site must find each other, verify identity, share working data and call each other's capabilities, including across organisations and with no shared network.
- Use both when a site has certified devices and people working around them: a Matter controller for the devices, Offline Protocol for the coordination.
- Matter wins on device interoperability, certification and ecosystem support. It does not define coordination between apps, data sync, identity for people or organisations, or calls between agents.
In short, use Matter to make devices interoperable and Offline Protocol to make the work around them flow locally.
What does each one standardise?
| Question | Matter | Offline Protocol |
|---|---|---|
| What it is | An application-layer standard that lets certified smart home devices from different brands work together | An SDK and coordination layer for physical operations: discovery, identity, edge sync, encrypted messaging and nearby service calls |
| Who builds with it | Device makers, chip vendors and smart home platforms | Product and platform teams building apps, gateways and agents for sites, fleets and field work |
| Governance | A working group of the Connectivity Standards Alliance, which had more than 900 members in June 2026 | Offline Protocol; open-source SDK |
| Current release (October 2026) | Matter 1.6 (June 2026); open-source SDK v1.6.1.0 | SDK v0.31.0 |
| Networks | Wi-Fi, Thread and Ethernet; Bluetooth LE, Wi-Fi or NFC to set devices up | Bluetooth LE, the local network, Wi-Fi Direct on Android, an internet relay, Reticulum and Nostr, with automatic failover |
| What it needs on site | Devices and controller on one IP network; a controller or hub for each ecosystem; a Thread border router for Thread devices | The SDK in each participating app; no server on local paths |
| What it standardises | Device types, clusters, attributes, commands and events, so any controller understands any certified device of a type | How apps find each other, verify identity, and exchange messages, replicated documents and service calls; the app defines the content |
| Identity and trust | Device attestation certificates for genuine products; operational certificates per fabric; multi-admin across ecosystems | Self-certifying Ed25519 identities verified device to device; MLS groups; optional OfflineID account binding |
| Encryption | Encrypted, signed messages between controllers and devices | MLS (RFC 9420), on by default |
| Interoperability guarantee | CSA certification, with each certified product recorded in the Distributed Compliance Ledger | None across vendors; any app with the SDK interoperates |
| Runs on | Certified devices, and controllers in Apple Home, Google Home, Amazon Alexa, SmartThings and Home Assistant | iOS and Android (React Native), Rust, Python on Linux, macOS and Windows, Java on the JVM, Ruby, a C API, early native Swift and Android, a preview Flutter plugin, an experimental browser build, and a no_std leaf profile for microcontrollers |
| Licensing and cost | Specification free to download; SDK under Apache 2.0. Certification requires CSA membership (Adopter $7,500 a year) and $2,000 to $3,000 per product, plus test-lab fees. CSA membership | Mesh SDK free under AGPL-3.0, including in production. Closed-source and App Store apps need the commercial license; contact us for pricing. Hosted services from $0 (Free), $99 a month (Pro), $499 a month (Scale). Local traffic is never metered. Pricing |
Where is Matter the better choice?
For device interoperability in the smart home, Matter is the standard the major ecosystems share. A certified Matter light, lock or plug works with Apple Home, Google Home, Amazon Alexa, Samsung SmartThings and Home Assistant, because each implements the same data model of device types and clusters. Certification by the Connectivity Standards Alliance, recorded in its public Distributed Compliance Ledger, is the guarantee a buyer can check, and each device carries an attestation certificate proving it is a genuine certified product.
Matter also keeps control local. The Alliance says Matter devices keep working within the local network when the internet goes down, and the major ecosystems control Matter devices over the home network rather than through their clouds. One device can belong to several ecosystems at once through multi-admin. The standard keeps growing: Matter 1.4 (November 2024) added solar, batteries, heat pumps and home routers with a built-in Thread border router; 1.5 (November 2025) added cameras, closures and energy tariffs; and 1.6 (June 2026) added NFC commissioning and Joint Fabric.
Offline Protocol does none of this. It is not a device standard, has no certification program, and is not built into any smart home ecosystem.
What does Offline Protocol cover that Matter does not?
Matter assumes devices and controllers share one IP network, and it describes devices, not the apps and people around them. Its published layers and device types do not include data sync between apps, identity for people or organisations, a mesh between phones, or calls between software agents.
Offline Protocol is built for that layer. Apps on phones, computers and gateways find each other over Bluetooth LE, the local network or a relay, relayed across up to 8 hops, with no server on local paths. They verify each other with self-certifying Ed25519 identities and talk in MLS-encrypted groups. They share working state as replicated documents that merge after offline edits, and they call each other's capabilities through serverless service discovery. The cloud stays the system of record.
The day-to-day result is less custom integration and fewer round trips: a technician pulls an asset's history from the site gateway, a driver and a yard worker complete a handoff phone to phone, and an agent on a gateway answers the apps around it, without each step waiting on a distant service.
Can Matter and Offline Protocol work together?
Yes, side by side. A gateway or app can act as a Matter controller for the certified devices on a site's network, using a Matter SDK or an ecosystem's APIs, and run Offline Protocol for coordination with the apps, gateways and agents around them. For example, a site gateway could read an EV charger's state over Matter and offer it as a capability that technicians' phones discover and call over Offline Protocol, even when those phones are not on the site's Wi-Fi.
Offline Protocol does not ship a Matter bridge, so that connection is application code you write and own. Keep each piece of data on one path, and decide in the app what crosses between the Matter side and the coordination side.
Which one should you choose?
Start from who has to work together. If it is devices and the controllers that run them, inside one home or building network, choose Matter. If it is people, apps, gateways and agents, across networks and organisations, choose Offline Protocol. Many sites need both.
Choose Matter when
You build or buy devices that must work with any major smart home ecosystem, you need a certification buyers recognise, and the devices and controller share one network.
Choose Offline Protocol when
Apps, gateways and agents at a site must discover each other, verify identity, share working data and call nearby capabilities, whether or not they share a network, with your cloud kept as the system of record.
Use both when
A site runs certified Matter devices and the people and machines around them need to coordinate. Let a gateway or app be the Matter controller and an Offline Protocol peer, and write the code that connects the two.
Where do these facts come from?
Matter facts are from the Connectivity Standards Alliance, the open-source Matter SDK and each ecosystem's own documentation, checked on October 20, 2026. Offline Protocol facts are from its documentation for SDK v0.31.0.
- Matter FAQ. Connectivity Standards Alliance on transports, local control, multi-admin, bridges and certification
- project-chip/connectedhomeip. The open-source Matter SDK, its layers, aim and license
- Matter 1.6 release. June 2026: NFC commissioning and Joint Fabric
- Matter 1.5 release. November 2025: cameras, closures, energy tariffs, TCP
- Matter 1.4 release. November 2024: energy devices, home routers with Thread, Enhanced Multi-Admin
- Why Matter devices belong on your primary Wi-Fi network. Local operation during outages, and one shared network
- Why certify. Transport choice, the Certification Declaration and DCL record
- Become a member. Membership tiers and per-product certification fees
- Distributed Compliance Ledger. The public record of certified products
- Connectivity Standards Alliance kicks off Unify. Membership, and commercial and industrial IoT, June 2026
- The fabric (Google Home Developers). Fabrics, operational certificates and multi-admin
- Set up a home hub (Apple Support). What a home hub provides for Matter accessories
- Matter support (Amazon Alexa). The Echo as local Matter administrator
- Offline Protocol platforms and transports. Where the SDK runs and what each path needs, v0.31.0
- Offline Protocol nearby service guide. Advertising, discovering and invoking a capability
Offline Protocol vs Matter FAQ
Is Offline Protocol an alternative to Matter?
Not for controlling smart home devices. Matter is the standard for certified devices from different brands to work with Apple Home, Google Home, Alexa and SmartThings, and Offline Protocol does not implement it. Offline Protocol covers a different job: coordination between the apps, gateways and agents at a site, including discovery, identity, shared data and service calls between devices that may share no network.
Can Offline Protocol control Matter devices?
No. Offline Protocol is not a Matter controller and does not ship a Matter bridge. An app or gateway can be both, using a Matter controller for the certified devices on the local network and Offline Protocol for coordination with other apps and people. The app decides what passes between the two.
Does Matter work without the internet?
Yes, inside the home. Matter is a local standard, and the Connectivity Standards Alliance says Matter devices keep working within the local network if the internet goes down. Control from away from home needs an internet-connected controller in the home, and some ecosystems need a hub before a device can be added. Read what keeps working locally.
Can Matter connect phones to each other?
No. In Matter, phones act as controllers and commissioners of devices on the home network. Matter does not define a mesh between phones or a way for apps to share their own data with each other. That is the job Offline Protocol does, over Bluetooth LE, the local network or a relay.
Is Matter used outside the home?
Matter is defined for smart home devices, and its device types are home devices, appliances, sensors and energy equipment. The Connectivity Standards Alliance says commercial and industrial IoT is where its influence is growing fastest, and its 2026 example for commercial spaces is Aliro, its access standard. Check that the devices a site needs exist as certified Matter products.
How do the costs compare?
They cost different things. The Matter specification and the open-source SDK are free, and certifying a product requires Connectivity Standards Alliance membership (Adopter from $7,500 a year as of October 2026), a per-product fee of $2,000 to $3,000, and test-lab fees. The Offline Protocol mesh SDK is free under AGPL-3.0-only when the app meets its obligations, closed-source and App Store apps need a commercial license, and hosted services run from $0 to $499 a month. Local traffic between devices is never metered. See Offline Protocol pricing.
