Appliance / Device Brands
Enable Matter faster for new or existing products
From standard modules and Matter SDK to Device Type / Cluster, host interfaces, and certification readiness, reduce the burden of coordinating multiple suppliers.
What are you trying to solve?
Start with the path that matches your product and business role, then explore the relevant technology and production approach.You do not need to understand every Matter term up front.
ODM / OEM / Manufacturing
Securely bring DACs, keys, and Factory Data into production
Plan DAC / PAI, private-key protection, work orders, serial numbers, MES / programming-tool integration, and traceability.
Gateway / System Integrators / Telecom Operators
Build a Thread control hub or add Matter / Thread capabilities to existing Gateways / APs / STBs / TVs
Evaluate USB / UART RCP, OTBR, Border Router, Bridge, and white-label integration based on your product architecture.
Not sure which integration path fits? Tell us about your current product and MCU / Module
Where should I start with Matter?
Choose a starting point based on your current hardware, engineering capabilities, and production plan.Then extend to full integration as your project requires.
Option 1 | Existing Hardware
Existing MCU / Module + Matter Integration
- Keep the existing hardware platform
- Matter SDK / Firmware
- DAC / PAI / Factory Data
- Production-tool integration
Option 2 | Shorten Time to Integration
Realtek Standard Module + DAC
- Standard Matter / Thread module
- Reference firmware and development tools
- DAC provisioning planning
- Customization based on product features
Option 3 | Upgrade Existing Products
RCP / Bridge + Firmware
- Evaluate USB / UART RCP
- Bridge / End Device architecture
- Host Command / I/O integration
- Minimize main-board redesign
Option 4 | Brand Production Deployment
Matter Integration and Production
- VID / PID and DAC / PAI planning
- CD / DCL certification preparation
- MES / work orders / provisioning
- Production traceability
Why Ciot?
With a Realtek-first Matter / Thread approach, Ciot connects modules, Matter SDK, DAC device identity, security keys, firmware, and production provisioning—reducing the integration burden of coordinating multiple suppliers.
Realtek-first Platform Integration
Prioritize Realtek Matter / Thread modules, RCPs, and platforms, then select an integration path based on product role and existing hardware architecture.
DAC Device Identity and Security
Plan DAC / PAI, private-key protection, TrustZone, or Secure Element integration to establish verifiable Matter device identity.
Product and Firmware Integration
Integrate Device Type, Cluster, Host Command, and GPIO / UART / I²C / SPI requirements with existing product-control logic.
Certification and Production Readiness
From Factory Data and DAC provisioning to MES / work orders and traceability, help move products from development and testing toward production readiness.
If another MCU or module has already been selected, you can keep the existing hardware architecture and use Ciot for Matter, security, and production integration. Realtek-first does not mean Realtek-only.
Complete Matter over Thread Hardware Platform
Explore Matter over ThreadFirst select the network role—End Device, Router, RCP, Border Router, or HMI—then choose the module and integration approach.
| Module / Platform | Application Role | Core Capabilities | Typical Use Cases |
|---|---|---|---|
| RTL8771GUV | Thread RCP（USB） | USB interface, Thread Radio Co-Processor | Add Thread connectivity to Gateways, STBs, and existing hosts |
| RTL8771HTV | Thread RCP（UART） | UART interface, Thread Radio Co-Processor | Appliance control boards and existing MCU integration |
| RTL8777G | End Device / Router | Matter over Thread, Bluetooth LE, and TrustZone security architecture | End devices such as lighting, plugs, locks, blinds, and sensors |
| RTL8772GWP | Border Router / HMI | Display and multitasking, Thread / IP integration | Thermostats, control panels, and smart-home hubs |
Reduce Integration Effort with Standard Modules
Module / End Device
- Reduce RF and low-level hardware development effort
- Use reference firmware and interface documentation
- Plan DAC / Factory Data per project
Matter Upgrades for Existing Products
RCP / Bridge
- USB / UART RCP architecture
- Existing MCU / Host communication integration
- Evaluate Bridge / End Device paths
OTBR / Gateway Integration
Border Router / White-label
- Thread Border Router / OTBR integration
- Connect RCP with existing Gateways / APs / STBs / TVs
- Evaluate white-label and system-integration paths
Firmware and Security Customization
Firmware / Security
- Device Type / Cluster customization
- Host / I/O interface integration
- TrustZone / Secure Element / Provisioning
Note: Using a module can reduce RF design and testing effort, but it does not exempt the end product from required certifications. Actual requirements depend on the module's certification status, Matter End Product Certification, product type, and target market.
Matter DAC Device Identity and Production Provisioning
During commissioning, a Matter device uses Device Attestation to prove its identity. Production products need a plan for the DAC, corresponding private key, and attestation trust chain, with certificates, keys, and Factory Data integrated into the production process.
1
PAA | Root of Trust
The Product Attestation Authority is the root of the Matter Device Attestation trust chain and should be planned according to brand, VID / PID, certification, and production strategy.
2
PAI | Intermediate Issuer
The Product Attestation Intermediate connects the PAA and product DAC. Define certificate workflows and data requirements for both testing and production.
3
DAC | Unique per Device
Each production device receives a unique DAC and corresponding private key. Key protection and secure injection are planned based on the MCU, TrustZone, or Secure Element architecture.
PAA→PAI→DAC→Device
During commissioning, the Commissioner validates the trust chain using the device's attestation data. Production products must also prepare the Certification Declaration (CD) and other required materials under the Matter Certification process.
Advanced Security: From Chip to Product Lifecycle
Based on the MCU, product risk level, and lifecycle requirements, integrate TrustZone, Secure Element, Secure Boot, key management, and secure communications.
1
Tiered Architecture
Evaluate standard MCU, TrustZone MCU, or MCU + Secure Element architectures based on product risk and cost requirements.
2
Core Security Functions
Secure Boot, key protection, device identity verification, secure communications, firmware integrity, tamper resistance, and related controls.
3
Hardware Root of Trust
Integrate Secure Elements from Infineon, iMQ, and others as required to strengthen private-key and device-identity protection for high-sensitivity devices.
Ciot Security SDK Architecture
Standard MCU
Matter Secure Lib
TrustZone MCU
Matter Secure Lib + Crypto API
MCU + Secure Element
Matter Secure Lib + Crypto API（HW）
Production and Lifecycle Management
Matter is not only about connectivity. Each device must also receive the correct unique identity, security keys, and production data.
Automated Production Provisioning
Support binding of DAC, Factory Data, serial numbers, and work orders, with integration evaluated for the MES, programming tools, and production environment.
Certificate and Traceability Management
Manage certificate issuance batches, device mappings, injection records, and audit trails, with certificate-status management extended across the lifecycle as required.
Align with Matter Certification and IoT Compliance Requirements
With Security by Design, Ciot helps manufacturers build device identity, key protection, secure updates, and production traceability into product design as a technical foundation for certification and regulatory requirements.
| Target Market / Standard | Capabilities Ciot Matter Can Help Establish |
|---|---|
| CSA Matter Certification | DAC / PAI / PAA architecture, VID / PID mapping, CD / DCL preparation, and platform / product testing support. |
| EU RED Cybersecurity | Help establish the technical foundation for device identity, key protection, secure communications, and product cybersecurity controls. Applicability depends on product scope and conformity-assessment requirements. |
| EU Cyber Resilience Act（CRA） | Support Security by Design, vulnerability handling, secure updates, and product lifecycle management as preparation for CRA compliance. Actual obligations and timelines depend on product type and applicable regulatory requirements. |
| UK PSTI | Device identity, secure configuration, vulnerability handling, and secure-update mechanisms can form part of the product-security foundation. Manufacturers remain responsible for implementing applicable requirements such as password policies, vulnerability-reporting mechanisms, and minimum security-update periods. |
| Japan JC-STAR | Can provide a technical foundation for device identity, key protection, secure updates, and vulnerability-management processes. Applicability depends on the product and evaluation level. |
| ETSI EN 303 645 | Support the design and implementation of multiple IoT security baseline controls to help align with downstream regulatory and product-security requirements. |
Note: A Matter Compliant Platform, module, or security function provided by Ciot does not mean the end product itself is Matter-certified or certified under applicable market regulations. Requirements depend on product type, software version, target market, and certification scope.
Planning a Matter product? Tell us where you are today.
Share your product type, current MCU / Module, planned connectivity (Thread / Wi-Fi), target market, and estimated production timeline.Ciot can help define the most suitable integration path and scope.
Please include: Product Type｜MCU / Module｜Thread / Wi-Fi｜Target Market｜EVT / DVT / MP
Discuss My Matter Project