Skip to content
KyrionKyrion

DEVELOPMENT

A platform in progress. A direction with purpose.

Kyrion is a working prototype moving toward private-alpha validation. It is not a finished consumer product and is not generally available.

In development

CURRENT CHECKPOINT

Strengthen the foundation. Then make interaction feel natural.

Recent work consolidates read-only Home Assistant import, service diagnostics and the action inspector. The next dedicated Velora phase focuses on repeatable processing, audio and confirmed device results.

Read the repository development notes

Where the platform stands

Home control

Manage rooms, lighting and device state through a common catalog. Nanoleaf, Philips Hue via Zigbee and a bounded Bluetooth light path have working implementations.

Available

Connected ecosystems

Native control paths plus a bounded, read-only Home Assistant device/state import. The HA import still awaits physical verification.

Available

Local intelligence

Local streaming chat and bounded German/English command proposals. Core validates permissions and targets before any action is executed.

Available

Shared installations

Owners can invite additional accounts to shared device control. Granular owner/member/guest household roles are not implemented yet.

Available

Diagnostics & activity

Service health, explicit device availability and correlated action history. Inspect decisions and execution outcomes without guessing.

Available

Local infrastructure

Core, local persistence and a bounded Raspberry Pi gateway form the current foundation. Cloud providers are optional capabilities.

Available

Velora & voice

Wake-word detection, transcription and multi-turn voice paths exist. Repeatable end-to-end voice and audio acceptance remain in development.

Experimental

Automations

Future scheduled and event-driven workflows through Core policy. A general automation builder and execution platform are not available.

Planned

Broader integrations

Versioned plugin contracts, richer Home Assistant capabilities and more device ecosystems. A public marketplace is not implemented.

Planned

Reading the status

Available

Implemented in the prototype. Not a general-availability release.

Experimental

An isolated or bounded implementation still requiring validation.

In development

Active work that has not met its acceptance boundary.

Planned

Future direction. Scope and delivery are not committed.

The road ahead

Outcome-oriented direction, without invented deadlines.

  1. 01In development

    Validate the everyday experience

    Reliable voice feedback, observable outcomes and repeatable behaviour on local hardware.

  2. 02Planned

    Build deeper home coordination

    Automations, richer household permissions and further integration capabilities.

  3. 03Planned

    Open up carefully

    Public documentation, broader validation and extension contracts before a public marketplace.

Features, scope and architecture may change as the platform is tested. No release dates, public alpha access or commercial availability are announced.

Currently in development

Follow the development

No public release date. No general availability. Features and architecture may change.