kanzo vs kanri

Local Kanban apps compared

kanzo and kanri both provide locally stored Kanban boards for organizing work. kanzo combines a browser board with an MCP server, CLI, and sharing or sync options, while kanri is a desktop app focused on offline use and personal board management.

kanzokanri
LanguageRustVue
LicenseAGPL-3.0GPL-3.0
Stars5092k
Forks26172
Last analyzedNov 1, 2026Oct 3, 2026

Key differences

  • kanzo is written in Rust and uses SQLite; kanri is written in Vue and stores boards in a JSON file.
  • kanzo connects coding agents through MCP and also offers browser and CLI access; kanri focuses on desktop board management with keyboard shortcuts.
  • kanzo supports live sharing on a trusted network and Git-based sync; kanri has no cloud sync and leaves backups and exports to users.
  • kanzo is licensed under AGPL-3.0; kanri uses GPL-3.0, with some files under other licenses.
  • kanzo runs on macOS, Linux, Windows, and Raspberry Pi; kanri runs on Windows, macOS, and Linux.
  • kanzo has 509 stars and 26 forks and is described as only days old in the supplied health data; kanri has 2k stars and 172 forks and is in active development.

Choose kanzo if you…

  • want coding agents to take tasks, update statuses, and comment through MCP.
  • need a browser board with CLI access and local SQLite storage.
  • want to share a board across a trusted network or sync it between machines through a private Git repository.
Read the kanzo analysis →

Choose kanri if you…

  • want an offline desktop board without an account or internet connection.
  • prefer board data stored locally in a JSON file and manage your own backups.
  • want to import Trello data and use card features such as subtasks, due dates, and tags.
Read the kanri analysis →

Compare the numbers side by side, or add more projects

This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.