Wekan: A Self-Hosted Kanban Board with Real-Time Collaboration and a Heavy Maintenance Load

What Wekan Solves and Who It Serves

Wekan targets teams and individuals who want a Kanban board without handing their data to a third-party service. The README states it is completely open source and free software under the MIT license. It positions itself as a tool for personal todo lists, holiday planning with friends, and team projects. The project claims a largest user base of 30,000 users in a single company, which indicates it is built to scale beyond small teams, though the README does not specify how that deployment was configured. The primary audience is organizations that require data control, such as public institutions or privacy-conscious companies. The README mentions an assessment against the Standard for Public Code, which suggests a focus on government and public-sector adoption, even though the project currently meets only 8 out of 16 criteria out of the box. If you need a Kanban tool that you can run on your own hardware, Wekan is a candidate. If you prefer a hosted solution, this is not the right project.

Architecture: Meteor, MongoDB, and Real-Time Updates

Wekan is built on the Meteor JavaScript framework, with the main branch using Meteor 3.5 and Node.js 24.x. The backend relies on MongoDB for data storage. The real-time user interface, as the README calls it, is a core feature: changes to boards, cards, and lists appear to other users without manual refresh. This real-time behavior comes from Meteor's publish-subscribe model, which pushes database changes to connected clients. The data flow is straightforward: clients interact with the Meteor server, which reads from and writes to MongoDB, and the server broadcasts changes to all subscribed clients. The README warns that if you run out of disk space, the MongoDB database gets corrupted, which highlights the central role of the database. There is no mention of an alternative database or a standalone mode without MongoDB. For a self-hosted deployment, you must be prepared to run and maintain a MongoDB instance, which is a significant operational consideration.

Getting Started: Docker, Snap, and Source Builds

The README points to https://wekan.fi/install/ for downloads, and lists Docker containers on GitHub, Quay, and Docker Hub. A docker-compose.yml file is provided in the repository, which is the quickest way to get a production-like setup. For development, the README describes a two-level build script: `./build.sh` (or `./build.bat` on Windows) presents a menu with categories like Setup, Dev server, Tests, Docker, and Tools. You pick a category number, then an item number inside it. Prerequisites for building from source are Git, Node.js 24.x, and Meteor. The README gives specific commands: install Node.js 24.x via nvm (`nvm install 24`, `nvm use 24`), and install Meteor with `curl https://install.meteor.com/ | sh`. There is also a mention of Snap as a deployment platform, and the README warns about automatic updates for Snap and Sandstorm, implying those are supported install methods. For a production server, the README recommends at least 4 GB total RAM, with 1 GB free minimum for Wekan. For thousands of users, it suggests a Docker setup with three frontend servers, each with 2 CPU and two wekan-app containers, plus one backend wekan-db server with many CPUs. That is a concrete scaling guideline, though it is not a benchmark result.

Operational Realities: Updates, Backups, and Failure Modes

The README is unusually blunt about operational risks. It states that updating to the newest version very often is a security requirement, because old versions have issues from old Node.js versions, and only the newest Wekan is supported. It also says backups of the database must happen at least once a day, and lists reasons: bugs, updates, users deleting a list or card, hard drive full, hard drive crash. It explicitly notes there is no undo yet. Some bugs can cause a board to not load at all, requiring manual fixing of database content. This is a genuine limitation: Wekan is not a set-and-forget application. The release cadence is high, with three releases (v11.24, v11.23, v11.22) on the same day, 2026-08-29, which supports the claim of frequent updates. If you cannot commit to a daily backup routine and a rapid upgrade cycle, Wekan will likely cause you pain. The README also warns that running out of disk space corrupts MongoDB, so disk monitoring is not optional.

The Standard for Public Code Assessment: A Mixed Signal

The README includes a notable self-assessment: Wekan meets 8 out of 16 criteria of the Standard for Public Code, and some others could be met with small changes. This is a rare admission from a project. It signals that while Wekan is open source and free, it is not fully aligned with the criteria that some public-sector organizations use to evaluate software. The assessment was made in November 2023, so it may be dated by the time of reading. The criteria not met are not specified in the README, so you would need to check the wekan.fi page for details. This is a concrete factor for government or public-sector adopters: if you need full compliance, you may need to contribute changes or accept gaps. For private companies, this may be irrelevant, but it is a transparent disclosure that the project does not claim to be perfect out of the box.

Translation Coverage and Community Contribution

Wekan has been translated into 234 languages, with 197 essentially complete, according to the README. Translations are accepted only via Transifex using a web browser, and new English strings can be added as PRs to the file `wekan/imports/i18n/data/en.i18n.json`. This is a concrete contribution path. The README encourages reporting bugs and feature requests as GitHub issues, rather than chat, because details get lost in chat. It also mentions IRC discussions. This shows a community that is active but has a specific workflow. For an engineering team evaluating Wekan, the translation breadth is a plus if you need multi-language support. The contribution process is clear, but it is not a typical pull-request-only model for translations, which might be a minor friction point.

Maintenance Cost and License Implications

The MIT license is permissive, which means you can use, modify, and distribute Wekan without copyleft obligations. The README does not mention any patent or trademark clauses beyond the use of the registered trademark symbol, so you should check the full license text for any trademark restrictions. The maintenance cost is high: you need to update frequently, back up daily, and monitor disk space. The README states that new features and fixes are added many times a day, which implies a fast-moving codebase. This can be a burden if you prefer a stable, slow-changing system. The README also mentions commercial support is available at wekan.fi, which is an option if you need external help. There is no explicit upgrade guide in the README, but the CHANGELOG.md is referenced for runtime updates. Plan for regular upgrade testing in a staging environment before applying to production, given the rapid release cycle.

Alternatives: What Else to Consider

The README does not name competitors, but any Kanban tool comparison should include Trello, which is a hosted SaaS with a free tier and a polished UI. Trello offers real-time collaboration out of the box, but you do not control the data. The key difference is deployment: Wekan is self-hosted, Trello is cloud-only. Another alternative is Focalboard, an open-source project that also offers self-hosting, but it uses a different architecture (Go backend, PostgreSQL or SQLite) and has a different feature set. The README does not mention Focalboard, but as an engineer, you know that the choice often comes down to whether you want a Meteor/Node.js stack or a lighter-weight Go binary. Wekan's real-time UI is a strength, but it comes with the operational weight of MongoDB. If you need a simpler self-hosted Kanban with fewer moving parts, a single-binary tool might be easier to maintain. The README does not compare these, so you must evaluate based on your own stack preferences.

Editorial conclusion

Adopt Wekan if you need a self-hosted, MIT-licensed Kanban tool with real-time collaboration and can commit to daily backups, frequent version updates, and a production server with at least 4 GB RAM. Do not adopt it if you lack the operational capacity for MongoDB maintenance and regular upgrades, or if you expect a polished, low-maintenance SaaS-like experience. Before deploying, verify your backup strategy, confirm you can run the latest release (v11.24) with Node.js 24.x and Meteor 3.5, and check the Standard for Public Code assessment: Wekan meets only 8 of 16 criteria out of the box, so review those gaps if public-sector compliance matters to you.

Official sources

1. Official documentation
2. Official README
3. Project repository
4. Release notes