MatterODM by Shenan YangguangWhat "Matter-ready new construction" means
A Matter-ready building is one where the structured cabling, the device mounting points and the network design are specified so that interoperable Matter security endpoints — door contacts, PIR occupancy sensors, panic buttons — can be commissioned by any compliant Matter controller, not just one brand's hub. The developer is not choosing a finished alarm system at the design stage; they are choosing a wiring and device philosophy that keeps the door open. That distinction is the whole point: the building is spec'd for interoperability, not for a single vendor's ecosystem, and the actual controller decision can be made later or changed later.
For a brand selling into construction, this reframes the pitch from "here is our system" to "here are certified endpoints and the commissioning documentation your electrician and your chosen controller already understand," which is a far more durable position in a market where buildings outlive most software vendors. The value is in supply and certification, not in locking the asset.
The pre-wire and structured-cabling decision
The pre-wire decision is whether to run low-voltage cabling to sensor and reader locations during construction or to rely on battery wireless endpoints, and for a Matter security rollout the answer is usually a mix: powered hubs on structured cabling, battery sensors where wiring is impractical. Powered devices — a border-router hub, a panel, any fixed reader — want cabling for both data and power; the long-tail of door and motion sensors is usually better left wireless to avoid a wiring job in every unit. The split is decided at the pre-wire stage, and getting it wrong locks in either cost or coverage gaps that are expensive to fix later.
Specifying the mounting points and the conduit even where you run wireless endpoints costs little at construction and preserves optionality, because a blank plate today is cheaper than a chase tomorrow. The disciplined developer pre-wires for the worst case and installs the minimum.
Why hub-agnostic protects the asset
Hub-agnostic protection means the building is not stranded if the original security vendor changes price, policy or ownership, because the Matter endpoints keep working with whatever compliant controller the owner chooses next — a property-rights argument as much as a technical one. A proprietary system installed across a hundred units is a liability the moment the vendor reprices the cloud or exits the market; the residents and the manager are held hostage to a contract they did not read at construction. Matter removes that trap by decoupling the endpoints from the controller.
The financial case is straightforward: a building financed over decades should not carry a technology lock-in measured in years, and a hub-agnostic spec is the cheapest insurance a developer can write into the drawings. It costs almost nothing to specify and saves a forced rip-and-replace.
Occupancy, access and the resident experience
For a multi-dwelling unit, Matter security overlaps with access and occupancy: a door contact on the entry, PIR occupancy for communal areas and a panic endpoint for staff give a manager intrusion awareness and energy insight from the same interoperable layer. The same endpoints that flag an unauthorised entry also confirm a corridor is empty, which feeds lighting and HVAC without a second sensor network. The resident gets a coherent experience — one app, one controller — rather than a stack of single-purpose boxes.
Because the layer is interoperable, a resident who already owns a Matter controller at home can often manage their unit with it, which is a selling point a developer can put in the listing without committing the building to one ecosystem. That resident-side flexibility is a downstream benefit of the same hub-agnostic spec.
Compliance for an installed system
An installed security system in a new building still meets the same product marks as a retail device — CE/UKCA, FCC, RoHS — and it must also satisfy the local fire, access and electrical codes that govern fixed installations, which differ by jurisdiction and are the owner's and installer's duty to confirm. The device marks prove the hardware; they do not prove the way it was wired into the wall, and a building inspector cares about the latter. A factory can supply the marks and the documentation, but it cannot certify an installation it did not perform.
Volume supply and the developer's procurement
At the volumes a multi-dwelling or new-build project implies, procurement is a supply-continuity question as much as a unit-price one, and the realistic risk is not the quoted cost but whether the supplier can deliver thousands of certified, consistent units on a construction schedule that does not wait. A supplier that owns the line and the certification is a different proposition from one that reboxes; the construction programme will find out which you chose at the worst possible moment if you guessed wrong.
What the factory delivers for a volume build
The factory that owns the source and the line supplies the endpoints at volume on a standard CSA-certified Matter connectivity module, supports the commissioning documentation and the white-label app and cloud stack if the developer wants a branded resident app, and carries the certifications the project's markets require. A relabeller cannot own the certification, cannot scale the line, and cannot support the commissioning documentation a building's electrician needs; it can only hand over boxes. The line between a builder and a reseller shows up precisely at volume.
Shenan Yangguang builds and certifies the Matter security hardware we produce and owns the tooling, the firmware and the volume line behind a construction or MDU rollout; we do not resell someone else's characterisation. If you are specifying Matter security for a new build or a multi-dwelling project, send us the unit count, the endpoint mix and the target markets; we will show you the hardware, the marks and the commissioning plan.