Planned
Understand the workspace
For example, manage lighting, rooms and selected device states in a small office through a common interface. Today’s device capabilities are a starting point; business-specific access rules still need validation.
FOR BUSINESS — IN DEVELOPMENT
Devices, services and team knowledge. One shared direction.
Kyrion aims to help small businesses and teams connect their digital environment in an understandable way. This area presents the vision and early development, not a production-ready business service.
In development
Business is in development. Initial Spaces and identity capabilities are implemented and tested separately, but are not yet integrated together or validated in real operation. Complete isolation is not established. There is no offering for production multi-tenant operation, hosted team environments or guaranteed support.
Discuss a use casePossible uses for small teams
The following examples describe possible future uses, not available business features.
Planned
Connect schedules and services
For example, bring shared events and connected services into one overview. The current personal calendar and integration capabilities do not establish complete team scheduling or resource booking.
Planned
Make team knowledge easier to find
For example, search internal guides with source references. K-Data starts with personal documents. Shared knowledge, document-level access rules and their connection to Spaces still need implementation and combined validation.
Planned
Assistance with clear boundaries
For example, explain information and propose supported actions. Core remains responsible for permissions and execution. General autonomous workflows, cloud team knowledge and industry-specific acceptance are not current offerings.
Access control is a prerequisite, not a promise.
The shared prototype has installation-wide roles, custom roles and owner-issued invitations. A separate development branch adds HOME/BUSINESS Spaces, memberships, bounded invitations, email confirmation, domain verification and local owner account recovery. Automated tests cover these capabilities; combined integration and real operational acceptance remain open.
Domain verification is implemented, but has not been acceptance-tested with a real mailbox and an owned domain. Separation of data, background jobs, AI streams and knowledge access also requires combined evidence. Multiple Spaces in a running installation remain blocked. Business voice is blocked in the separate branch until the acting person can be reliably identified. Local and optional cloud processing must be explained for each use case.
What remains before business use
Integration of separate workstreams, conflict-free migrations, identity and permission review, and combined isolation tests for devices, services and documents. Operations, recovery and real model answers need evidence on the intended runtime.
Subscriptions, billing, a customer portal, managed hosting and privileged remote support are not implemented. No prices or availability dates are announced.
Explore development statusWhich use case would you like to connect?
We welcome discussion about concrete needs of small businesses and teams. An inquiry does not establish a service offering or guaranteed access.