The architecture is the website.

Kevin is self-hosted AI infrastructure: one endpoint in front of every model you use, a per-request cost ledger on your own disk, and a hard spend cap that stops a runaway loop before it becomes an invoice.

Rather than describe that in prose, this site shows you the drawings the platform generates about itself. 55 of 55 subsystems are rendered below, grouped by the part of the family that owns them.

Each diagram is rebuilt from the source files it watches, and every page names those files and the commit it was rendered from. If the code moves and the picture doesn't, that is a visible bug rather than stale marketing copy.

Core

The daemon, the bus it speaks on, how work is distributed, what repairs it, and where its credentials live.

LatticeThe nervous system — every subject on the bus and who listens.EventBus InternalsMQTT Topic Topology
HolonEvery calculation, render, and handoff — the unit of work itself.Holon Queue PipelineMailbox & DispatchSwarm Dispatch Manager
HeimdallThe watchkeeper — version drift caught and healed.VersionVerifier + AutoHealer
HankThe keystore — every secret fetched at runtime, never stored in code.Reactive Keystore

AI & inference

Where model calls go, what they cost, and what knowledge they are grounded in.

WaltThe orchestrator — one endpoint in front of every model, metered.AI Dispatch CascadeAI Proxy + Savings LedgerLLM Fabric ProxyStripe → Queue → ClickHouse
RickThe reasoning layer — agent loops and how they are controlled.Agent Control FrameworkAutonomous Claude LoopJob Submit / Execute / Result
AnnieKnowledge routing — what gets retrieved before a model answers.Ingestion + Knowledge InfrastructureRAG System

Surfaces

The screens a person actually touches.

MarcoThe desktop — the operator surface and its agent bridge.70+ ToolsElectron + MQTTMarco Agent BridgeMarco VibeContextStore
MonaObservability — she sees the fleet before anyone else does.Fleet Control (Groups + Devices)

Products

Things built on the platform that a customer buys or runs.

SibylThe coding fleet — sessions on demand, isolated per project.Bootstrap, Session, BillingSibyl Client DaemonSibyl Site + Oracle APIsibyl.iiiai.us Production
SterlingEnsembles and options analysis, driven by config packs.Options Data SessionOptions Data Spec
SaulMeeting and document intelligence — mail, legal, the paper trail.Email AutomationLegal Assistant
FloDiscovery — finding what is out there before it matters.Service Discovery
RhoThe character layer — persona as a first-class object.Character Interaction
MinnieThe installer and the small daemon that follows it.AI Proxy ServiceInstaller and Entry Point

Edge

Firmware on real hardware, how it gets there, and how plain language becomes a rule that keeps running with the network gone.

MaxHardware and firmware — ESP32 targets and the OTA path.Firmware Mx ArchitectureOTA Firmware Flow
ChipPlain language becomes a device rule that runs with no model and no network.Natural Language to Device Rules

Infrastructure

The hosts, the edge proxy, and who is allowed through it.

VeraThe hosts — deployment, containers, the public edge.Ansible Fleet ProvisioningDocker InfrastructureLinode Prod Nodenginx Public Edge
GrantAuthorization — who may do what, decided in one place.Authorization Decision

Governance

The rules the platform holds itself to, and the evidence it keeps.

TrixieRules and compliance — specs, backlog, and the gates between them.Backlog / KAN TicketsKnowledge / Content SystemOpenSpec Workflow
NormThe nightly research engine — intelligence gathered while you sleep.Fleet Intel Pipeline
StandardsS001–S007 — the invariants every service is held to.Build VersioningBus-Driven ArchitectureConfig is OpinionMQTT / Errors / RolesPort Management