Find your fit
Who it is for
It can suit a team that wants a visual shared view of tasks and is prepared to run a self-hosted application. Separate boards can organize different projects or work groups, while card details give assignees a common place for dates, checklists, comments and files.
A project with simple To Do, Doing and Done stages can start with lists and cards. Teams that need to plan by date or compare work across people can evaluate the documented calendar, Gantt, table and swimlane views against a sample project.
The work it supports
Core capabilities
Set up a board with lists for the actual stages of work. Put a task on a card with a description, due date, labels or comments, then move it between lists as the team progresses. This gives a quick view of what is waiting, active and complete.
Make a card more useful for execution with an assignee, start and due dates, checklists, subtasks, attachments and activity history. The current docs also list dependencies, so a team can inspect linked work rather than relying only on card order.
Use swimlanes, table, calendar, Gantt and statistics views when a plain list is not enough. Lists and swimlanes include sorting and work-in-progress limits, which can help a team notice an overloaded stage.
Filter or sort work inside a board and use the documented global search to find a card across boards. Selected cards can also be copied, moved or recolored together, which may help during a board tidy-up.
Assign per-board roles to control participation. The docs list nine role choices and organization or team membership limits; test access with a small sample board before inviting people to sensitive projects.
WeKan documents trigger-action rules, buttons that run rules and outgoing webhooks. These can reduce repetitive board steps, but confirm a specific trigger and destination with a harmless test before making an automation part of the team’s process.
Bring existing board data in from formats the vendor lists, including Trello, JSON, CSV/TSV, Excel, Jira and Kanboard. Export options include JSON with or without attachments, Excel, CSV and TSV. Use a small migration sample to check card fields, members and files.
Team members can watch, track or mute a board and use notification drawer or email notices, according to the docs. Confirm which events generate useful alerts so that an active board does not become noisy.
Understand the offer
Pricing and getting started
WeKan says its software code is published under the MIT license, with a self-hosting option. The license and the day-to-day running costs are separate: arrange the server, installation, maintenance and backups for the chosen deployment.
Private support, feature/fix work and hosting help are separate prepaid commercial services. The page describes nonrenewing support plans and B2B nonrefund terms. Confirm current scope, price and response arrangements before buying paid assistance.
Look a little closer
Before you choose
Choose the installation method and supported database before moving real project data. The vendor lists bundles, Snap, Docker and Kubernetes, but the required maintenance path can differ between them.
Treat backup and restore as part of the setup, not an afterthought. WeKan’s install guide calls for at least daily backups and warns that deletion and infrastructure problems can destroy data without an undo path. Restore a sample before relying on the board for important work.
Pilot one realistic board with a few roles, a work-in-progress limit, a rule and a cross-board search. If replacing another tool, import a small sample and export it again to verify the data needed for a later move.
4 distinct sources behind this profile. Research observed Oct 19, 2026. Features and offers can change.
View sources and research →
