LOCAL-FIRST HOME OPERATING SYSTEM

Your home. One system.
Your control.

A Local-First Home Operating System for your devices, rooms and digital services. Keep everyday control on your own infrastructure, with intelligence as an option.

Explore Kyrion View on GitHub

Working development prototype. General automations and a supported consumer installation are still in development or planned.

Local by design

Intelligence is optional

Your home stays yours

LESS SWITCHING, MORE DOING

Less switching. More control.

Bring selected devices and services into one understandable place. Start with the controls that work today.

Rooms & lighting

Organise rooms and control selected Nanoleaf, Zigbee and Bluetooth lights.

Calendar & media

Local events, read-only Google Calendar, Spotify Connect and YouTube links.

People & access

Invitations, installation-wide roles and a shared, Core-controlled action path.

HOW KYRION WORKS

One platform between you and your home.

You decide what should happen. Velora and other interfaces help you express it. Kyrion Core understands the request, checks it and connects it to your devices and services.

You
Your request, your decision.
Web & optional voice
Use the Web interface today. Velora voice reliability is still being validated.
Web available / Voice experimental
Kyrion Core
Checks identity, permissions and action policy, then records execution results.
Validate · Authorise · Execute
Cloud when you need it.Optional services, separate from the local foundation.
Your home
Selected lighting, sensors and media through bounded integrations.
NanoleafZigbeeSpotifyHome Assistant

Local functions remain independent wherever practical. Individual integration availability is limited in the prototype and shown separately.

A HOME THAT WORKS TOGETHER

A practical foundation. Built around your home.

One coherent layer above the devices and services you already use. A foundation for everyday control, with room to grow.

Local-first architecture

Core control and data stay on your infrastructure wherever practical. External services are optional and visible.

Unified device control

Rooms, lights and device state in one place. Working Nanoleaf, Zigbee and bounded Bluetooth control paths.

Privacy & ownership

Core owns permissions and validates actions. Your personal data is never an unrestricted instruction source.

Extensible integrations

Stable capabilities connect different ecosystems. Home Assistant import is read-only; a public plugin system is planned.

A home you can share

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

Clarity when things change

Device availability, service health and an action inspector help explain what happened—and why.

Explore the platform

Velora just welcomed you.

Experimental

MEET VELORA

Velora, an assistant taking shape.

Velora is the developing intelligent voice interface for Kyrion. Local chat, “Hey Velora” wake detection, transcription and bounded device commands exist. Repeatable voice reliability and natural dialogue still need validation; AI remains optional.

Intelligence proposes. Core decides.

LOCAL FIRST. CLOUD WHEN YOU WANT IT.

Your infrastructure. Your choice of connections.

Kyrion itself does not depend on cloud accounts. Devices, rooms, central settings and local functions stay in your own system wherever practical.

YOUR SYSTEM

The foundation stays local

Kyrion is built for local processing and storage. A traditional server or NAS is not required – a suitable local computer is enough for the relevant use case.

OPTIONAL CONNECTION

Services are added when you need them

Spotify uses an explicitly connected account. Google Calendar display is read-only; YouTube loads a visible link player without an account connection. These services require their providers and network access.

CONNECTIONS WITH CLEAR BOUNDARIES

Every action has a boundary.

Core enforces installation-wide roles and validates device actions. Optional AI proposes requests through the same controlled path. Room and device permission scopes remain planned.

Core owns authorisation and execution

FOR THE THINGS YOU ALREADY USE

Built to connect systems.

Implemented means present in the development prototype, not a consumer release. Hardware evidence covers selected devices; it does not establish compatibility with every device in an ecosystem.

Standards

Zigbee (Zigbee2MQTT)Available

Bluetooth (MELK-OA20)Experimental

Matter / ThreadPlanned

Device ecosystems

NanoleafAvailable

Philips Hue (Zigbee)Available

Aqara / myStromPlanned

Services

Spotify ConnectAvailable

Home Assistant (read-only)Experimental

YouTube (link player)Available

Google Calendar (read-only)Available

JellyfinPlanned

Home Assistant import awaits physical verification. Spotify Web controls and repeatable voice reliability still have acceptance gates.

GETTING STARTED

Do you need your own server?

Core, Web and PostgreSQL need a configured local host. Local AI and speech add separate runtime and hardware requirements.

Can I install Kyrion with one command?+

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.

What already runs on local hardware?+

Core, Web and PostgreSQL form the local platform. A Raspberry Pi gateway supports selected lighting and voice paths. Local AI and speech use separately configured providers; a Pi-only AI setup is not established.

Where can I find setup instructions?+

The repository contains developer startup instructions and the installer implementation status. These are technical setup documents; a supported consumer installation is still in development.

Developer startup

BUILT IN THE OPEN, STEP BY STEP

Independent by design. Transparent in development.

Current work prepares a fresh Installer v1 release, following security hardening, installation-wide roles and local Calendar support. Voice and Home Assistant hardware acceptance remain separate open gates.

In development

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

Currently in development

Explore what comes next