It's a Plan (itsaplan) is an open-source, self-hosted project management and issue tracking application written in TypeScript under the AGPL-3.0 licence, built for teams that want Linear-style planning on their own servers and for teams that want AI agents working alongside people on the same board.

What it is

It's a Plan is a full issue tracker on its own: projects, boards, cycles, custom fields, and dashboards. It sits in the Business Software / Project & Work Management category and in the issue-tracker ecosystem whose other members are named in its own topic list — jira, linear, kanban, agile, bug-tracker. Its stated difference is that AI agents work there like any teammate: an agent gets a role, permissions, and an assignee slot, and takes issues on the same board as the people. The README is explicit that the tracker is complete without them, so an installation can run as a conventional planning tool and never turn on a single agent.

The concrete problem it solves is hosted, per-seat issue tracking. The README positions it as the open-source alternative to Linear, Jira, Trello, and Plane, and the specific thing it replaces is the SaaS subscription model those products use: the software runs on your own server, on your own database, with your own API keys, with no per-seat fees and no lock-in. Everything is reachable over the REST API, webhooks, and MCP, so the same instance serves human planners and automated workers.

Key capabilities

• Kanban, table, timeline, and calendar views, each savable as a tab with its own filters, display fields, and two-level grouping.
• Cycles that time-box work, with unfinished issues automatically moving to the next cycle.
• Per-project issue configuration covering custom fields, labels, states, and issue types, plus subtasks, checklists, attachments, and blocks, relates, and duplicates links between issues.
• AI agents as project members, running internally on any model or externally on your coding CLI, with runs started by an @mention, an assignment, or a schedule.
• Platform surface for integration: REST API with OpenAPI, an MCP server, webhooks, and pull requests from 5 forges.
• Docs as shared Markdown pages in a tree with revision history, private and locked pages, favorites, embedded files, and links to the issues they describe, alongside freeform notes boards of sticky notes on a canvas.
• Configurable dashboards reporting throughput, breakdown, and pulse, plus quick actions on an issue and auto-assignment when an issue moves into a state, with passkeys and Google sign-in across 9 languages.

Who uses it and how

• Teams that need a tracker on their own database and own API keys rather than buying seats, and that treat that ownership as the reason to migrate.
• Groups already running coding CLIs locally, which attach as external agents and pick up issues through assignment or @mention on the same board as staff.
• Mixed-discipline organisations — software development, marketing, design, support, sales, operations, and research are all named as fitting kinds of work — where one board shape has to serve several functions.
• Builders who need programmatic access: the REST API with OpenAPI, the MCP server, webhooks, and pull-request sync from 5 forges support tooling written around the tracker.
• Teams that want public visibility without accounts, using read-only share links for a view or an issue.
• Anyone who wants the tracker alone; the agent layer is optional and the README says so directly.

Getting started

The README excerpt provided here does not document an install command, a published package name, a Docker image, or a compose file, so no install method can be stated reliably. The available entry points are the repository at github.com/croffasia/itsaplan and the project site at https://itsaplan.dev/.

How it compares

Against Linear, Jira, Trello, and Plane, the axis the README draws is licence and hosting: those are proprietary hosted services, while It's a Plan is AGPL-3.0 and runs on your own server. The second axis is the cost model, since per-seat fees are replaced by self-hosted operation, and the third is data ownership, since the database and the model API keys stay with the operator. It does not claim feature parity with any of them; its claimed differentiator is agents as board members plus open API, webhook, and MCP access.

When to use it — and when not to

A self-hoster must operate the server, the database, and their own model API keys, and must accept that the project is under active development with breaking changes expected before the first stable release. It is a poor fit for teams that want a managed service with vendor support, and for anyone who will not run infrastructure or cannot tolerate an unstable pre-1.0 surface. The install documentation is not present in the material available here, which is itself a reason to check the repository state before committing a team to it; the repository is otherwise active, with 721 stars, 112 forks, and a push on 2026-09-16.

git clone https://github.com/croffasia/itsaplan.git
cd itsaplan
bun install
bun run setup   # answer "Try it"