subaud · the AIDLC stack

An AI development stack
your developers own

A self-owned toolchain for the whole AI Development Life Cycle — set up the machine, shape the spec, coordinate fleets of agents, and react to real events. It lets a small team ship like a big one. Any model, your own tools, your data on your disk.

Independence by design

Beholden to no one

Every layer is swappable and self-owned. Nothing here depends on a single company staying friendly, online, or affordable — the sovereignty a national developer base actually needs.

🧭
Your harness, not theirsBuilt on pi plus your own .tools — not tied to any vendor’s coding agent. Execution stays on your backend.
🔌
Any modelRuns through an OpenAI-compatible layer — OpenRouter, DashScope/Qwen, open models. swap the model, ship the same product.
🏠
Local-firstEach tool runs on the machine, source-available, and never phones home — SQLite on disk, unix-socket transport.
🔐
Your data, your diskTool state and history live in local files on machines you control — not locked inside a vendor’s cloud.
The stack

One toolchain, the whole lifecycle

Six local-first tools for how developers actually build with AI today — enough that one developer can ship what used to take a team.

Provision
kemptready any machine
Shape
galleytighten the spec
Build
mustercoordinate agents
Operate
channels · hailreact & supervise
muster · build

Run a fleet of agents at once

A developer can only watch one agent at a time — but real work spans many files, services and repos. muster is a local bus where agent sessions register, hand each other tasks, and report back. A coordinator dispatches parallel work and collects the results without you relaying anything. Any agent that speaks MCP can join.

galley · shape

Shape specs and docs with an agent

AI projects live or die on the spec. galley opens a Markdown or HTML file in the browser: you mark passages, leave instructions, press Revise, and see exactly what the agent changed — round after round, with full history and the human steering the artifact directly.

channels · operate

Wake agents on real events

Agents sit idle waiting for a prompt while CI fails, webhooks fire and tests break. channels pushes an external event into a running session and starts a turn — an idle agent woken by the world, not by a human typing.

kempt · provision

Reproduce any machine in one command

Environment drift and setup toil quietly kill velocity, and onboarding a new developer can take days. One readable manifest describes the machine; kempt shows exactly what it would change, then converges any machine to it — local-first, no surprises.

Why it matters for Nigeria

Give Nigeria’s developers a self-owned, local-first AIDLC stack and a small team ships like a big one — coordinating fleets of agents, on models you choose, with the harness, tools and code on machines you control. This is the difference between renting AI capability from abroad and owning it at home.

See where it starts — a real business, digitized.
Next →  Nutshell
×