KEEL · DYNO SYSTEMS · ADVISORY

Dynamic systems.
A solid core.

DynoKore Keel is the project record for software built by coding agents: requirements, decisions and tasks kept as linked records in a database, so every agent works from short, accurate context. We build our own enterprise systems with it, starting with DynoInvoice.

Become a Keel design partner Read the DynoInvoice case
Singapore-based. Delivering for clients worldwide.
KeelPRODUCT The project record for software built by coding agents. Open to design partners. DynoInvoiceBUILT WITH KEEL E-invoicing and GST compliance for Singapore, built by agents in the open. AdvisoryOUR METHOD How we run coding agents, brought to your team.
WHAT WE DO

One engine. The systems it builds. The method behind it.

01 · PLATFORM

Keel

Spec-driven development for coding agents. Requirements, acceptance criteria, decisions and tasks are versioned records with typed links. Each task gets a short context built from its links, changed decisions reach the work linked to them, and tasks are marked done from the merged change and CI. Works with your agents through MCP and the command line.

Apply for early access →
02 · SYSTEMS

Dyno systems

Enterprise systems built with Keel. DynoInvoice is the first, built in the open; more will follow. Each traces from requirement to merged change, and you can inspect it.

See DynoInvoice →
03 · ADVISORY

Agent engineering advisory

Keel doesn't prescribe how your agents work. Our way of running them — agent roles, review, who answers which questions, the gates — is something we teach, from people who run it on their own products every day.

Discuss your team →
HOW KEEL WORKS

Every change has a reason on record.

What an issue tracker did for teams of people, Keel does for coding agents: it keeps what each task must satisfy, and the links between them, in one record.

  1. Source passage
  2. Requirement
  3. Acceptance criteria & decisions
  4. Task + context
  5. Merged change
  6. CI evidence
  7. Done

Linked, not copied

Each decision lives in one record, and the requirements, tasks and modules it governs link to it. When it changes, the links below it are marked for review.

Short, accurate context

An agent reads the records its task links to, with the rules it must follow always included, instead of the whole spec or whatever fits in the prompt.

Done on evidence

A task is offered only when it's ready, and the server marks it done from the merged change and its CI verdict. Every change keeps its link back to why it exists.

PROOF, IN THE OPEN

DynoInvoice: built by agents, recorded in Keel, source on GitHub.

Read the code. Follow a commit back to its task, requirement and review. See what people decided and what agents did.

Read the case study View on GitHub
859 live requirements in Keel
602 tasks done
687 merge requests merged
38% of merge requests sent back by an independent reviewer at least once
From the Keel record and the public repository, 26 October 2026 (00:00 SGT). Live records only.
DYNO SYSTEMS

One system being built in the open.

DynoInvoice is the first system we’re building with Keel. More will follow; if you need a system built this way, talk to us.

DynoInvoiceE-invoicing & GST compliance, SingaporeOpen case study
AGENT ENGINEERING ADVISORY

Our method, from our own mistakes.

Everything we teach, we learned building our own products with agents — what to gate, what to hand to people, and what it really costs.

AssessmentWhere agents fit in your current delivery, and what has to be in place first.
WorkshopHands-on sessions on traceable requirements, test-first gates and agent roles.
Embedded pilotWe run one real project alongside your team until it can run the next one alone.

Have a system to build — or a team to bring up to speed?

A 30-minute conversation. Your landscape, our honest view.

Book a call [email protected]