Capability-aware devices
CANVAS adapts controls to the capabilities a device reports instead of forcing every light, television, sensor, or climate device into one generic card.

HELIX connects the home, gives AI a bounded way to understand intent, and keeps execution inspectable, permission controlled, and recoverable.
HELIX builds a normalized model of rooms, floors, devices, capabilities, users, integrations, and events while keeping vendor-specific behavior isolated.
CANVAS adapts controls to the capabilities a device reports instead of forcing every light, television, sensor, or climate device into one generic card.
Integrations communicate through a small versioned protocol so one flaky vendor or cloud service does not take down the platform.
Prefer local APIs and protocols. Add cloud accounts only where the device requires them and keep those dependencies explicit.
Owner, administrator, and household permissions create a path toward appropriate access for powerful controls and sensitive context.
HELIOS can discuss the home, control supported devices, help create dashboards and automations, diagnose integration problems, and explain system events.
Requests are routed to models that can perform the required task, including structured tool use.
Unavailable or incapable models can be detected and replaced without silently degrading the experience.
HELIX can notice routines and offer suggestions while leaving approval with the household.
Answers can use current devices, rooms, connector health, events, and household context rather than generic smart-home advice.
CANVAS is the visual surface for rooms, devices, conversations, integrations, users, migration, system events, and add-ons.
Action completed through the local connector. Event evidence retained.
HELIX treats migration as a staged, reversible process rather than a one-way import that risks the working home.
Authorize a source without changing it.
Stage devices, rooms, names, and source integrations.
Select what should move and clean up noisy entities.
Review the exact proposed diff and integration gaps.
Apply the approved migration to HELIX.
Reverse the commit if the result is not right.
HELIX connectors are proprietary, clean-room integrations built against vendor APIs and the HELIX connector protocol.
For suitable REST integrations, HELIX can work from a vendor OpenAPI specification instead of relying on a language model’s memory.
Generated manifests are validated against defined rules and tested against the live API before use.
Each connector remains independently buildable, testable, restartable, and diagnosable.
Early access is for people prepared to test actual integrations, document limitations, and help shape a platform built for long-term operation.