At a glance — how these 4 alternatives compare
Our read on each project's adoption, maintenance activity and commercial-use risk, derived from GitHub signals and SPDX license terms rather than star count alone. Sorted by stars. How we score.
| Project | Adoption | Maintenance | Commercial use |
|---|---|---|---|
| ★ 20,975 · JavaScript | Mainstream | Active | Low risk Embed in a proprietary product with no copyleft obligation |
| ★ 12,162 · JavaScript | Mainstream | Active | Unknown risk No clear SPDX id — treat as all-rights-reserved until verified |
| ★ 11,710 · JavaScript | Mainstream | Stale | Unknown risk No clear SPDX id — treat as all-rights-reserved until verified |
| ★ 9,677 · PHP | Mainstream | Active | Low risk Embed in a proprietary product with no copyleft obligation |
The alternatives
wekan
The Open Source kanban, built with Meteor. GitHub issues/PRs are only for FLOSS Developers, not for support, support is at https://wekan.fi/commercial-support/ . New English strings for new features at imports/i18n/data/en.i18n.json . Non-English translations at https://app.transifex.com/wekan/wekan only.
wekan/wekan Updated 2026-06-27 planka
PLANKA is the Kanban-style project mastering tool for everyone
plankanban/planka Updated 2026-06-28 leanote
Not Just A Notepad! (golang + mongodb) http://leanote.org
leanote/leanote Updated 2023-11-27 kanboard
Kanban project management software
kanboard/kanboard Updated 2026-07-01 Editor's take
Yusuke Morinaga · last revisited
Trello is a deceptively simple thing to replace — the trap is the data migration, not the boards.
Trello looks like the easiest SaaS on this whole site to replace: it is boards, lists, and cards, and every project below does boards, lists, and cards. The honest trap is not features — it is migration, and it is the one thing that genuinely splits this list. Only WeKan has a built-in Trello JSON importer that pulls your cards, lists, and attachments across; the others (Planka, Kanboard) mean either API scripting or a manual rebuild. So the real question is whether your boards are worth importing or worth pruning — answer that first, then choose on feel.
WeKan — the most faithful Trello clone, dated paint
WeKan (20.9k stars, JavaScript, MIT) is the closest functional match: boards, lists, cards, plus swimlanes and attachments, in a layout a Trello user recognises immediately. MIT licensed — the cleanest terms here. It is also the only option with a built-in Trello JSON importer, which is the single biggest practical reason to pick it: you export each board from Trello and pull cards, lists, and attachments straight in, instead of rebuilding by hand. The honest knock is purely cosmetic: the UI feels a generation behind Trello’s current design. If your team cares about behaviour matching Trello and can live with plainer styling, WeKan is the safe pick, and it is actively maintained (pushed 2026-05-20).
Planka — the modern-looking one, with a license to read
Planka (12k stars, JavaScript, NOASSERTION) is the pick if the dated WeKan
look would lose your team. It is a cleaner, more contemporary Trello-style
board — the one that will get the least “ugh, this looks old” pushback. Two
honest caveats: it has fewer integrations than the others, and its card
license is NOASSERTION (Planka changed its licensing terms — read the
current LICENSE before any commercial deployment, this is the one in this
group where the terms genuinely matter). Like the rest, no Trello importer, so
you are recreating boards by hand.
Kanboard — pick this when it is really about workflow, not pretty cards
Kanboard (9.6k stars, PHP, MIT) is the option I would reach for when the team is less “designers who loved Trello’s polish” and more “ops/IT who want a no-nonsense board with WIP limits, subtasks, time tracking, and automation rules.” It is lightweight, MIT-licensed, runs happily on a tiny PHP host, and it is the most workflow-serious of the four. It will never win a beauty contest against Planka, and that is fine for its audience.
The fourth entry is not really a Trello alternative
Leanote (11.7k stars, JavaScript) appears here, but it is fundamentally a note-taking app (Evernote-shaped) with some kanban bolted on — and its last commit on the card is 2023-11-27, well over a year stale. Between “wrong category” and “not actively maintained,” I would skip it as a Trello replacement and choose from the three above.
How to actually move
Start by exporting your Trello boards to JSON (Trello supports this from each board’s menu). On WeKan you feed that straight into its built-in Trello importer for cards, lists, and attachments; on Planka you script the import against its REST API; on Kanboard you accept a manual rebuild for the boards that matter and archive the rest. The teams that are happiest a month later are the ones that treated the switch as a chance to prune dead boards rather than faithfully porting years of clutter into a new tool.
Comparison notes
WeKan self-hosted is the most direct functional replacement for Trello, with a near-identical board, list, and card structure plus swimlanes and attachment support, though its UI feels dated compared to Trello's current design. Planka is a more modern Trello alternative with a cleaner interface but fewer integration options and no official Trello data importer requiring manual recreation. Leanote combines note-taking with kanban boards, which suits teams that mix documentation with task management, but diverges significantly from pure Trello-style kanban workflows.
Migration tips
- Export your Trello board data as JSON from each board's menu and use WeKan's built-in Trello JSON importer to migrate cards, lists, and attachments.
- For Planka migrations, custom scripting via its REST API is required since no official Trello importer exists — budget engineering time for this conversion.
- Trello power-ups integrating Slack, GitHub, and Jira will need manual replacement with equivalent webhook configurations in your chosen self-hosted tool.
Which alternative should you pick?
Replacing Trello isn't a single call — it's a trade between license terms, team size, and how much early-stage roughness you can absorb. The 4 projects above split along those lines:
- You want the most active community and the lowest risk of abandonment → wekan. 20,975★ — the largest user base in this list, which usually means more StackOverflow answers, more plugins, and more deployment runbooks online.
- You need a project that has shipped a release in the last few weeks → kanboard. Last commit 2026-07-01 — the freshest activity in this list.
License & commercial-use notes
With a Trello replacement the license usually decides more than the feature list — whether you can modify it, ship it inside a product, or host it as a service. The 4 projects here fall into:
- Permissive (wekan, kanboard) — MIT / Apache / BSD / ISC — modify and embed inside a commercial product with no copyleft obligation. The safest bucket for shipping in a proprietary codebase.
- Unverified license (planka, leanote) — GitHub returned no clear SPDX id. Treat as all-rights-reserved until you read the project's LICENSE file directly — do not assume commercial use is permitted.
License fields come from the GitHub API's SPDX classification and can lag a relicense. The repository linked on each card is authoritative — confirm its LICENSE file before any license-sensitive deployment.
Maintenance health of these 4 projects
Of the 4 projects listed, 3 shipped at least one commit in the last 12 months. See how we rank for the full criteria and our self-hosting cost reality check, which apply across every comparison on this site.
Frequently asked questions
How do these 4 alternatives compare on maintenance health?
3 of 4 have shipped a commit in the last 12 months. At least one project here has 5,000+ GitHub stars, which usually correlates with sustained maintainership. Always check the last-pushed date in the cards above and read the latest 5 closed issues — those two signals together catch 80% of abandoned-project cases.
How this page was compiled
- Repository facts (stars, license, language, last commit) come straight from the GitHub public API and are linked on each card as the primary source.
- Editorial analysis is drafted from Trello's use case and the alternatives' repository metadata, then reviewed by hand.
- Maintenance signal: 3 of 4 projects shipped a commit in the last 12 months as of the latest rebuild (most recent activity: ).
- Last editorial review: by Yusuke Morinaga.
- Spotted an error? Email [email protected] with the page URL (subject prefix
[correction]) — we ship corrections within 14 days.