Pricing

Free as in actually free. Paid as in actually paid.

The OSS desktop app is the free path: full product, MIT license, on your machine. Cloud is for teams who need to share a board — per-seat, no fake trials, transparent feature distribution.

FREE · MIT

OSS Desktop

Free forever. The whole product, on your machine.

$0

+ pay-what-you-can donations

  • Unlimited boards & projects
  • Parallel agent dispatch
  • Autopilot (feature-dev + qa)
  • Personas & decision prompts
  • Cost analytics, live
  • Claude Code + Codex
  • GitHub Issues mode (personal PAT)
  • MCP server included
  • No telemetry · no account
Download
MOST POPULAR

Team

Cloud-hosted board for small teams. Agents stay local.

$19

per seat / month

  • Everything in OSS, plus —
  • Real-time presence on the board
  • Assignment notifications
  • Cross-device sync (laptop ↔ phone)
  • Org-wide cost rollup
  • Slack notifications on run finish
  • Managed GitHub App
  • Real-time collaborative card editing
  • Up to 25 seats
  • Google SSO
  • 90-day event retention
Start with cloud

Business

For orgs that need compliance hooks and an API surface.

$39

per seat / month · min 10 seats

  • Everything in Team, plus —
  • SAML SSO + SCIM provisioning
  • Audit log (multi-actor, immutable)
  • REST API + personal access tokens
  • Outbound webhooks
  • Per-org agent activity dashboard
  • Priority support · SLA
  • 1-year event retention
  • Unlimited seats
Contact sales

Enterprise

Custom controls for regulated environments.

Custom

volume + commitment based

  • Everything in Business, plus —
  • Dedicated CSM
  • BAA · DPA · custom MSA
  • On-prem agent registry option
  • Custom retention windows
  • Annual contract with custom terms
  • Migration & onboarding support
Talk to us

Compare

Every feature, side by side.

FeatureOSSfreeTeam$19/seatBusiness$39/seatEnterprisecustom
Boards & cards
Unlimited boards & projects
Five columns + Inbox
Local SQLite mode———
GitHub Issues modePersonal PATManaged appManaged appManaged app
Sentry import
Recipe library
Agents
Parallel agent dispatch
Autopilot — feature-dev
Autopilot — qa
Personas (built-in + custom)
Decision prompts
Cost analytics — per run/card
Cost analytics — org rollup—
Claude Code + Codex
Pre-push containment hook
Collaboration
Real-time presence—
Cross-device sync—
Assignment notifications—
Real-time collaborative editing—
Slack notifications—
Org agent activity dashboard—
Identity & access
Email login—
Google SSO—
SAML SSO——
SCIM provisioning——
Audit log (multi-actor)——
Seats includedSingle userUp to 25UnlimitedUnlimited
Integrations & API
MCP server (kanbots-mcp-server)Cloud-sideCloud-sideCloud-side
REST API + PATs——
Outbound webhooks——
On-prem agent registry———
Support & retention
Event retentionForever (local)90 days1 yearCustom
Community supportGitHub issues
Email support—StandardPriority + SLADedicated CSM
BAA / DPA——On request

Frequently asked

Honest answers, no asterisks.

Is there a free trial for cloud?
No. The free path is the OSS desktop app — fully featured, MIT-licensed, runs entirely on your machine. Cloud has a paid hosted backend (Postgres, Redis, auth, billing, real-time presence) which costs us per active user, so we don't offer a free tier. If you're evaluating, install OSS first; if you decide your team needs to share a board, sign up for cloud.
What's the difference between OSS and cloud?
OSS desktop runs locally — SQLite database, .kanbots/ next to your repo, no servers. It has every solo-productivity feature: parallel agents, autopilot, personas, decisions, MCP, GitHub mode. Cloud adds the things that structurally require multiple users or devices: real-time presence, assignment notifications, cross-device sync, audit log, SSO, Slack notifications, org cost rollup. Same UI, same agent runtime, different scale of collaboration.
Where do my agents run on cloud — locally or in the cloud?
Locally. Cloud coordinates the board, presence, and notifications. The agent itself (Claude Code or Codex) runs through the kanbots-agent CLI on your machine, in your worktree. Code never leaves your hardware. Cloud only sees metadata: card titles, threads, run status, costs.
How are seats counted?
A seat is any user who is a member of your organization. Read-only guests do not count. Add or remove seats any time; billing is prorated to the day.
Can I cancel any time?
Yes. Cancel from billing settings; you keep access until the end of the current period. No cancellation fees. On cancel you can export your data as NDJSON and import it into a fresh OSS workspace — Cloud → OSS works as a graceful exit.
What if I need to downgrade from Business to Team?
Higher-tier features (SAML, audit log, REST API, webhooks) become inaccessible. Your data is never deleted automatically; you have 30 days to export anything that requires a higher-tier feature to access.
Can I migrate from OSS to cloud?
Yes. The cloud onboarding has an "Import from OSS desktop" option: upload your .kanbots/db.sqlite, the import worker maps issues → cards, threads → comments, runs → historical run records, personas → personas. The uploaded file is deleted from blob storage within 24 hours.
Do donations to the OSS project unlock anything?
No. Donations are pay-what-you-can and never gate features. Every OSS user has the full product. Donations sustain packaging, signing certs, CI for the OSS repo — they're a gift relationship, not a transaction.
What payment methods do you accept for cloud?
All major credit and debit cards (Visa, Mastercard, Amex, Discover) via Stripe. Annual plans can be paid by bank transfer (ACH/SEPA) on request.