Matter gateway & Thread border router In development

A gateway is two products in one enclosure, and the two roles have different certification consequences. As a Thread border router it provides the network your battery sensors join. As a bridge it exposes existing non-Matter devices to the ecosystem. Brands ask for both; we design them as one platform with each role's requirements mapped separately.
Thread border router Matter bridge Multi-protocol In development

The two roles

Device type and cluster selection for the combined product is confirmed at design freeze, since combining roles changes the test surface.
RoleWhat it doesWhy it matters
Thread border routerProvides the Thread network that battery-powered Matter devices join, and routes that traffic onto the home IP networkWithout one, a Thread sensor cannot be commissioned. If you sell Thread devices, you are implicitly asking the customer to already own a border router — or you sell them one.
Matter bridge / aggregatorPresents non-Matter devices to the Matter ecosystem as bridged endpointsLets a brand carry its existing installed base into Matter without replacing the hardware in the field.
Multi-protocol coexistenceThread, Wi-Fi and Bluetooth radios sharing one enclosure with acceptable RF isolationAntenna design and isolation are the engineering problem here, not the software.
The commercial argument for a bridge. If you already have thousands of installed non-Matter devices, a bridge is how you sell those customers Matter compatibility without a recall. It is a very different product from a border router, and it is usually the one that pays for itself.

Design considerations

RF

Three radios, one box

Thread, Wi-Fi and Bluetooth in the same enclosure means antenna placement and isolation become the primary design constraint. This is decided at mechanical layout, not tuned afterwards.

Power

Always-on, different rules

Unlike a battery sensor, a gateway is mains-powered and always on. That removes the energy constraint and adds thermal and reliability ones.

Bridging

Translating a foreign device

Every bridged device needs a mapping from its own data model to Matter clusters. The quality of that map decides how well the device behaves inside the ecosystem — and it is where bridging projects usually fail.

Certification

Two roles, one submission

Combining roles changes the endpoint structure and the test surface. We confirm the final device-type and cluster allocation before firmware implementation.

Specifications

Development-stage outline. Full specification is published at design freeze.
ParameterCurrent design direction
RolesThread border router; Matter bridge / aggregator
RadiosThread, Wi-Fi, Bluetooth Low Energy
PowerMains
EthernetOption under evaluation for wired backhaul
HousingTo be defined with the design partner
Certification statusIn development

Customisation & ordering

ItemDetail
MOQConfirmed once the role combination and enclosure are fixed.
Available nowArchitecture discussion and scoping. Samples follow design freeze.
CustomisableRole combination, radio set, enclosure and industrial design, Ethernet option, firmware feature set and local-language onboarding flow.
Certification ownershipYour Vendor ID or transferred to you, agreed before the project starts.
If your goal is simply to ship a Matter sensor product, you usually do not need to build a gateway — the customer's existing ecosystem hub often provides the Thread border router. Ask us before adding this to the bill of materials.

Related reading

Composed devices, bridges and multi-endpoint products

Service guide

How endpoint structure changes the certification test surface.

Matter door / window contact sensor

Product

The Thread sensor that a border router exists to serve.

Gateway, bridge, or neither?

Tell us what you are trying to achieve. Sometimes the answer is that you do not need this product at all, and we will say so.

Request a Quote