---
title: "Self-hosted issue tracker"
description: "Pick a self-hosted issue tracker for an exe.dev VM: Plane, Kaneo, Kanboard, OpenProject, Huly, Multica, or the issues built into Forgejo and Gitea."
url: https://exe.dev/deploy/issue-tracker
category: "Productivity"
updated: 2026-11-17
---

# Self-hosted issue tracker

Choose an issue tracker to run on your own VM, for your team and your agents.

- **Software:** Self-hosted issue trackers
- **Machine-readable:** https://exe.dev/deploy/issue-tracker/manifest.json

An issue tracker is a good thing to run on an exe.dev VM. It is always on,
it sits behind HTTPS and your exe.dev login from the first minute, and
you decide who else gets in with [sharing](/docs/sharing). The VM also
has coding agents on board, so the same tracker your team uses can be
filed into, worked from, and closed by Claude Code, Codex or Shelley,
through each tracker's API or MCP server.

These are the trackers with a tested recipe here. Each recipe installs
the tracker, keeps it private, backs it up nightly, and shows an agent
creating and closing an issue.

## At a glance

| Tracker | Best for | License | Memory | exe.dev sign-in | For agents |
|---|---|---|---|---|---|
| [Plane](/deploy/plane) | Teams replacing Linear or Jira | AGPL-3.0, open core | ~1.3 GB | Yes, via a small sign-in shim | REST API, official MCP |
| [Kaneo](/deploy/kaneo) | Small teams, nothing paywalled | MIT | ~0.5 GB | Yes, via Dex (OIDC) | REST API, CLI, MCP |
| [Kanboard](/deploy/kanboard) | A plain kanban board that just works | MIT | ~30 MB | Yes, built in | JSON-RPC API |
| [OpenProject](/deploy/openproject) | Gantt charts, schedules, time and cost | GPL-3.0, open core | ~2.5 GB | Yes, via header SSO | REST API v3 |
| [Huly](/deploy/huly) | Issues, chat and docs in one app | EPL-2.0 | ~4 GB | Yes, via Dex (OIDC) | Community MCP and CLI |
| [Multica](/deploy/multica) | Assigning issues to coding agents | Source-available | ~0.6 GB | Yes, via a login bridge | Agents are assignees |
| [Forgejo](/deploy/forgejo) / [Gitea](/deploy/gitea) | Issues next to your Git repos | GPL-3.0 / MIT | small | Yes, built in | REST API, Gitea MCP |

## Which one to pick

**Start with [Plane](/deploy/plane)** if you want a modern tracker for a
software team: cycles, modules, five layouts, project pages and an intake
queue, with keyboard-first screens that feel like Linear. The Community
Edition has no user limit. SSO, importers, time tracking, the workspace
wiki and dashboards are in Plane's paid Commercial Edition. It is the
largest of the light options, at about a dozen containers.

**Pick [Kaneo](/deploy/kaneo)** if you want a smaller, fully MIT tracker
with boards, a backlog, a Gantt view and GitHub or Gitea sync, and
nothing held back for a paid edition. It ships a CLI and an MCP server,
so agents are first-class.

**Pick [Kanboard](/deploy/kanboard)** if you want the least to run and
look after. It is one small container with SQLite, and it signs people
in with exe.dev on its own, with no bridge to run. It is in maintenance
mode and looks its age.

**Pick [OpenProject](/deploy/openproject)** if your projects run on
dates: Gantt charts with dependencies, milestones, backlogs, time and
cost tracking, meetings and a wiki. It is the heaviest of the classic
trackers and restarts slowly.

**Pick [Huly](/deploy/huly)** if you want one app for issues, team chat,
documents and video calls. It is the heaviest here, at about 4 GB of memory and 9 GB of images, though a
default VM runs it. Its agents use a community MCP server and CLI, since
Huly has no official one.

**Pick [Multica](/deploy/multica)** if the point of your tracker is to
hand work to agents: assign an issue to Claude Code or Codex and it does
the work on the VM, comments, and moves the card to review. It is
source-available rather than open source, and its agents run with full
access, so keep that VM private to a trusted team.

