Skip to content

Ethereal Forge · First tool offering

The keel your AI projects are missing.

AI projects drift. Agents build fast — but specs, code, and status sprawl out of sync, and “done” stops meaning done. Keel is the delivery system that keeps the build anchored to the plan.

How it works

Five verbs, in order

Keel is complexity-gated: trivial work skips the ceremony. But nothing — nothing — is done without verification.

  1. Frame

    Say what you're building and why. The frame is the boundary every later decision gets checked against.

  2. Spec

    Turn intent into a spec an agent can't misread — one unit of work at a time, small enough to verify.

  3. Build

    Agents build to the spec, not to their own momentum.

  4. Verify

    Every unit closes with a verification receipt. No receipt, no done.

  5. Drift

    Compare what exists to what was promised, and catch the gap before it compounds.

The proof

If there’s no receipt, it’s not done

Every unit of work closes the same way: spec, commit, test, receipt — and every receipt is chained to the one before it, so the delivery record can’t be quietly rewritten.

Who it’s for

Built for work you have to stand behind

Teams shipping with AI agents

You move fast because agents do the building. Keel makes sure speed doesn't quietly trade away correctness — every unit of work is verified before it counts.

Founders whose codebase outran the plan

The agents built more than anyone wrote down, and now nobody can say what's actually done. Keel is the rescue: it re-anchors the project to a plan and attests to delivery outcomes — not vibes.

Agencies that must prove delivery

Your clients don't want status updates, they want evidence. Keel gives you receipts for every unit shipped — a delivery record you can hand over instead of asking to be trusted.

Put a keel under your next build

Whether you’re starting clean or rescuing a project that ran ahead of its plan — tell us where the drift hurts.

Request early access