Dekku for Scrum teams and engineering managers
See every change by stage, who it waits for and what it costs. Changes reach develop one at a time.
Dekku is a self-hosted delivery board for teams that build with AI coding agents. Your Scrum team keeps its events and its Definition of Done; agents write the code inside them.
Delivery gate · queue by readiness
Waiting for people
Dekku does not replace Scrum. It gives each event the facts it usually has to collect by hand.
Ideas become cases through an exploration. The product owner approves each spec and its acceptance criteria.
Each sprint item is one case with its own branch, budget and Jira item.
The Flow and Blockers views show what waits for whom, without collecting updates by hand.
Show the acceptance evidence per criterion, on the build that merged.
Cost by stage and first run against rework show where the agents struggle and where specs were thin.
Your Definition of Done sets the quality standards for every change. Dekku runs the configured checks and enforces required approvals; your team ensures they cover those standards.
Saved views over the same record the team works in: the flow, the queue, the blockers and the cost.
Changes by stage and by who holds them, with work in progress and waiting time per stage.
If develop moves, the candidate and its evidence are rebuilt
One change of a project passes the final rebuild, last evidence and merge at a time. The others queue by readiness and see their place.
Everything that stops a change, with the person who can unblock it. A broken test setup goes to the admin, not back to the agent.
First runRework
First runs against rework, per stage, inside a budget per change and one for the whole queue.
In your cloud or your data centre. Secrets stay on the server, runners scale with the queue, and agents never receive your Git credentials or model-provider API keys.
dekku/ # workloads in your cluster proxy, console # behind your ingress and TLS server # process, LLM gateway, git, integrations postgres # the record, or your managed instance runners # agents and checks, rootless, scaled object storage # evidence and artifacts, S3-compatible
Connects to
Claude Code implements a change for the developer who runs it. Dekku runs Claude Code in isolated runners and coordinates the change for the whole team. The approved spec, the approved design, the required checks and the acceptance are each on record.
Each change is one Jira item. Dekku keeps it updated and marks it Done when the approved, checked change is merged.
Acceptance criteria describe one change. Your Definition of Done sets the quality standards for every change. Dekku runs the configured checks and enforces required approvals; your team ensures they cover those standards.
A reviewer requests changes with a note, and the agent's next attempt starts from it. A failed check blocks progress until its relevant inputs change and the check passes.
They review the code the agents wrote, keep the tests and checks meaningful and fix the project's configuration when it breaks. Agents write the code; people decide.
No. Each change has a budget, and so does the queue as a whole. Going over pauses the change or the queue until a person decides.
We take one item from your backlog through the six stages with you. You see what each person decides and what Dekku does in between.
A walkthrough with the people who build Dekku. We keep your answers and the country you write from to prepare the demo; Cloudflare Turnstile filters spam.
