BPMN 2.0 vs. No-Code: When Does Which Approach Pay Off?
Deutsch
BPMN 2.0 or no-code? What sets them apart, when each one fits, and what to watch for on governance and portability in 2026.
In short: BPMN 2.0 is an international standard for describing processes as models. No-code is an approach to building applications from ready-made components without programming. The two are not mutually exclusive. No-code pays off for simple, self-contained workflows with few people involved. BPMN 2.0 pays off when a process touches several departments and systems, contains decision rules, or has to be shown to auditors, customers or IT [1][3].
If you want to digitise processes, you usually hear two pieces of advice: model them in BPMN 2.0, or build them without code in a no-code tool. Both lead to running workflows. They differ in how a process comes about, who maintains it, and what remains when systems or vendors change. This article clarifies the terms, shows a real-world example and gives you five questions to help you decide.
1. What is BPMN 2.0?
BPMN 2.0 is standardised as ISO/IEC 19510:2013 and is identical to OMG BPMN 2.0.1 [1]. The notation is meant to be understandable for everyone involved, from the specialists who design processes to the developers who implement them and the managers who run them [1]. ISO describes it as a bridge between process design and implementation. The standard was last reviewed and confirmed in 2022 [1].
The OMG, which maintains the standard, describes BPMN as a flowchart-like notation that is independent of any particular implementation environment [2]. The current OMG version is 2.0.2, from January 2014 [2].
2. What is no-code?
The Lower Saxony Ministry of Economic Affairs describes no-code as a step beyond low-code: applications are built by assembling ready-made components and configurations, without writing a single line of code [3]. The main difference from low-code is the amount of technical knowledge required. Low-code still needs some grounding in programming logic, no-code does not [3].
The trade-off is flexibility. Low-code platforms can be extended with custom functions using programming syntax, whereas no-code solutions typically cannot, which limits how far you can customise them [3].
3. Why the comparison falls short
BPMN 2.0 is a standard for representing processes. No-code is an approach to building software. They sit on different levels and can be combined.
The Lower Saxony police provide an example. A team of experts captured knowledge about cybercrime in process models using BPMN 2.0 and DMN 1.0. DMN stands for Decision Model and Notation and models decision rules [3]. A BPM engine then generated a web interface from the models automatically. Around 95 percent of the digitisation effort went into modelling, and around 5 percent into supplementary service functions programmed by IT specialists [3]. In other words, domain experts without deep programming skills could model their own knowledge, and IT was relieved [3].
So the real question is not "BPMN or no-code" but: how complex is the process, and how much of it should survive as a model that stays readable regardless of the tool?
4. When does which approach pay off?
These rules of thumb help with a first assessment. They do not replace a check of your specific case.
No-code is often enough when
- the workflow is simple and self-contained, such as digital leave requests or processing membership applications, which the State of Lower Saxony cites as examples [3]
- few people are involved and hardly any systems need to be connected
- the workflow rarely changes and needs little custom logic
- a small team wants to get started quickly
BPMN 2.0 pays off when
- a process connects several departments and systems, for example onboarding with HR, IT and the line manager
- decision rules, approvals and escalations are part of it
- you have to present the workflow to auditors, customers or IT and need a model everyone can read [1]
- the process is meant to run for a long time, independent of a specific environment [2]
Lower Saxony also points out that hybrid no-code/low-code platforms are often used at the edge of large core systems to improve small sub-processes [3]. And according to the paper, there is no single universal platform, as vendors set different priorities [3].
5. Governance decides success
Whichever route you choose, without rules things sprawl. Bitkom describes how sprawl quickly emerges when business departments build their own applications on external platforms without IT oversight, and calls release management and a governance model indispensable [4].
The State of Lower Saxony recommends guidelines for in-house software development, such as separate development and test environments and permission concepts to protect company data, plus trusting exchange with IT to avoid shadow IT [3]. This applies to no-code tools just as much as to BPMN platforms.
6. What also matters in 2026: portability and AI
Portability. The European Commission gives 12 September 2025 as the date the Data Act became applicable and updated the related FAQs in January 2026 [5]. Among its rules, customers of cloud services should be able to switch to another provider quickly and smoothly, without losing data or the functionality of applications [6]. For your selection, this means: ask how you can export data and processes. According to the OMG, a BPMN model is independent of any particular implementation environment [2]. With no-code applications, portability depends on the vendor.
AI. Lower Saxony describes how vendors integrate generative AI into no-code platforms, speeding up app development considerably [3]. Building faster does not change the fact that governance and documentation remain necessary.
7. Five questions for your decision
Answer these for the process you want to automate.
1. Does the process touch more than one department or more than two systems?
2. Are there decision rules, approvals or escalations?
3. Do you have to document the workflow for auditors, customers or IT?
4. Is the process meant to run for more than a few years?
5. Do you want to be able to change vendors or systems later without rebuilding the process?
If you answer yes three times or more, that points to a BPMN model. With one yes at most, a no-code tool is often enough.
8. BPMN 2.0 and low-code with FireStart
FireStart brings both sides together. Processes are modelled in BPMN 2.0 (ISO/IEC 19510), and the models stay portable. Business teams adapt workflows themselves using low-code, without an IT ticket. FireStart complements SAP, DATEV, Personio and Microsoft 365, so nothing has to be replaced.
Approvals and critical decisions stay with people, and every step is logged with user, timestamp and decision. AI supports document extraction, classification and decision preparation. Hosting is in Germany (GDPR compliant), either in the cloud or on-premises.
Two examples of processes that span several departments: employee onboarding and invoice approval.
Frequently asked questions about BPMN 2.0 and no-code
What is the difference between BPMN 2.0 and no-code?
BPMN 2.0 is a standardised way to represent processes as a model [1]. No-code is an approach to building applications from ready-made components without programming [3]. One describes how a process is represented, the other how an application is built.
Is BPMN 2.0 an official standard?
Yes. BPMN 2.0 is standardised as ISO/IEC 19510:2013 and is identical to OMG BPMN 2.0.1 [1]. ISO reviewed and confirmed the standard in 2022 [1].
Can I combine BPMN 2.0 and no-code?
Yes. The Lower Saxony police modelled processes in BPMN 2.0 and DMN 1.0 and turned them into a web interface on a low-code platform [3].
When is no-code enough?
For simple, self-contained workflows with few people involved, such as digital leave requests [3]. When a lot of custom logic is needed, the lack of code extensibility sets limits [3].
When do I need BPMN 2.0?
When a process touches several departments and systems, contains decision rules and approvals, or has to be presented to auditors and IT. A model everyone can read helps here [1].
What changes in 2026 for the portability of cloud applications?
The Data Act has applied since 12 September 2025 [5]. It is meant to let customers of cloud services switch providers without losing data or functionality [6]. Still, ask your vendor about export and documentation.
Sources
1. ISO: ISO/IEC 19510:2013, Object Management Group Business Process Model and Notation, https://www.iso.org/standard/62652.html
2. OMG: BPMN, Business Process Model and Notation, https://www.omg.org/spec/BPMN/
3. Lower Saxony Ministry of Economic Affairs, Transport, Construction and Digitalisation: Positionspapier Low-Code (September 2024, in German), https://www.mw.niedersachsen.de/download/213480
4. Bitkom: Bedeutet Low-Code das Ende von ERP? Discussion paper (in German), https://www.bitkom.org/sites/main/files/2023-02/230215DiskussionspapierERPfinal.pdf
5. European Commission: Commission publishes Frequently Asked Questions about the Data Act, https://digital-strategy.ec.europa.eu/en/library/commission-publishes-frequently-asked-questions-about-data-act
6. Malta Communications Authority: The Data Act, https://www.mca.org.mt/the-data-act
FireStart wird in der EU gehostet (DSGVO-konform, EU-Datenspeicherung). Website: www.firestart.com. Kontakt: sales@firestart.com.
