Control lighting, organize events and find information again: Kyrion is bringing these tasks together step by step. You choose which devices, services and AI capabilities to use.
In development
Development prototype, not a generally available product. Implemented code, automated tests and real-world acceptance are different kinds of evidence. Business and personal document retrieval have open integration and validation work.
Create rooms, assign devices and control selected lights. Nanoleaf and specific Zigbee/Bluetooth lights have physical evidence. This does not establish support for every model. Home Assistant supplies a bounded device/state import; full hardware acceptance remains open.
Implemented in prototype
Bring events and services together
Local events, bounded editing of ordinary Google events and explicit synchronization of individually linked events are implemented, with live checks using marked test events. All-day and recurring Google events remain read-only. Spotify Web receiver acceptance is open; YouTube uses the visible browser player.
Experimental
Choose how assistance helps
K-AI provides local chat and bounded command proposals. Confirmed memories, history and a personal calendar can be enabled as context. Velora adds voice; repeatable dialogue reliability still needs validation. A satellite does not identify its speaker and receives no private context.
Experimental
Find answers in your documents
An initial implementation provides personal PDF/text upload and local retrieval with sources. Additional fixes were tested separately and are not fully integrated. Real model answers, installation and recovery still need validation; no team knowledge, OCR or cloud document context.
Local control. Deliberate cloud choices.
Core manages permissions and validates actions. Basic device controls do not require AI. Local models and document retrieval need separately configured runtimes and suitable hardware. Local first does not mean every connected service runs locally.
Google, Spotify and other external services require their own connections. Cloud AI is optional and needs provider access and explicit consent. The current AI path releases only the current message; personal memories, history, calendar and documents are not released as cloud context. Fully local operation of every feature is not promised.
Setup and access today
Kyrion currently requires technical experience and your own development environment. Web, Core and PostgreSQL are configured separately; AI and voice need additional local services. Supported devices must be reachable on your network and explicitly enrolled. A Raspberry Pi can serve as a gateway, but is not an established replacement for all AI hardware.
There is no released consumer installer, general signup or guaranteed alpha/beta access. You can express interest in future testing through the existing contact channel.