**Use [Forgejo](/deploy/forgejo) or [Gitea](/deploy/gitea)** if your
issues belong with your code. Their issues, labels, milestones and
project boards come with the Git forge, pull requests close issues, and
exe.dev signs your team in.

## Your agents and your tracker

Every recipe here stores an API token in the tracker's settings file on
the VM and shows an agent filing, commenting on and closing an issue.
Plane, Kaneo and Huly connect to Claude Code and Shelley as MCP servers
(Huly's is a community one); Kanboard and OpenProject use a small
command-line helper around their APIs; Multica has its own CLI and
assigns issues to the agents directly. From another VM or your computer, the same APIs work through the
[HTTPS proxy](/docs/proxy) with an exe.dev token.

## Sharing with your team

All of these start private: only you can open
`https://<vm>.exe.xyz/`. To let a teammate in, run
`ssh exe.dev share add <vm> <their email>` on your computer (see
[sharing](/docs/sharing)). Each recipe signs them in with that exe.dev
login on their first visit, so there are no passwords to hand out, and
`share remove` takes access away again. Huly adds everyone who signs in
to its workspace. Plane and Kaneo only let in people you have also
invited inside the tracker. In Multica, OpenProject and Kanboard they get
an account on their first visit, and you add them to a workspace or
project there.

## Frequently asked questions

### What is the best self-hosted issue tracker?

For most software teams, [Plane](/deploy/plane): it is the closest open-source match to Linear and Jira, AGPL-3.0 with no user limit, and its official MCP server lets agents work the board. If you want something lighter with nothing paywalled, use [Kaneo](/deploy/kaneo); if your issues belong next to your code, use the issues in [Forgejo](/deploy/forgejo) or [Gitea](/deploy/gitea).

### Which of these are truly open source?

Kaneo, Kanboard, Forgejo and Gitea are open source with no paid edition held back. Plane's Community Edition (AGPL-3.0) and OpenProject Community (GPL-3.0) are open source, with SSO and some features in paid editions. Huly is EPL-2.0. Multica is source-available: Apache-2.0 plus conditions that forbid running it as a service for other organizations without a commercial license.

### Which ones sign people in with their exe.dev login?

All of them, as set up on these pages: anyone you [share](/docs/sharing) the VM with opens it and is signed in as themselves, with no second password. Kanboard, Forgejo and Gitea trust exe.dev's [login headers](/docs/login-with-exe) directly. Kaneo and Huly use their own OIDC sign-in with Dex as a local bridge, OpenProject its free header sign-in, and Plane and Multica a small script that each page serves for you to read. Any program on the VM itself could forge those headers, so each page says what that means.

### Can I import from Jira, Linear or GitHub Issues?

Plane's importers are in its paid Commercial Edition. OpenProject's free Jira migrator is a beta for Jira Data Center. Forgejo and Gitea migrate whole GitHub repositories with their issues. Every tracker here has an API, so an agent can also copy issues across with a short script.

### How much does it cost to run an issue tracker on exe.dev?

Only your [VM plan](https://exe.dev/pricing); none of these charge for self-hosting the free edition. Kanboard needs about 30 MB of memory and Kaneo about 500 MB, Plane about 1.3 GB, OpenProject about 2.5 GB and Huly about 4 GB. A default VM runs any one of them.


## Related

- [Self-host Plane](https://exe.dev/deploy/plane.md): Linear-style issue tracking for your team and your agents, on your own VM.
- [Self-host Kaneo](https://exe.dev/deploy/kaneo.md): A light, fully open-source issue tracker that your agents can work from too.
- [Self-host Kanboard](https://exe.dev/deploy/kanboard.md): A small, sturdy kanban board that signs your team in with exe.dev.
- [Self-host OpenProject](https://exe.dev/deploy/openproject.md): Work packages, Gantt charts and boards that sign your team in with exe.dev.
- [Self-host Huly](https://exe.dev/deploy/huly.md): Issues, chat and docs in one open source workspace, private on your VM.
- [Self-host Multica](https://exe.dev/deploy/multica.md): An issue board where Claude Code and Codex take the tickets.
