Plans and billing

kanman's plans (Local, Starter, Team and Enterprise), billed per AI team, the 14-day Team trial, and compute on your own key or passed through at cost plus 15 percent.

kanman is billed per AI team, not per seat. Every member of your workspace can work with every team at no extra cost.

The kanman pricing page compares the plans side by side. This page explains what each plan includes and how billing works.

Plans

Plan Price per AI team What it includes Runs at a time per team
Local Free The kanman board, and the kanman MCP server in your own Claude Code or Codex. The work happens on your machine. No cloud runs
Starter €99 per month Runs by kanman, your own self-hosted runners and the option to run everything on your runners, one tracker, the outcome gate with acceptance specs and evidence, decisions and the audit log up to 2
Team €249 per month Everything in Starter, plus context connectors, maintenance scans, on-call and Slack and Microsoft Teams. For teams of up to 15 people. up to 5
Enterprise From €1,000 per month Single sign-on and SCIM, long audit log retention, a custom DPA, an optional self-hosted control plane, an SLA and an agreed number of teams up to 20

All prices are net prices. No VAT is charged: kanman is sold by a small business under § 19 of the German VAT Act (Kleinunternehmerregelung).

Teams with more than 15 people choose Enterprise or ask us.

The number of runs at a time is a cap. Your team’s own setting decides how many runs it actually starts (max_concurrency); the effective value is the lower of the two. See Policy settings.

Each team in a workspace has its own plan. A workspace with three teams can have one on Team, one on Starter and one still in its trial.

What each plan includes

Feature Local Starter Team (and the trial) Enterprise
Board, conversation with kanman and the kanman MCP server ✓ ✓ ✓ ✓
Runs by kanman, in kanman Cloud or on your own runners – up to 2 at a time up to 5 at a time up to 20 at a time
Tracker (Jira, GitHub Issues, GitLab) – one per team any number any number
Outcome gate with acceptance specs and evidence – ✓ ✓ ✓
Decisions and the audit log, including export – ✓ ✓ ✓
Context connectors (Confluence, Notion, SharePoint, docs, uploads) – – ✓ ✓
Maintenance scans – – ✓ ✓
Services and on-call – – ✓ ✓
Slack and Microsoft Teams – – ✓ ✓
Single sign-on and SCIM – – – ✓
Audit log retention beyond one year – – – ✓

Features that belong to the whole workspace, such as installing Slack or Microsoft Teams, single sign-on and the audit log, are available as soon as one team of the workspace has a plan that includes them.

When a feature is not in your team’s plan

The feature stays visible, so you always know what it does. Its settings page shows a short card instead of the controls: what the feature does, which plan includes it (for example Part of Team) and a button such as Choose Team that takes you to Plan and usage. Nothing is switched off silently:

  • If you ask kanman for something your plan doesn’t include, for example “Run a maintenance scan” on Starter, kanman tells you that maintenance scans are part of the Team plan and where to choose it.
  • If someone mentions kanman in Slack or Microsoft Teams for a team without the Team plan, kanman answers once that conversations there are part of Team. You can always reach kanman in the app.
  • Alerts sent to an on-call source of a team without the Team plan are refused, so your alerting tool shows the failed delivery instead of the alert getting lost.
  • On Local, stories move into Ready directly, without the outcome gate.

What a team already has stays readable after its plan changes: past runs, evidence, decisions, findings, incidents and the audit log.

The 14-day Team trial

Every new team starts with a 14-day trial of the Team plan, without a credit card. During the trial the team has everything in Team, with up to 5 runs at a time.

While the trial runs, the team’s card in Plan and usage shows Team trial and how many days are left, for example 12 days left (until 16 Oct 2026).

When the trial ends and no plan has been chosen, the team moves to Local. kanman starts no runs for it any more, neither in kanman Cloud nor on your own runners. The card shows Local with a line such as Trial ended on 16 Oct 2026. No runs until you choose a plan. When a story reaches Ready, kanman says once in the team’s conversation that the trial has ended and points to Plan and usage; the story waits in Ready. Nothing is lost: the board, the team’s history (runs, evidence, decisions) and Local keep working, so you can go on working stories from your own Claude Code or Codex. As soon as you choose a plan, runs start again and kanman picks up the waiting stories.

