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

Prepare a safe fresh installation. Prove it on real hardware.

Installation-wide RBAC, local Calendar CRUD and read-only Google Calendar display are implemented. Installer v1 validates fresh-install boundaries and signed manifests, but has no released artifact bundle. ARM64 acceptance, certificate provisioning, backup/restore verification and a clean Pi rehearsal remain open.

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 chat & proposals

Local streaming chat and bounded German/English command proposals. Core validates permissions and targets before any action is executed; reliable end-to-end voice remains in development.

Available

Shared installations

Owner-issued invitations and installation-wide system/custom roles are implemented. Room and device permission scopes remain planned.

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

Calendar & Lounge

Local Calendar CRUD, read-only Google Calendar display, Spotify Connect controls and a visible YouTube link player are implemented. Spotify Web receiver acceptance remains open.

Available

Installer v1

Not yet. Installer v1 has an implemented fresh-install boundary, but its checked-in manifest contains no installable artifacts. Signed release acceptance, certificates, backup/restore verification and a clean Raspberry Pi rehearsal remain open.

In development

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 Installer v1

    Prove signed artifacts, fresh owner setup, certificates and recovery on a clean Raspberry Pi before a pilot release.

  2. 02In development

    Validate everyday reliability

    Complete repeatable voice and Home Assistant hardware acceptance, then expand automation and scoped household permissions.

  3. 03Planned

    Extend deliberately

    Mobile, Matter/Thread and versioned plugin contracts remain planned. Prove official plugins before any 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

Explore what comes next

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