Kevin, the platform core

Infrastructure · Layer 1

"Does the hard stuff nobody sees."

What Kevin does

Kevin is the Python daemon at the center. It serves the web app and the API, loads plugins, and runs the services the other products depend on.

One daemon, many products

A single generic codebase serves every product. Domain meaning, such as field names, prompts and labels, comes from config, not code.

HTTP API and live events

A FastAPI-style HTTP API for requests, and server-sent events so the browser sees changes as they happen.

Service manager

A tray-managed service manager starts services in order and protects against crash loops.

Local and cloud models

Runs local models through Ollama on workstations with a GPU, and sends work to cloud providers when that's cheaper or more capable.

Self-healing versions

Every service publishes an immutable build version and a heartbeat. When versions drift apart, the stale service restarts itself.

SQLite by default

No database server to install. Postgres, ClickHouse and InfluxDB are optional backends for industrial scale.

How it works

It's a daemon reading config.

  1. You start the daemon from the tray.
  2. It reads config for services, ports and plugins.
  3. Services start in order and announce themselves on the bus.
  4. The web app and API serve requests, and model calls go out through the carousel.

Where it fits in the four layers

1 Infrastructure & roles Vera, Grant, the bus, the device registry
2 Data pipeline & state Flo, DynaRAG, the carousel
3 Reasoning & inference Rick, Annie, Max, Hank
4 UI & collaboration Marco, Noted, Norm, the graph

Kevin is layer 1. It provides the roles and plumbing that the other layers publish to and subscribe from, so they never have to call each other.