Boards and cards
Columns bound to workflow stages, swimlanes, drag and drop with optimistic moves. Cards hold markdown, attachments, tags, priorities, due dates, estimates, custom fields, subtasks and checklists.
Worklane is a workflow-first Kanban platform for software teams. Stages and transitions form a real directed graph — with branches, merges, conditions and permissions — and everything else on the platform reacts to it.
English, Russian and German out of the box — switch without a reload.
Draw the process your team actually follows: branch it, merge it, send work back. The board renders the graph, and a move that the workflow rejects rolls straight back — no card ever ends up somewhere the process does not allow.
Require a comment or an assignee, restrict a move to a role, enforce a WIP limit, or gate it behind a condition tree over the card's own fields.
Drag to arrange, drag to connect. Unreachable stages and dangling edges are flagged as you draw, before anyone works against a broken process.
Software development, mobile, marketing, HR — or an empty canvas. Every template is a normal workflow you can keep editing afterwards.
Every meaningful action emits a catalogued domain event. Automation, webhooks, the live board, plugins and the audit log all read from that one stream, so the parts stay in agreement without any glue of your own.
Columns bound to workflow stages, swimlanes, drag and drop with optimistic moves. Cards hold markdown, attachments, tags, priorities, due dates, estimates, custom fields, subtasks and checklists.
A milestone sits on the board like a card while grouping the work beneath it: progress by count or by effort, forecast completion date, dependencies, nesting and a roadmap timeline.
IF an event and a condition tree, THEN an ordered list of actions — fifteen built in, with delays, per-action error handling and a run log. Webhooks are signed, retried with backoff and templated per event.
Markdown, threads and replies, emoji reactions, @mentions with autocomplete, code blocks, image previews, full edit history and live typing indicators — where the work is, not in a separate chat.
Assigned work, overdue and due-soon cards, work blocked by an unfinished dependency, reviews, mentions and invitations — each card listed once, under its most urgent reason.
Classic and Classic Dark, Glassmorph, Retro, Neumorphism, Mesh Gradient, Pixel and Workcraft. Pure CSS variables, so switching is immediate — and independent of the language you picked.
A plugin contributes settings, screens, automation actions, event listeners and its own English, Russian and German catalogue. Most need no external service and no extra tables — they build their view from data the platform already holds.
Nested pages, markdown with revision history, server-side search, and two-way links between pages and the cards they describe.
Reporting takes one sentence. While you type, the queue checks whether the same thing has been reported before — confirm and it becomes another occurrence rather than a second row.
Pin feedback to the pixels it refers to and turn the lot into subtasks. Ticking a subtask resolves its point and the other way round, so the checklist and the image never disagree.
Cycle time, lead time, throughput, 85th percentile and a cumulative flow diagram, rebuilt from the event store rather than from a snapshot.
Not just the interface. Validation errors, notifications and emails are localized on the server too, resolved from user preference, then project override, then company default, then Accept-Language. Dates, numbers, the first day of the week and pluralization follow the active locale — including Russian one/few/many.
3 cards moved to Code review
3 карточки перемещены на «Ревью кода»
3 Karten in „Code-Review“ verschoben
A fourth language needs no code: translation overrides can be added at runtime, and user-generated names — projects, stages, tags, custom fields, milestones — can be translated too.
Open the app and start with a template, or draw your own workflow from an empty canvas. The demo company comes seeded with a branching process, five members and a board that already has history.