Keel is the reference implementation of EIOS, the Entity Information Operating System: a durable information spine that preserves originals, records events, maintains living knowledge, and serves governed views to humans and AI agents.
Part of the Entity Core open initiative.
Reference architecture v1.0 — draft. A first runnable contract service, v0 (the Minimum Viable Keel contract, implemented locally and tested, not deployed), is in service/. This repository holds the reference architecture: component roles, storage conventions, service contract v1 (draft), integrity checks, intake, operations and deployment model, implementing EIOS spec v1.4. The first proof instance will be built against it, and its evidence will revise it.
| Profile | Description |
|---|---|
| Keel Managed | Entity information management as a service: infrastructure, backups, updates, connectors, security, and operations managed for the entity, with mandatory export, deletion, and takeover rights. |
| Keel Self-Hosted | A portable VM/server distribution runnable on any cloud provider, a company server, or on-premise hardware. Same information model, same agent-facing service contract. |
The service interface is provider-neutral before it is implementation-specific: switching profiles or providers changes base URLs and credentials, not the architecture.
- Reference architecture — component roles, storage conventions, principals and bootstrap, service contract v1 (draft), integrity checks, intake and authority transition, exports, operations, communication layer, deployment model, Minimum Viable Keel, roadmap
© 2026 Valto Loikkanen. Code, schemas, and tooling in this repository: Apache License 2.0. Documentation: CC BY 4.0 with attribution to Valto Loikkanen / Entity Core.
Contact: valto@valtoai.com