keel · the backbone
The steady spine
everything stands on.
Always on, quietly routing every model call through a single model-agnostic streaming gateway — so the model underneath can change without anything above it noticing.
steady head · ribs dock on · swappable base
The part that doesn't sleep
01Always on
Keel is the part that doesn't sleep. It runs the standing work and keeps the line open, so the rest of the workshop can assume the backbone is simply there.
The head of the keel carries a single always-on light — a steady glow, deliberately not a blinking status blip. Steadiness is the whole message.
You notice a keel only when it's gone. This one is built so you never have to.
One path for every call
02One gateway, any model
Every model call flows through the same model-agnostic streaming gateway. The apps calling in speak to one steady address — they never have to know which model is answering today.
The model on the other side is swappable: swap it, upgrade it, or route around it. Picking up more depth becomes a routing choice, not a rebuild.
one address in · the model underneath can change, hosted or local · nothing above has to notice
The boring, dependable layer
03Steady by design
The point of a keel is that you don't think about it. It's built to be the boring, dependable layer — the thing you notice only when it's missing.
Which is exactly why it's engineered not to be. Steadiness isn't the exciting part of the workshop. It's the part that lets every other part be exciting.
A steady line reads as nothing at all. The gap is the only time a backbone gets noticed — so keel is built to never leave one.