Resources

Learn how Kevin works

Short explainers through full technical deep-dives. Start anywhere. The first three cards are all you need.

What is Kevin?

Three ideas.
01

A family of services, each with one job

Walt orchestrates, Mona monitors, Max runs on hardware, Vera answers questions about your documents, and so on. Each service owns one responsibility, so you can run only the ones you need.

02

They share a message bus

Services publish and subscribe on a shared bus: MQTT between machines and devices, plus a latest-value cache. When a sensor fires or a command arrives, the services that care hear about it right away, with no polling.

03

You send one request. It routes itself.

Send a message to any entry point: HTTP, MQTT, or straight to a device over BLE or serial. The routing layer works out which services need to act, so you don't wire them together by hand.

The family

Play any video, or see the full family
Orchestrator
Walt
Assigns work and keeps the other services coordinated, driven by config rather than code.
Web interface and monitoring
Mona
The React web app the daemon serves: dashboards, health checks and alerts in one place.
Core platform
Kevin
The Python daemon, API and service manager that every other piece runs on.
Document knowledge base
Vera
Indexes your documents on your own machine and answers questions about them with citations.
Nightly research
Norm
Reads arXiv, Semantic Scholar and Google Scholar overnight and files what is new for Vera.
Edge firmware
Max
Firmware for ESP32-S3 boards with LoRa radios, updated over the air.
Reactive keystore
Hank
A key-value store that tells subscribers when a value changes.
Device rules
Chip
Say what you want a device to do. Chip turns it into a rule the device keeps running.
Message bus
Lattice
Subject-based messaging with a last-value cache and history.
Operations and authoring
Marco
The browser-based surface for running the platform and writing in it.
Authentication and entitlements
Grant
Decides who can do what, and names the rule behind every denial.
RAG router
Annie
Sends each question to the right knowledge collection and the lowest-cost model, with citations.
Pattern engine
RAT
Recursive Associative Tensor: the math Holon runs on, for finding patterns in raw data.
Self-improving loop
Rick
Runs nightly knowledge-graphing and pattern-extraction passes over the platform's own knowledge.

Platform diagrams

Tap any diagram to expand
Kevin Family
The Kevin Family
Every service at a glance
Deployment
Deployment topology
Where everything lives: edge server and local machines
Firmware
Firmware: Max
ESP32-S3 HAL → Mx → App layers
MQTT
The message bus
MQTT topics, publishers, subscribers
Hank
Hank: reactive keystore
Write + subscribe paths
Dashboard
Chip: dashboard
React and MQTT over WebSocket
Knowledge
Knowledge engine
RAG router, vector store, Vera, Norm
Websites
Websites layer
DNS → Caddy → backend routing
▶
System data flows (animated)
Marco → Daemon → Carousel → Worker → Dashboard
▶
Firmware data flows (animated)
Max (ESP32-S3) — Boot, Tasks, Telemetry
▶
End-to-end data flows (animated)
Device → MQTT → Daemon → Carousel → Worker → Result

Listen and watch

AI-generated explainers

No explainers published yet. Check back soon.

Architecture

Full technical reference