Wekan Hosting

How Wekan works

Wekan represents a workflow as a board divided into lists. Cards move between those lists as work changes state, while titles, descriptions, members, labels, dates, checklists, attachments, comments, and custom fields keep the relevant context with each item. Swimlanes can separate streams of work without creating a different board for every team or customer.

Board visibility and membership determine who can view or change information. Administrators can create accounts and organise shared workspaces, while the API allows approved external tools to interact with boards and cards. The catalogue packages MongoDB alongside the application to retain accounts, board content, and configuration.

Key Wekan features

Kanban boards make status visible without requiring every participant to interpret a report. Filters help people narrow a busy board by member, label, date, or other card information. Checklists break a card into smaller actions, and comments preserve a discussion beside the work instead of scattering it across chat messages.

Rules and integrations can extend a board, but the exact behaviour depends on the installed release and configuration. The hosted page therefore describes the stable board, list, card, member, label, checklist, attachment, and API concepts rather than promising every community integration.

Wekan vs Trello

Wekan is a self-hosted Kanban application whose boards and account data stay inside the operator's deployment. Trello is an Atlassian-hosted service with boards, templates, built-in automation, integrations, and a Power-Up ecosystem maintained within its commercial platform.

Trello may be the stronger choice for teams that want a mature managed service, official integrations, and vendor-operated automation without maintaining an installation. Wekan is appealing when the requirement is a familiar card workflow on controlled infrastructure and the organisation can manage accounts, configuration, and service boundaries itself.

Who uses Wekan

Product and operations teams use Wekan for backlogs, release work, support queues, procurement, and recurring processes. Editorial groups can plan content across stages, while small organisations use boards to replace status spreadsheets with a shared visual queue.

Kanban software does not define the workflow by itself. Teams still need sensible list names, ownership rules, limits on work in progress, and a process for archiving obsolete cards. A board that contains every task indefinitely can become harder to use than the spreadsheet it replaced.

Self-hosting Wekan: requirements and cost

Capacity depends on users, boards, cards, comments, attachments, filters, API calls, and the packaged MongoDB service. The plan mapping lists PostgreSQL and MariaDB as “Not required”, so Wekan does not receive the relational-database step-up. Persistent board and account data still need to remain attached to the application stack.

AvaHost maps Wekan to Plan 1 at €2. For Wekan, the service provides one-click setup, branded HTTPS hosting, automatic application updates, and scheduled backups. Application email is disabled, so invitations, notifications, and email-based password recovery are unavailable; administrators should create users through supported non-email workflows and keep owner access documented.