Matter Controller Manufacturer — Matter and Thread Hub OEM/ODM

Matter is the industry agreement that lets one device join Apple Home, Google Home, Amazon Alexa and SmartThings without the manufacturer writing four separate integrations. A Matter controller — often built as a Thread border router — is the piece of hardware that brings Matter devices onto the local IP network and keeps them reachable by every ecosystem at once.

For a brand owner this changes the commercial maths. Instead of certifying and maintaining one app per ecosystem, you certify once and the device is commissionable anywhere. The cost moves from integration work to certification work, which is why the decision to build Matter needs to be made at the platform stage rather than as a late firmware option.

XingLiao builds Matter controllers, Thread border routers and protocol bridges in Shenzhen, on proven platforms with 7 to 15 day sampling.

What a Matter controller actually does

A Matter device speaks IP. That is the core of the standard — no proprietary mesh translation at the application layer. But many Matter devices are low-power sensors and locks that run on Thread, a low-power mesh that is not itself IP-routable to your Wi-Fi. Something has to connect the Thread mesh to the home Wi-Fi or Ethernet network. That something is the Thread border router, and it is usually the same physical box as the Matter controller.

So a Matter controller in practice does three jobs: it commissions new devices onto the fabric, it routes between Thread and Wi-Fi or Ethernet, and it holds the fabric credentials so that a second ecosystem — Apple Home after Google Home, for example — can be added later without re-pairing anything.

Matter controller specifications

Matter does not replace Zigbee — yet

This is the most common planning mistake. Zigbee 3.0 has ten years of deployed devices, mature low-cost modules, and a component supply chain that is stable and cheap. Matter has interoperability and ecosystem backing but a smaller installed base of end devices, and certification adds cost per device.

The practical answer for most brand owners is a dual-protocol controller: Zigbee 3.0 for the device fleet you ship today, Matter and Thread for the ecosystem compatibility your retail channel will require within two years. One box, one app, both protocols. A Zigbee gateway that also border-routes Thread is the configuration we recommend for anything shipping in 2026.

There is also a migration path for devices already in the field. A Matter bridge can expose existing non-Matter Zigbee devices to a Matter fabric, so a customer's installed base does not become obsolete. That is a real selling point in retrofit markets and worth building into your product story.

Certification: the part that needs a timeline

Matter is not self-declared. To use the Matter logo and to have commissioning work reliably across ecosystems, a device goes through CSA certification, which requires a registered vendor ID and a product listed in the Connectivity Standards Alliance's distributed compliance ledger. Testing is done at an authorised test lab, and the results are submitted with the certification.

Two consequences for your planning. First, budget calendar time — certification is measured in weeks and can bottleneck a launch. Second, decide at platform selection, because retrofitting Matter onto a radio platform that was never qualified for it is more expensive than choosing the right module at the start.

We support clients through this: module selection, test-lab preparation, and documentation. What we do not do is promise a Matter logo on a platform that cannot carry it.

Where Matter controllers are deployed

• Retail smart home ranges where the box must state "works with Apple Home, Google Home and Alexa" without qualification.
• New-build developers who cannot know which ecosystem the buyer will use.
• Hotels and serviced apartments needing one commissioning flow that survives a change of management platform.
• Security and sensor fleets on Thread, where battery life and mesh reliability are the buying criteria.
• Distributors hedging protocol risk who would rather not bet the catalogue on either Zigbee or Matter alone.

Private label scope and volumes

Standard controllers with your branding start at 500 pieces per colour. Firmware work — your app, custom commissioning flow, installer bulk provisioning — begins around 3,000 to 5,000 pieces. New enclosure tooling takes 25 to 40 days.

Controllers are normally developed together with door and window sensors, Tuya smart switches, smart locks and motion sensors, so the whole fleet commissions into one fabric.

Frequently Asked Questions

Is Matter going to make my Zigbee products obsolete?

Not in the near term. Zigbee 3.0 remains the cheaper, more mature device protocol. Matter's advantage is ecosystem interoperability, and a dual-protocol controller supports both at once.

Do I need Thread, or is Matter over Wi-Fi enough?

Matter over Wi-Fi suits plugs, switches and appliances that are mains-powered. Battery sensors and locks need Thread, which means your controller must be a Thread border router.

How long does CSA certification take?

Plan in weeks, not days, and start it at platform selection. Testing happens at an authorised lab and the listing is published to the compliance ledger.

Can existing Zigbee devices be exposed to Matter?

Yes, through a Matter bridge. It exposes non-Matter devices to a Matter fabric so an installed base stays usable — a strong argument in retrofit markets.

What is the minimum order quantity?

500 pieces per colour on an existing platform; custom firmware or tooling from roughly 3,000 to 5,000 pieces, with tooling at 25 to 40 days.

Which ecosystems do you test against?

Apple Home, Google Home, Amazon Alexa and SmartThings. Commissioning is validated per ecosystem rather than on one and assumed for the rest.

Does the controller keep working offline?

Local scenes and local control run on the device. Remote access from outside the home needs an internet connection, as with any hub.