Read the license before the feature tour
Every tool on this page is free to download. That is the least interesting thing about them. The questions that decide whether an open source tracker serves you for five years are different: What license governs the code, exactly? Where is the boundary between the open edition and the paid one? If you modify the tool and offer it to your own customers over a network, what does the license make you publish? And who maintains the project, at what pace, with what governance? This guide answers those four questions for each candidate, then grades the trackers as trackers.
One correction before the bench: Linear itself is proprietary and cloud-only, so every tool here is a replacement, not a variant. And a second correction that this category needs constantly: a free hosted tier is not open source, and source-available is not open source. The bench below contains only projects whose code is available under an OSI-approved license, and the boundary cases are labeled as such.
| Tool | License | Shape | Edition boundary |
|---|---|---|---|
| Plane | AGPL-3.0 | Closest to Linear: cycles, modules, pages | Some features reserved for cloud and enterprise editions |
| Huly | EPL-2.0 | All-in-one: issues, docs, chat | No feature gate on self-hosting; hosted cloud discontinued in 2026 |
| Vikunja | AGPL-3.0 | Task manager with strong list and kanban views | Open core is the product; small project |
| Gitea | MIT | DevOps platform: Git, CI, packages, issues | No gate; the tracker is one module of a bigger platform |
| Kaneo, Focalboard | MIT | Lightweight boards and tasks | Young or slow-moving projects; graded in prose below |
Plane: AGPL-3.0, and the boundary to check
Plane is the default answer because it is the closest shape to Linear that open source offers: work items, cycles, modules, pages, and intake, in an interface that feels current. Its Community edition is licensed under AGPL-3.0 and self-hosts free; the cloud Free plan covers up to 12 users, Pro costs $6 per user per month billed annually, and Business $13.
The AGPL matters in one specific scenario: if you modify Plane and offer the modified version to others over a network, the license obliges you to offer them the source of your modifications. Internal use, unmodified or modified, does not trigger distribution duties for your own team's work in the way people fear; the obligation is about offering the service to third parties. The edition boundary matters more day to day: some capabilities live in Plane's cloud and enterprise offerings, so check the exact feature you need against the Community edition before migrating, not after. The self-hosted guide grades what running Plane takes.
Huly: EPL-2.0, all-in-one, and a 2026 status change
Huly is the ambitious entry: issues, documents, and team chat with huddles in one platform, licensed under the Eclipse Public License 2.0. EPL-2.0 is weak copyleft: it is friendlier to commercial and internal use than AGPL, with obligations centered on the files you modify rather than the whole service. Self-hosting carries no feature gate; you get the full product.
The status change every buyer must know: Huly's hosted cloud was discontinued in 2026 because funding ended, and the upstream repository is frozen, with development continuing in a community fork. Older roundups still quote Huly Cloud per-workspace tiers (Common free, Rare $19.99 per month); those tiers are no longer purchasable, and this site's dataset carries them as null for exactly that reason. Huly today is a self-host-only commitment to a project in transition: powerful, genuinely open, and a maintenance bet you should make with open eyes.
Vikunja, Gitea, and the honest small print
Vikunja (AGPL-3.0) is a task manager first: excellent lists, kanban, Gantt, and a calm interface, self-hosted by many home and small-team users. As a Linear replacement it covers personal and small-team tracking well and product-engineering rituals (cycles, triage) thinly. Gitea (MIT) is the opposite shape: a complete self-hosted DevOps platform whose issue tracker is competent but basic. Choose Gitea when the goal is consolidating code hosting, CI, and issues in one small binary, the same consolidation logic graded in the GitHub destination guide; do not choose it expecting Linear's planning model. Kaneo and Focalboard, both MIT, are lighter boards worth knowing for small teams; Kaneo is young, and Focalboard's pace has slowed, so both are prose-grade here rather than tool-grade: promising, small, and a maintenance risk to weigh honestly.
What about the tools that are not on this bench? Any tracker whose repository is source-available under a custom license, or whose open edition is a demo of the paid one, is excluded by the rule this page runs on. If a vendor's marketing says open source, the license file in the repository is the only version of that claim worth trusting, which is why the checklist below starts there.
