Hardware Infrastructure
Validated Infrastructure

Hardware Certification

Curated devices, validated topologies, and known failure modes — because reliability is a choice.

REQUEST A PILOTVIEW PROTOCOLS

Certified hardware only

Production environments are not laboratories. Vœrynth is commissioned with a validated hardware set so behavior stays stable across updates, replacements, and time.

Hardware Compatibility List (HCL)

Entries below are examples. We maintain a versioned HCL per release line.

Class A — Approved

CategoryModel/ClassNotesReplacement
Wired GatewayKNX IP InterfaceStable topology; version-pinnedReplace with same class; restore config bundle
Mesh CoordinatorZigbee CoordinatorCertified firmware; monitored healthReplace, re-pair via commissioning procedure
Mesh ControllerZ-Wave ControllerCertified region; monitored healthReplace, restore network keys; validate node health
Mesh ProtocolThread Border RouterCertified firmware; monitored healthReplace, restore network keys
Integration StandardMatter BridgeLocal control only; verified vendorReplace, re-authenticate fabric

Class B — Conditional

CategoryModel/ClassConditions
Bluetooth GatewayBLE BridgeAllowed for convenience; not for safety-critical control
Consumer HubsGeneric Home HubsOnly as isolated boundary devices; no core dependency
IP DevicesWiFi-based DevicesIsolated VLAN only; static IP assignments required
EcosystemApple HomeKitSecondary UI only; automation logic must remain in Vœrynth core

Class C — Not Supported

CategoryReason
Uncertified ClonesUnstable firmware / inconsistent behavior
Auto-updating DevicesVendor updates break deterministic behavior

What certification includes

  • Firmware version constraints
  • Topology and placement rules
  • Failure and recovery behavior
  • Update compatibility checks
  • Replacement procedure

Stability First

We only support what we can test, validate, and guarantee. If it breaks in a lab, it doesn't go to your site.

Prefer systems that age well?

REQUEST A PILOTVIEW RELEASE POLICY