Full audit history
The engine records every step of a process: who did what, when, and with which data. That record is the basis for traceability in financial services, and the reason for the name.
Fasti BPM is a business process management platform built on Camunda 7 CE. It runs your BPMN and DMN, keeps a full audit history, and adds the tooling the Community Edition never shipped.
Not released publicly yet. Source code and downloads will be published on this site.
Illustration of a recorded process instance, not a product screenshot.
One distribution with the process engine, a REST API and operations web apps, packaged as a single JAR. Everything Fasti adds lives in its own modules, separate from the base engine.
The engine records every step of a process: who did what, when, and with which data. That record is the basis for traceability in financial services, and the reason for the name.
Run BPMN processes and DMN decision tables on an engine proven over many years, with the namespace and APIs you already know.
Start processes, work on tasks and query state over REST at /engine-rest.
Process monitoring, a task list and user administration ship with the distribution.
Use H2 to try it in minutes; switch to PostgreSQL with one configuration profile.
To be released under the Apache License 2.0. At launch you can read the code, build it yourself and run it on your own infrastructure.
Describe the process in BPMN and the business rules in DMN, using the standard namespace.
Deploy to the engine and drive it through the REST API or the web apps. Data lives in PostgreSQL.
Each activity, decision and variable change is written to history as it happens, ready to be reviewed.
Regulated organisations that need every approval, every decision and every data change to leave a trail that can be reviewed later.
7.24.0 is the final Community Edition release. Fasti keeps the org.camunda.* packages, the BPMN namespace and the camunda.bpm.* configuration prefix, aiming to stay compatible with existing processes and integration code.
Java 21, Spring Boot, Maven and a REST API: integrate with what you have and extend through plugins instead of patching the engine.
The Community Edition stopped at 7.24.0. Fasti maintains its own engine build based on that release to keep fixing bugs and upgrading libraries. The changes below are already in the main branch of the Fasti engine; the Fasti BPM distribution will move to this engine as part of the roadmap.
| Component | Camunda 7 CE 7.24.0 | Fasti engine |
|---|---|---|
| Minimum Java | 11 | 17 |
| Spring Boot | 3.5.5 | 4.1.2 |
| GraalJS | 21.3.12 | 25.0.5.0.3 |
| Bouncy Castle | 1.47 | 1.87 |
| Jackson | 2.15.2 | 2.19.4 |
| SLF4J | 1.7.36 | 2.0.20 |
| Logback | 1.2.13 | 1.6.6 |
With any entry in disabledPermissions, monitoring queries skipped the read-permission check. The comparison is corrected so permissions are enforced as configured.
Expressions nested in an or-query bypassed the engine's query validator. Every or-query is now validated with the same validator as the main query.
Four REST endpoints that read, download or delete a single attachment or comment did not check permissions on the task. They now check them like the list endpoints do.
The page that creates the first administrator stayed open when administrators were configured outside the default group. It now closes for every way the engine defines an administrator.
The filter that appends a trailing slash could send users to another host. It now redirects only for internal paths.
Process variables whose names start with polyglot.js. are skipped when loaded into the script engine, so they cannot act as GraalJS configuration options.
Each JavaScript execution left contexts that were never closed. Each run now uses a single context and closes it when done.
The same problem in decision tables that use JavaScript expressions, fixed the same way.
Responses are always closed, including when there is no body or when output mapping fails.
A JavaScript script task whose resultVariable received an object or array always failed. The result is now stored as a Java collection.
Scope and limits. The comparison is with Camunda 7 CE 7.24.0 only. The bugs listed above were confirmed with regression tests against the source of that release. We do not attach CVE identifiers to these items and have not published performance or memory measurements. The Fasti engine requires Java 17 or later.
Items labelled “Planned” have not been released; scope and order may change.
Not yet. Fasti BPM is in active development and has not been released publicly. Leave us a note and we will tell you when it launches.
Fasti BPM is built on Camunda 7 Community Edition 7.24.0, the final Community Edition release. It is an independent project and is not affiliated with or endorsed by Camunda Services GmbH.
Compatibility is a design goal. Fasti keeps the org.camunda.* packages, the BPMN extension namespace and the camunda.bpm.* configuration prefix. The Fasti engine does raise the minimum Java version to 17.
The Apache License 2.0.
We do not attach CVE identifiers to the items on this page. They are described by what was wrong and what changed, and compared with Camunda 7 CE 7.24.0 only.
Running processes on Camunda 7 CE, or looking for a traceable BPM platform for your organisation? Tell us what you need to solve and we will let you know when Fasti BPM launches.