For software architects and IT leads

Keep AI-generated changes under technical control.

Require design approval, automated checks and code review before a change advances. Dekku records each decision and its check results.

Book a demoSee how it works
CRM-07142 06 accept · waiting for youHuman approval at 4 of 6 stagesBudget reserved before every model callOne branch and one pull request per change

Implementation starts only after the required design approval.

Find your role

Fig. 1 — The console's inbox: the design waiting for your approval, with its checks and its cost.

More AI-generated code means more work to verify.

AI agents can produce changes quickly. Teams still need to agree on requirements, review technical decisions, check the implementation and verify the result. Under deadline pressure, keeping those steps consistent becomes harder.

Dekku connects them in one workflow. Each change carries its specification, its check results and its approval history, so your team can see what is ready and what still needs attention.

Design review and acceptance stay required, even under deadline pressure.

One workflow connecting requirements, code and decisions.

SpecificationAn approved specification gives agents and reviewers a shared reference.
ChecksA failed check holds the change until something it reads changes and the check passes.
Acceptance evidenceTests and screenshots are linked to each acceptance criterion.
Approval historyEvery approval names the person, the stage and the version they reviewed.
Changed requirementsChanges to the specification or its acceptance criteria require approval again.

Six stages. Who does what, and who decides.

  1. 01

    Spec

    Define the expected behavior and acceptance criteria. The Product Owner approves the specification.

  2. 02

    Design

    Review the technical approach. The architect approves the design.

  3. 03

    Build

    AI agents write the code and tests against the approved specification and design.

  4. 04

    Integrate

    Your test suite and the checks you require run on the change. A failed check blocks progress until its relevant inputs change and the check passes.

  5. 05

    Review

    A developer reviews the code and approves it or requests changes.

  6. 06

    Accept

    The Product Owner reviews the result and its evidence against the agreed criteria.

Sent back at any stage, a change returns with the reviewer's note, and the next attempt starts from it.

Review the design. Control what moves forward.

Questions teams ask first.

How does Dekku connect to our repositories and checks?

Dekku works with your Git host: one branch and one pull request per change. It runs your test suite and checks in its own runners and merges exactly the checked result into your integration branch.

What access do AI agents need?

None to your secrets. Agents work in a sandbox with the files of the change and a token for Dekku's gateway that is valid for one run. They cannot commit, push or reach your database and keys; only the server writes to the branch.

Who can approve each stage?

Your project's policy assigns each approval to a role, for example the design to the architect, and Dekku enforces it. In a one-person setup, that person holds every role.

What happens when an approved specification changes?

The earlier approval no longer counts. Dekku asks for approval of the new version before the work moves on.

Where does Dekku run?

On your infrastructure: the same Docker Compose setup on a laptop or a team server. Only four things leave it. The change's branch and pull request go to your Git host. Model requests go through Dekku's gateway with your organization's account, carrying the files a step needs. Integration messages go out without transcripts or secrets, and telemetry is metadata only.

What does the cost shown for a change include?

The model usage of each stage, counted against a budget reserved before every model call. If further work would go over the budget, the change pauses for a decision.

See how Dekku handles a change from your backlog.

Bring a backlog item to the demo. We'll walk through its specification, technical reviews, checks and acceptance, showing what each person sees and decides.

A walkthrough with the people who build Dekku.