BPMN 2.0 Lightweight Modeller

Overview

Enterprise BPMN tools are bloated, expensive, and overkill for most day-to-day BA work. I needed something fast — a lightweight desktop tool that lets me model processes without signing into a cloud platform, waiting for a canvas to load, or fighting with licensing.

This modeller runs locally, accepts multiple input formats, and produces clean BPMN 2.0-compliant diagrams that can be exported and shared with stakeholders.

The Problem

Most business analysts rely on Visio, Lucidchart, or Camunda Modeler for process mapping. These tools work, but they come with friction:

• Cloud dependency — many require accounts, logins, and internet access
• Feature bloat — enterprise tools pack in execution engines, simulation, and deployment features that BAs rarely need
• Format lock-in — proprietary formats make it hard to move diagrams between tools
• Cost — per-seat licensing adds up fast for teams

I wanted a tool that does one thing well: let an analyst go from idea to BPMN diagram as fast as possible.

Input Formats

The modeller accepts multiple input types to meet analysts where they are:

• BPMN 2.0 XML — import existing diagrams from any BPMN-compliant tool for viewing, editing, or refinement
• Plain text process descriptions — write out steps in natural language and the tool structures them into a flow
• Manual node placement — drag-and-drop tasks, gateways, events, and swim lanes onto the canvas
• Hybrid workflows — combine text-based input with manual adjustments for quick iteration

Key Features

• Desktop-first — runs locally with no cloud dependency or account required
• BPMN 2.0 compliant — output follows the OMG BPMN 2.0 specification
• XML import/export — full round-trip support for standard BPMN XML
• Text-to-diagram — parse structured text descriptions into process flows
• Swim lane support — model cross-functional processes with role-based lanes
• Gateway logic — exclusive, parallel, and inclusive gateways with condition labels
• Clean output — export diagrams as PNG, SVG, or BPMN XML for documentation and stakeholder review

Why Desktop Only

This is a deliberate design choice. Process maps often contain sensitive operational details — org structures, system names, approval workflows, compliance processes. Keeping the tool local means:

• No data leaves the machine
• No vendor has access to proprietary process information
• Works offline, on planes, in secure environments
• No subscription fatigue

Use Cases

• Discovery workshops — quickly sketch processes during stakeholder sessions
• As-is / To-be mapping — document current state, then model the target state side by side
• Requirements validation — use process maps to verify that user stories cover the full workflow
• Handoffs — export BPMN XML for developers or architects who use execution-oriented tools
• Documentation — generate clean visuals for BRDs, process documentation, and training materials

What I Learned

• BPMN 2.0 XML is more complex than it looks — the spec covers execution semantics that most visual tools ignore
• Text-to-diagram parsing requires careful handling of conditional logic and parallel paths
• Desktop applications have different UX constraints than web apps — keyboard shortcuts and local file management matter more
• The best tools are the ones that get out of the way and let you think about the process, not the tool

Updates

2026-03-27 — Core modeller design and feature spec documented.