Compute: your key or pass-through

The coding agent and the reviewer use language models. Each team pays for that compute in one of two ways:

Billing mode How it works
Use your own key (bring your own key) Runs use your workspace’s own Anthropic, OpenAI, Azure OpenAI or Amazon Bedrock key. Your provider bills the model costs to you directly.
Pay through kanman (pass-through) kanman provides the model access and bills the compute at provider cost plus 15 percent, as a separate line on the team’s invoice. No key needed.

Owners and admins choose what new teams use under New teams use in Workspace settings > Model access; the team setup starts each new team with that choice. A team can choose otherwise in its Settings > Agent and models, which shows the workspace default and offers Use the workspace default to go back to it. The workspace key itself is managed in the same place, see What model providers see.

Pass-through compute is invoiced for teams with a plan (Starter, Team or Enterprise). It covers everything kanman does with its own model access for the team: coding runs, reviews and kanman’s own steps such as maintenance scans. kanman records the cost of each step as it happens and adds it to the team’s usage within about 15 minutes, so the line on the next invoice equals the spend shown in the team’s budgets plus 15 percent. Compute during the Team trial is not billed, and nothing used before a plan started is billed later. A team that uses its own key never has a compute line.

Whichever mode you use, your team’s budgets apply: per run, per day and per month. kanman stops before a budget is exceeded and asks in the decision inbox. See Budgets and cost.

On Local, the work runs in your own Claude Code or Codex, so your existing subscription or key covers the compute.

Guided onboarding

On request, we set up your first team with you: the repository, the acceptance manifest, the policy and the first stories. Guided onboarding is an optional paid service in addition to the plan, priced for your setup. Most teams start on their own with the 14-day trial; you can add guided onboarding during the trial or later. Ask us for an offer, see Questions.

Managing billing

Workspace owners and admins manage billing.

  1. Open Workspace settings > Plan and usage (/<workspace>/settings/plan). The command Plan & billing in the message box (/billing, or Ctrl+Shift+S, Cmd+Shift+S on Mac) opens the same page, and so does asking kanman “Show me the billing”. Older links to the billing page open it too.
  2. The page opens with your AI teams. Each team shows its plan (Team trial, Local, Starter, Team or Enterprise), a meter of how many of its runs are in use right now, for example Runs at once: 2 of 5 in use, and the next date: the days left in the trial or when the plan renews.
  3. On the team, choose Choose a plan. A panel opens with Starter and Team.
  4. Pick the plan, tick I order for a business and accept the terms of service (kanman is sold to businesses only) and choose Continue to payment. You complete the payment in a secure checkout and return to Plan and usage. The plan is active as soon as the payment is confirmed.
  5. For Enterprise, choose Talk to us about Enterprise in the same panel. There is no online checkout for Enterprise: the link opens an email to us that already names the team and the workspace, and we set it up with you.

To see what each plan includes, open Compare plans below the teams.

Invoices and payment details

Choose Open billing portal at the top of the card to see and download invoices and to update the payment method, billing address and VAT ID. All teams of a workspace share one billing account, so you get one invoice stream. The portal is available after the first plan has been started.

The cost of each run is shown on its run page and summed up in the weekly team report.

Changing or ending a plan

Switch a team between Starter and Team, or end its plan, in the billing portal. A plan ends at the end of the current billing period. The team then moves to Local: kanman starts no runs for it, neither in kanman Cloud nor on your own runners, while the board, the kanman MCP server and the team’s history (runs, evidence, decisions) stay available.

A team that started on an earlier pilot agreement keeps the Team plan until the end date of that agreement. After that, it continues like any other team: choose a plan, or it moves to Local.

If a payment fails, the team shows Payment due and keeps working while the payment is retried.

Questions

For Enterprise, guided onboarding or invoices, write to [email protected].

Last updated: January 1, 0001

Open kanman