How Cryptographic Fabric Slots Let Matter Devices Execute Local Commands Across Rival Ecosystems

A smart bulb can respond to Siri and Alexa simultaneously without internet routing because it stores a distinct cryptographic certificate for each ecosystem in isolated hardware memory slots. When a command arrives over the local network, the device verifies the signature against the specific ecosystem's certificate, executing the instruction entirely on-device.[1][3]

This mechanism, known as Multi-Admin within the Matter protocol, fundamentally changes how smart home hardware operates. Instead of relying on cloud-to-cloud API bridges that introduce latency and points of failure, the interoperability is baked directly into the local silicon.[1]

The shift eliminates the traditional walled gardens of home automation. By standardizing how cryptographic identities are issued and stored, the Connectivity Standards Alliance (CSA) has forced competing tech giants to share access to the same physical hardware without sharing user data.[1][4]

The Legacy Cloud Bottleneck

Prior to the Matter specification, cross-platform compatibility was an exercise in server-side routing. If a user asked Google Assistant to activate an Amazon-linked smart plug, the command could not travel directly to the device on the local network.

Instead, the request traveled from the user's phone to Google's servers, across the internet to Amazon's servers via an OAuth integration, and finally back down to the plug. This cloud-to-cloud API polling typically introduced an average round-trip latency of 850 milliseconds.[4][5]

Beyond the delay, this architecture was fragile. If either company's server experienced an outage, or if the user's internet connection dropped, the local hardware became unresponsive. The device was effectively a thin client waiting for remote instructions.[5]

How Matter Fabrics Isolate Ecosystems

Matter solves this dependency by introducing the concept of a fabric. A fabric is a closed, logical network of devices and controllers that share a common cryptographic root of trust, operating entirely within the local area network.[1]

When a user pairs a new smart lock to Apple Home, Apple's ecosystem acts as a Certificate Authority. It generates a unique Node Operational Certificate (NOC) and securely provisions it onto the lock over a local Bluetooth or Wi-Fi connection.[3]

This certificate binds the device to the Apple fabric. The lock stores the NOC in a dedicated segment of its non-volatile memory, known as a fabric slot, allowing it to cryptographically verify any future commands originating from Apple controllers.[1]

Cryptographic Slots and Multi-Admin

The breakthrough of Matter is that a device is not limited to a single fabric. The specification mandates that certified hardware must support a minimum of five concurrent fabric slots, allowing the device to hold distinct identities for multiple ecosystems simultaneously.[1]

"The Multi-Admin feature requires that a Node be able to concurrently participate in multiple Fabrics," the CSA Matter Specification 1.3 states. "Each Fabric provides an independent cryptographic domain."[1]

If the user subsequently shares that same smart lock with Google Home, Google acts as a separate Certificate Authority. It issues its own 256-bit elliptic curve cryptography (ECC) certificate, which the lock saves into its second fabric slot.[3]

The two ecosystems remain entirely isolated from one another. Apple cannot read the Google certificate, and Google cannot access the Apple certificate. The hardware simply maintains a secure, independent relationship with both controllers.

Access Control and Privilege Isolation

Storing a certificate is only the first half of the security equation. To prevent a compromised ecosystem from wreaking havoc on the entire home, Matter pairs each fabric slot with a strict Access Control List (ACL).[1]

When the device receives a cryptographically valid command, it consults the ACL associated with that specific fabric. The ACL dictates exactly which clusters—Matter's term for specific device functions, like brightness or temperature—that particular ecosystem is permitted to modify.[2]

If a user grants a third-party energy monitoring app access to a smart plug via a new fabric slot, the ACL can be configured to allow read-only access to the power draw. The device will explicitly deny any command from that fabric attempting to switch the plug off.

Bypassing the Internet

With the certificates securely stored on-device, command execution shifts from the cloud to the local network. When a user issues a command via Google Home, the Google hub sends an IPv6 UDP packet directly to the lock over the local Wi-Fi or Thread network.[2]

This packet is encrypted and signed using Google's fabric credentials. Upon receiving the packet on UDP port 5540, the lock checks the signature against the Google NOC stored in its second fabric slot.[2][3]

Because the cryptographic verification happens on the device's own microcontroller, the command executes in under 40 milliseconds. The internet is completely bypassed, meaning the automation continues to function even if the home's broadband connection goes offline.[4][5]

The Role of Thread Border Routers

While Wi-Fi devices handle these UDP packets natively, low-power sensors rely on the 802.15.4 Thread protocol. Thread devices cannot connect directly to a standard Wi-Fi router, requiring a Border Router to bridge the two networks.

Because Matter fabrics operate at the IPv6 network layer, the Border Router does not need to understand the encrypted payload. It simply takes the IPv6 packet from the Wi-Fi network and forwards it onto the Thread mesh, preserving the end-to-end encryption.[2]

This means an Apple HomePod can act as a Border Router to pass a Google Home command to a smart lock. The HomePod routes the packet blindly, unable to read the contents because it lacks the specific Google NOC required to decrypt the payload.

The Memory Cost of Interoperability

While the protocol delivers on its promise of local control, the marketing often obscures the hardware realities of this cryptographic overhead. Maintaining multiple secure connections requires substantial memory, which is a scarce resource on cheap Internet of Things devices.[4][5]

Each active fabric slot consumes approximately 4 to 6 kilobytes of RAM to manage the encrypted session state. This sits alongside the non-volatile memory required to store the certificates and access control lists.[5]

For a smart bulb utilizing a low-cost microcontroller with only 256 kilobytes of total RAM, supporting the mandated five fabric slots consumes a significant percentage of its available resources. This is why many manufacturers struggled to update older hardware to support the standard.[4][5]

Marketing Versus Shipped Reality

The capability is real, but the user experience remains fractured. While the hardware can execute commands from competing ecosystems without cloud linking, the tech giants still design their apps to prioritize their own walled gardens.[4]

Sharing a device from Apple Home to Samsung SmartThings requires generating a temporary pairing code, opening the rival app, and repeating the commissioning process. The underlying cryptography is seamless, but the interface is deliberately cumbersome.[4]

Furthermore, while basic commands are standardized across all fabrics, advanced features often remain locked behind proprietary vendor extensions. A smart thermostat might expose its temperature control to all fabrics, but reserve its energy-tracking data for its native app.[1]

This reveals the tension at the heart of the standard. The Connectivity Standards Alliance succeeded in decentralizing the command execution, but the ecosystem providers are still fighting to maintain user lock-in at the software layer.[4]

The true durability of this architecture lies in consumer ownership. By moving the authentication from remote servers to local silicon, the protocol ensures that a purchased device will continue to function on the local network long after its manufacturer's cloud servers are eventually shut down.[4]