WeKan ® is a FLOSS collaborative kanban board application with MIT license.
Whether you’re maintaining a personal todo list, planning your holidays with some friends,
or working in a team on your next revolutionary idea, Kanban boards are an unbeatable tool
to keep your things organized. They give you a visual overview of the current state of your project,
and make you productive by allowing you to focus on the few items that matter the most.
Since WeKan ® is a free software, you don’t have to trust us with your data and can
install Wekan on your own computer or server. In fact we encourage you to do
that by providing one-click installation on various platforms.
Change Color: Board theme and background image, Swimlane, List, Card
Overrides: 1 Admin Panel, 2 Board Settings, 3 Member Settings
Drag drop reorder with one or Multi-Selection:
Board icons to Workspaces at All Boards page
Swimlane, List, Minicard
Board
Top header: Mobile/Desktop view, Show/Hide Drag Handles, Starred Boards Bookmarks, Sort Boards, Filter, Search, Notifications, Member Settings
Member Settings:
Show My Dependencies, Show Board Dependencies, Import/Export JSON/SVG
Dependencies are for SAFe PI Plannings, drawing colored lines between cards, like Kendis or Scaled Agile Framework. Import Export as JSON and SVG.
My Cards, Due Cards, My Attachments, Search All Boards, Date Settings,
Change color - override theme, Nofications Settings (Tray, Email, etc),
Font change and Font size change, Change Avatar,
Change Language (250+ languages)
Change Settings: Show desktop drag handles, Submit editors with Enter,
Open many cards at once, Play a sound when a checklist item is completed,
Show cards count if list contains more than ... cards,
Show rescue dialoque before closing for unsaved card descriptions
Board Views:
Swimlanes, Lists
Minicard: At list there is card, that has not been not opened yet
Card: Opened card popup of minicard
Attachments viewer for PDF and Office documents
Drag drop reorder one or Multi-Selection: Swimlanes, Lists, Minicards, Checklists, Checklist Items
Burndown, Burnup, Cumulative Flow, Control, Cycle Time, Flow Efficiency,
Lead Time, Throughtput Histogram, WIP Run, Pulse, Aging WIP,
Blocker Analysis, Monte Carlo Forecasts, Process Behavior (XmR),
Work Item Size vs Cycle Time, Map
Right Sidebar / Board Settings:
Rules: like IFTTT like Trello Butler
Lists view for Rules
Workflow view: like Jira Workflows
Blocks: like Scratch or Jira AutoBlocks, shows same IFTTT Rules
Import / Export IFTTT Rules
Export board :
Select what to include: Card details, Board, Activities, Labels, People (Creator, Owner, Members, Assignees), Board Info (Board, List, Swimlane), Dates (Created, Received, Start, Due, End), Description, Custom Fields, Checklists, Subtasks, Comments, Attachments, Votin, Plannin Poker, Stickers, Location (link to map based on coordinates), Dependencies, Sort, Scrum Settings
Storage: MongoDB GridFS, Filesystem, S3/MinIO, Azure Blob, Google Cloud
Database migration
Problems
Summary
Security
Delete: Optional enable permanent delete.
History Undo/Redo available at Board, List, Card, etc menus at Swimlanes and List views
Notifications
Reports
Security: shows any attempted attacks based on names from https://wekan.fi/hall-of-fame/ like built-in SIEM with country flag and city based of location of IP address based on location headers like CloudFlare etc
WeKan and Standard for Public Code assessment was made at 2023-11. At 2026 WeKan becameß full FLOSS with FerretDB v1 Fork, also see 2026 talk WeKan 10 years at https://wekan.fi/docs for more details.
Currently Wekan meets 9 out of 16 criteria out of the box.
Some others could be met with small changes.
Translations to non-English languages are accepted only at Transifex using webbrowser.
New English strings of new features can be added as PRs to master branch file wekan/imports/i18n/data/en.i18n.json .
Please add most of your questions as GitHub issue: WeKan ® Feature Requests and Bugs.
It's better than at chat where details get lost when chat scrolls up.
1 GB RAM minimum free for WeKan ®. Production server should have minimum total 4 GB RAM.
For thousands of users, for example with Docker: 3 frontend servers,
each having 2 CPU and 2 wekan-app containers. One backend wekan-db server with many CPUs.
Enough disk space and alerts about low disk space. If you run out of disk space, MongoDB database gets corrupted.
SECURITY: Updating to newest WeKan ® version very often. Please check you do not have automatic updates of Sandstorm or Snap turned off.
Old versions have security issues because of old versions Node.js etc. Only newest WeKan ® is supported.
WeKan ® on Sandstorm is not usually affected by any Standalone WeKan ® (Snap/Docker/Source) security issues.
Backups of WeKan ® database once a day minimum.
Bugs, updates, users deleting list or card, harddrive full, harddrive crash etc can eat your data. There is no undo yet.
Some bugs can cause WeKan ® board to not load at all, requiring manual fixing of database content.
We also welcome sponsors for features and bugfixes.
By working directly with WeKan ® you get the benefit of active maintenance and new features added by growing WeKan ® developer community.
# Clone your fork
git clone [email protected]:YOUR_USERNAME/wekan.git
cd wekan
# Make the script executable
chmod +x build.sh
# Step 1: Install dependencies (Setup -> Install dependencies)
./build.sh
# Press 1 (Setup) and Enter, then 1 (Install dependencies) and Enter
# Step 2: Build WeKan (Setup -> Build WeKan, after dependencies complete)
./build.sh
# Press 1 (Setup) and Enter, then 2 (Build WeKan) and Enter
# Step 3: Run WeKan in development mode (Dev server -> localhost:3000)
./build.sh
# Press 2 (Dev server) and Enter, then 1 (localhost:3000) and Enter
If a dev server is already running on that port, the Dev server options stop it automatically and start a fresh server on the same port.