Thread and Matter get talked about together so often that it's easy to assume they're the same thing. They're not, and the difference is exactly why a Border Router matters.
Matter is the application layer, the standard that lets a switch, a sensor or a driver speak a common language to Apple Home, Google Home, Alexa or Home Assistant, regardless of who made the device. Thread is a radio protocol, a low-power mesh network that devices can run Matter on top of, as an alternative to running Matter over Wi-Fi. A device is either "Matter over Wi-Fi" or "Matter over Thread," not both at once, and that choice is usually fixed by the chip inside it.
What a Border Router actually does. A Thread mesh network is self-contained. Devices on it talk to each other locally, forming a self-healing mesh where messages can hop between devices instead of depending on one central hub. But that mesh, on its own, has no way to reach your home Wi-Fi, the internet, or your controller app. A Thread Border Router is the bridge: it connects the Thread mesh to your IP network, so your phone can control a Thread device, and so that device's status can sync into your smart home platform.
You might already have one and not know it. Several mainstream smart speakers and hubs include Border Router functionality built in: Apple HomePod mini, current-generation Apple TV, several Google Nest devices, and some Amazon Echo models all quietly run this role once set up. If you already own one of these and have set up Apple Home, Google Home or Alexa, you may already have Thread coverage without ever buying a dedicated device.
When a dedicated Border Router makes sense. Thread supports multiple Border Routers on the same network for redundancy, unlike a single Wi-Fi router being the one point of failure, so adding a dedicated unit isn't wasted even if you already have one from a smart speaker. It's worth it specifically when: you don't already own a compatible hub, you're installing Thread devices in a space too far from your existing Border Router for reliable mesh coverage, or you're doing a commercial or multi-unit install where relying on a consumer smart speaker's uptime isn't acceptable.
FAQ
Is Thread the same as Matter?
No. Matter is the cross-platform application standard; Thread is one of the radio protocols Matter can run over, alongside Wi-Fi. A device is built for one or the other, not both.
Do I need a Border Router for every Thread device I own?
No, you need at least one Border Router active on your network to bridge any Thread devices to your app and the internet, not one per device. Multiple devices share the same Border Router(s).
What happens to my Thread devices if the Border Router goes offline?
Devices on the Thread mesh can usually still talk to each other locally (for example, a Thread switch can still control a Thread bulb directly), but remote access, app control from outside the home, and cloud-dependent automations stop working until the Border Router is back online.
Does Rez-ti make a Border Router?
Yes. It's built on the same Matter-native hardware platform as the rest of the catalog, intended for buyers who want a dedicated, reliable Border Router rather than depending on a consumer smart speaker, particularly relevant for OEM/ODM partners specifying a full Matter product line rather than assuming end users already own compatible hubs.