Kanera

Self-hostable project management where your team and your AI agents work on the same boards.

Kanban, Table, Calendar, Timeline, and dependency views over one set of cards. More structure than a basic Kanban board, without the overhead of a heavyweight work suite.

Try it free · Self-host with Docker · Connect an AI agent · Feature tour · Docs

Why Kanera

• Agents work on your board, not in a side chat. Claude, Codex, Cursor, and other agents pick up cards over MCP or the kanera CLI. A live chip shows each run on its card, turns amber when the agent needs you, and every change is attributed via Claude or via Codex.
• Every board in a workspace shares one setup. Lists, labels, custom fields, and automations are defined once per workspace, so In Review or Client means the same thing on every board and cross-board views line up without cleanup.
• See what blocks what. Link prerequisites across boards, then read the dependency map or the Timeline's critical path, slack, and projected finish.
• Self-hosted has no gating. No plans and no per-seat fees. Guests, the REST API, webhooks, and notifications to Slack, Discord, ntfy, Gotify, and more are all included.

Self-host with Docker

With Docker running (Compose 2.23 or newer), Bash, curl, and OpenSSL installed, run:

curl -fsSL https://www.kanera.app/install.sh | bash

The interactive installer asks whether you want localhost or production, generates the secrets, downloads the release's prebuilt images, and starts Kanera. No checkout or build is needed. For localhost, open http://localhost:4200 when setup finishes.

To supply the mode directly:

# Localhost

curl -fsSL https://www.kanera.app/install.sh | bash -s -- --mode localhost

Production with automatic HTTPS (requires public DNS and inbound ports 80/443)

curl -fsSL https://www.kanera.app/install.sh | bash -s -- --mode production --domain kanera.example.com

Already have an HTTPS proxy? Add --https existing to the production command and point your proxy at 127.0.0.1:4200. The installer creates a new ./kanera directory; use --directory to choose another. DEPLOY.md covers setup, email, backups, and upgrades; DOKPLOY_DEPLOY.md covers Dokploy.

Prefer not to run it yourself? The hosted service has a free plan and a 30-day Pro trial with no card required.

One place for moving work forward

• Plan in the view that fits. Move between Kanban, Table, Calendar, Dependencies, My Cards, Team Cards, and Work Done without duplicating work.
• See what unblocks the team. Connect prerequisites across boards, trace the chain in Map, Timeline, or Steps, spot risks and bottlenecks, and edit blocking links directly on the map.
• Keep the details with the task. Add descriptions, comments, attachments, labels, custom fields, watchers, and assignable checklist items to cards.
• Connect the code to the task. Link GitHub pull requests automatically through card keys, follow their review and merge states, and render commit links with readable change summaries.
• Set clear priorities. Use Home and a ranked Up next queue to keep urgent work visible across every board.
• Make progress visible. Review what was created, moved, completed, or checked off without chasing another status update.
• Keep knowledge nearby. Use personal, workspace, and board notes for decisions, processes, references, and project context, with Scratchpad ready for quick capture.
• Stay in flow from the keyboard. Open search and personal tools, jump between core pages, switch board views, create cards, and update an open card with contextual shortcuts. Press ? to see what is available.
• Delegate to AI agents. Give your agent cards to work on, follow live runs and blockers, and review results with clear agent attribution.
• Automate and integrate. Handle repetitive updates with trigger-based automations, post card activity into Slack, Discord, Telegram, or Zulip, and connect other tools through the REST API, webhooks, and MCP server.
• Get told what matters, where you want it. Choose per notification type whether an update reaches email, browser push, ntfy, Gotify, or your own webhook, then add per-workspace exceptions so one busy board does not drown out the rest.
• Work together in real time. Stay current with live updates, mentions, activity history, and controlled guest access.
• Work from any screen. The full Kanera experience adapts to phones, tablets, and desktops, and installs as a PWA on iOS, Android, and desktop.

Workspaces and standalone boards

Organisation

├─ Workspace │ └─ Board │ └─ Card └─ Standalone board └─ Card

Use a workspace when several boards should follow the same operating model. Lists, labels, custom fields, checklist templates, and automations are configured once and used across its boards, keeping workflows and reporting consistent as projects grow.

That means a status like In Review or a field like Client has the same meaning everywhere—no rebuilding each board or reconciling mismatched setups later.

For work that does not need to share that setup, create a standalone board. It keeps its own lists, labels, custom fields, checklist templates, automations, members, access, and integrations independently of your workspaces.

Work with AI agents, with progress you can see

Use Claude, ChatGPT, Codex, Cursor, or another agent you already work with to pick up cards, read their context, carry out tasks, and report back in Kanera. Agent work stays on the same boards as your team's work, with live progress, visible blockers, and a record of who did what for whom.

Know what is running and what needs you

An agent opens a run before multi-step work and updates it with a short progress note. Everyone viewing the board sees a live chip on the card; it turns amber when the agent is waiting on a person. Open the card to see the agent, its current work, and when it last reported. A pull request or session link can take you straight to the result.

When the run ends, its outcome and closing summary stay in the card's activity. Runs that stop reporting are marked stalled after fifteen minutes, so an interrupted agent does not leave work looking active. A blocked run makes the wait visible; the agent should also comment with its question so watchers and assignees are notified.

Follow your agent's work without losing attribution

With an OAuth connection, comments and changes show the person the agent acted for plus a via Claude, via Codex, or other agent badge. That includes browser sign-in through the CLI: name the agent with kanera auth login --agent "Claude Code". Personal API keys attribute actions to their owner without a via badge; workspace and board keys use the key's name.

Your agent's changes can notify you even though it acts on your behalf. The Agent tab brings those updates together, and Work Done distinguishes agent output from your own actions. Agents still operate within the connected person's current board permissions, and read-only credentials prevent writes at the server.

Read more about agent runs, attribution, and the Agent Workflow template.

Connect your agent through MCP or the CLI

The CLI and the MCP server expose the same tool layer, so anything an agent can do over MCP it can also do with kanera from a shell. That includes the Timeline view's schedule: work.schedule (CLI kanera schedule , SDK kanera.work.schedule()) returns the critical path, slack in working days, scheduling conflicts and the projected finish for a board or workspace, so an agent can answer "when will this finish" and "what slips if this moves" with the same numbers the chart shows, and the schedule.conflict_detected and schedule.critical_path_slipped events, or scheduling_conflict_appears / critical_path_slips automations, tell it when a plan needs attention. Try the CLI without installing it:

npx -y @kanera/cli commands

Read-only credentials are enforced by the server, and self-hosted Kanera exposes its own MCP address and API for the same CLI and SDK. See Work with coding agents from the terminal for picking up cards and reporting progress from Claude Code or Codex.

A board for delegating work and reviewing results

Start with the Agent Workflow template: Backlog → Agent Working → Waiting on Me → Review → Done. Describe the task on a card, then ask your agent to pick it up. Following Kanera's agent instructions, it moves the card as work starts, needs your input, or finishes. You review the result and decide when it belongs in Done.

The workflow combines ordinary cards with agent runs. Runs track a working session; card moves remain explicit actions by the agent or a person, so starting or finishing a run does not silently move the card.

See Kanera in action

Home keeps today and the week in focus

Start with overdue work, items due today, the next seven days, and recent progress in one focused view. Jump back into active boards and scan