Skip to content
kanman, the robot that does the work

kanman fixes main at 2 a.m., answers "who owns this?" at 9 and posts what you shipped on Friday. One kanman for the whole team, plus a private line for each of you.

Start the 14-day trial Log in

Team plan, no card needed

One week on team-web

Main went red at 02:14. Nobody woke up.

By breakfast it was green, with a story for the real fix. The rest of team-web's week went like this.

  1. Monday 07:52 #team-web Habit: watch main

    kanman

    Main went red at 02:14. The lockfile bump in #318 pulled in a new undici, and two integration tests now time out on keep-alive. I pinned the old version at 02:31, main is green, and the proper upgrade is a story on the board. Coffee first, then review it.

    Upgrade undici without the keep-alive timeoutsReady

    • Integration tests pass with the new version
    • No pinned version left in the lockfile
    • Keep-alive timeout stays configurable
  2. Tuesday 11:20 #team-web New habit

    Mira

    @kanman every Friday afternoon, post what we shipped this week

    Shipped this week

    When
    Fridays at 15:00
    What
    Merged work and closed stories, and why they matter
    Where
    #team-web, nothing on a quiet week
    May
    Post in Slack
  3. Wednesday 14:05 Pull request #241 Habit: review pull requests

    kanman

    Two things before this merges. The retry loop in sync/worker.ts never backs off, and the new /exports endpoint skips the role check. I reproduced both with a failing test, attached below.

    Changes requested

    • Retry loop without backoff in sync/worker.ts
    • No role check on /exports
  4. Wednesday 16:40 Personal(only you) One-off ask

    Jonas

    tell me when #412 is merged and deployed

    kanman

    On it. I’ll tell you, not the whole channel.

    kanman 18:12

    #412 merged at 17:55 and went out with the 18:05 deploy.

  5. Thursday 09:10 #team-web Mind: memory

    Priya

    first week here. who knows the billing webhooks?

    kanman

    Mira wrote most of webhooks/billing.ts in March, and Theo changed the retries last week in #388. I keep a short page on how billing events flow: Mind, Memory, Billing events. Shall I ask Mira for 20 minutes this week?

  6. Friday 15:00 #team-web Habit: shipped this week

    kanman

    Shipped this week: CSV export for invoices (#402), search on large projects three times faster (#407), and Monday’s undici upgrade. One question waits on Mira: should archived projects show up in search? Otherwise a quiet week. Suspiciously quiet.

Example team, invented. What kanman does in it, it does in the app today.

The whole product

Mind, Habits, Stories, Connections.

Four tabs. That's the whole product. Everything else happens in chat.

Mind

Knows who wrote billing.ts.

The board, the code, the conventions and who owns what. Ask who knows the webhooks and you get a name, the pull request and a page on how billing events flow.

Read the docs: Mind (opens in a new tab)

Habits

Does the boring part. Every time.

Reviews every pull request, watches main, sorts 40 dependency bumps into waves you approve with one tap. One sentence in chat starts a new habit: "every Friday, post what we shipped." Fridays are handled.

Read the docs: Habits (opens in a new tab)

Stories

"Done" comes with receipts.

Every story has acceptance criteria, and every change runs your CI plus an independent review against them before it merges. When a card says done, something checked it. On Fridays, Stories shows what shipped and why it mattered.

Read the docs: Stories (opens in a new tab)

Connections

Jira gets "ask first". GitHub gets the keys.

GitHub, GitLab, Jira, Slack, Microsoft Teams and the rest of your stack. Per system you pick off, ask first or automatic, and kanman enforces it in code, not by being polite.

Read the docs: Connections (opens in a new tab)

Team chat and Personal

The team gets a teammate. You get a private line.

The team chat gets the release notes. Your private line gets "your PR has been waiting three days".

Team chat

Shared with the whole team.

  • Picks up the team's stories and reviews its pull requests
  • Remembers what the team decided, with sources
  • Answers anyone on the team, in the app, Slack or Microsoft Teams

Personal

Just you and kanman.

  • What waits on you across all your teams, one tap each
  • Your one-off asks, like "ping me when #412 deploys"
  • How you like to work: short updates, focus Fridays, your language

Nothing you tell kanman in Personal is visible to anyone else.

Personal and For you in the docs (opens in a new tab)

Watch it work

One sentence in. One merged pull request out.

Two minutes in the real app, proof attached.

A requirement from finance for the Sandbox Team is typed into the general conversation. kanman offers to continue in the team's chat, the conversation moves there beside the team's board, and kanman drafts three stories with acceptance criteria, which are approved and written to the tracker. The first story is moved to Ready on the board and kanman starts planning. kanman asks to approve the plan, the plan is approved in the conversation, and the run passes every check on a clean checkout. The pull request is merged, the story moves to Done with its criteria, tests and cost, and the weekly report sums up the week.

Under your rules

It can't talk its way past the rules. We tried.

The limits live in code, your code host and your runner. A prompt doesn't decide what it may merge.

  • Proof before merge

    Every change passes your own CI and a review by a separate session that did not write it. The reviewer reruns the bug or the acceptance check before and after the change. The host that merges checks both.

  • Limits it can't sweet-talk

    What kanman may touch, spend and merge is enforced outside the model, by kanman, your code host and your runner.

  • Claude Code or Codex does the typing

    The model you already trust writes the code. Your tracker, code host and chat stay exactly where they are.

  • Frankfurt sandboxes, or your runner

    Sandboxes run in Frankfurt and your data is stored in the EU. With your own runner, code runs inside your network.

How kanman keeps your code safe

Pricing

Priced per AI team. Not per seat.

Start free on your own machine. Try the Team plan for 14 days, no card needed.

Local

The kanman board and the kanman MCP in your own Claude Code or Codex. Your machine does the work.

€0per AI team
  • The kanman board for your team's stories, decisions and history
  • The kanman MCP for Claude Code or Codex on your machine
  • Cloud runs, runners and the independent review start with Starter
Start free

Starter

kanman works your stories under your rules and proves every change.

€99per AI team / month

Billed monthly, no minimum term. Cancel to the end of any billing month.

  • Cloud sandboxes in Frankfurt or your own runner, including runner-only mode
  • One tracker - GitHub Issues, Jira or GitLab
  • Your CI plus an independent reviewer on every change, enforced at merge
  • Decisions and audit log
  • 2 runs in parallel
Start the 14-day trial

14 days free

Team

kanman as a full teammate, in your channels and on call.

€249per AI team / month

Billed monthly, no minimum term. Cancel to the end of any billing month.

  • Everything in Starter
  • Context connectors for your docs, wikis, Confluence, Notion and SharePoint
  • Maintenance scans and on-call
  • Slack and Microsoft Teams
  • 5 runs in parallel
  • Up to 15 people per team. Larger team? Talk to us.
Start the 14-day trial

Volume pricing for Team

The number of Team teams in your workspace sets the price of every one of them.

Team teams in your workspacePrice per team and month
1 to 4 €249
5 to 9 €224.10 10% off
10 or more €199.20 20% off

Enterprise agreement

One agreement for your whole workspace, on top of your teams' plans.

  • SSO and SCIM
  • Audit log kept for 3 years
  • Data processing agreement
  • SLA
  • Pay by invoice
  • A named contact
  • Self-hosted control plane on request
Coming soon · Talk to us

14 days of the Team plan, free

Every new team gets the Team plan for 14 days, without a card. When the trial ends, cloud runs pause until you pick a plan. Your board and the Local plan keep working.

Start the 14-day trial

Guided onboarding

Want us to set kanman up with your team? Guided onboarding is available on request, with any paid plan, priced for your setup.

Ask about onboarding

Model usage runs on your own keys (Anthropic, OpenAI, Azure OpenAI or Amazon Bedrock), or is passed through at provider cost plus 15%. No per-seat pricing.

Prices are net. No VAT is added, as kanman is a small business under section 19 UStG.

FAQ

What leads ask before day one

Short answers. Each one links to the long version.

Something missing? Email [email protected]
How is this different from assigning issues to Copilot, Claude or Codex in GitHub or Linear?
Those tools turn an issue into a pull request. kanman is the teammate around that: it turns requests into stories with acceptance criteria, keeps habits like reviews and watching main, follows the limits you set, and has every change checked by your CI and by a reviewer that did not write it before it merges. The coding itself still runs on Claude Code or Codex. Read the docs (opens in a new tab)
What does working with kanman look like day to day?
You talk to it: in your team's chat in the app, in Slack or in Microsoft Teams, or privately in Personal. Ask for work and it drafts the stories. Ask for something every week and it makes it a habit. It tells you when something is ready and asks only when a decision needs you. Read the docs (opens in a new tab)
Do we have to leave Jira or GitHub?
No. kanman works in your tracker, whether that is GitHub Issues, Jira or GitLab. Stories, status changes and pull requests show up where your team already looks. No tracker yet? A team can keep its stories on its own kanman board and connect a tracker later. Read the docs (opens in a new tab)
Which models does it use? Can we use our own contracts?
The coding runs through Claude Code or Codex. You can bring your own keys for Anthropic, OpenAI, Azure OpenAI or AWS Bedrock, or your company's OpenAI-compatible AI gateway, or let kanman pass usage through at cost plus 15%. kanman picks the model by complexity, so small fixes stay cheap. Read the docs (opens in a new tab)
Where is our code processed and stored? What do model providers see?
kanman runs in the EU. Coding happens in sandboxes in Frankfurt, and every run gets a fresh sandbox that is thrown away afterwards. Model calls go to the provider you choose when you bring your own keys, or through kanman to Anthropic or OpenAI in the US. Either way, the provider sees only the prompts and code context a run needs. With the self-hosted runner, code execution stays in your network. Read the docs (opens in a new tab)
Can it merge to main on its own?
Its own changes, yes, and only when your CI is green and a reviewer that did not write the change approved that exact commit with no blocking finding. The machine that merges checks this, not a prompt. Protected branches stay protected, and if your code host requires a person's approval, kanman waits for it like any colleague. A person's pull request is never merged by kanman. Read the docs (opens in a new tab)
What does it cost to run, and how do budgets work?
Every plan is a flat price per AI team, never per seat, listed in the pricing section. Local is free, Starter and Team are billed monthly. From 5 Team teams in one workspace, every Team team costs less (volume pricing). Model usage comes on top, on your own keys or at provider cost plus 15%. You set budgets per run, per day and per month with hard stops. Incident work is never blocked by a budget. Read the docs (opens in a new tab)
Can we self-host?
Yes. The self-hosted runner comes with every paid plan from Starter and does all code execution inside your network, with your model contracts. Switch on "Run everything on our runners" and model calls, reviews and every repository action stay there too; kanman's cloud keeps the board, the decisions and the audit log. With the Enterprise agreement (coming soon), kanman's control plane can run on your own servers as well, on request. Read the docs (opens in a new tab)
Can we try it before we pay?
Yes. Every new team gets the Team plan free for 14 days, no card needed. When the trial ends, cloud runs pause until you pick a plan; your board and the free Local plan keep working. If you would like us to set kanman up with your team, guided onboarding is available on request. Guided onboarding