apache-2.0 · public on npmnpx @kontourai/flow-agents init

Nothing here is gated.

The engine is free today. The conversation is about your workflow.

An agent hands you forty pages of analysis and a green checkmark. You have twenty minutes and no way to tell which parts were actually checked. That's the moment Kontour is built for — and you don't need us to start. Install the engine into the coding agent you already run and it gates the work on evidence instead of promises, today, for nothing.

The separate thing on offer here is hands-on. Bring one process you actually run and tell us what "done" means for it; we encode that as checks the work has to pass, so what comes out carries evidence you can re-check yourself. You judge it on outcomes you can verify, not a story you take on faith.

Want the occasional build update?

One email when there's something real to show — no pitch sequence. We keep your address, the page you signed up from, the date, the browser string the request carried, and the page that referred you. Ask us to delete it any time at [email protected]. The full list, and the code that writes it →

Ready to talk instead? [email protected]· follow on GitHub

the free path, in one command

# run it inside the repo you want gated

$ npx @kontourai/flow-agents init

Installed Claude Code bundle into ~/your-repo

Flow Agents install summary:

✓ Runtime: claude-code (auto-detected)

✓ Destination: ~/your-repo

✓ Telemetry sink: local-files

- Console: local-only

No key, no waitlist, no email required. Gates block on Claude Code and Codex; everywhere else the engine advises rather than stops the work. The two-command tour — install, then validate one of our own receipts yourself — is on the developers page →

What you'd be signing up for

One concrete workflow is enough.

A useful first note says what the work is, who needs to trust it, what evidence exists today, and what currently gets missed, stale, skipped, or buried in chat. No procurement packet or polished brief required — and you don't need to send us anything confidential to start. Describe the shape of the work, and if it turns specific enough to need paperwork, we'll sort that out before you send anything sensitive.

What you bringOne process you already run, and a straight answer to "what does done mean here?" Plus enough of your time to explain how the work actually runs, rather than how the diagram says it runs. We'll scope that with you before you commit to anything.
What you getYour definition of done encoded as gates the work has to pass, and output carrying evidence you can re-check without taking our word for it. Gates refuse or escalate to you — they never silently proceed. You keep what we build: the engine and both kits are Apache-2.0, so none of it depends on us still being here. We haven't set pricing for this work — terms are part of the first conversation, not a rate card we're holding back.
What happens after you send itA person reads it — there's no queue, no sequence, and nobody whose job is to keep you warm. The first conversation is a short call about fit and one concrete example, not a demo. If it isn't a fit we'll say so.

Start with the shape of the problem

AI-assisted work

Design partner

You have a real process — intake, review, research, delivery — where the result matters more than the effort. We build the gated version with you: your acceptance criteria encoded, every output carrying evidence you can check.

Start this thread →[email protected]

Claims and evidence

Product builder

You are building an app that makes claims and needs to show source, freshness, uncertainty, and gaps.

Start this thread →[email protected]

Gates and readiness

Agent workflow team

You are shipping with coding agents or internal tools and want durable plans, review, verification, and release evidence.

Start this thread →[email protected]

The same shape turns up in legal intake and conflict checks, insurance claims information gathering, customer-service follow-through, research synthesis, and investment decisioning: work with a definition of done where the only proof it was met is somebody's word. None of those are clients — they're desks where the pattern is easy to recognize.

The one we run on ourselves

Agent-built code that earns its merge.

Kontour is built through its own gates, and the evidence is public rather than described: every bundle on the receipts page is downloadable and re-validatable on your machine, without trusting us or running anything of ours to check it.

Check the receipts →