Share and integrate
The model reaches the rest of your organisation as documents, as files which other tools read, and through the systems you already run.
The model reaches the rest of the organisation as documents, as files which other tools read, and through integrations chosen by what they are for rather than by a particular product.
Documents nobody writes
Documentation is generated from the whole model or any part of it, every diagram followed by what it shows in words, and can be published to Confluence with review comments flowing back into the tool.
In the manual: generated documentation
Never locked in
A model can be exported and imported as a file, and its processes and decisions exported to and imported from the BPMN and DMN standards. An existing BPMN estate can thus be brought in, and the model can run on a BPMN engine.
In the manual: exporting to Camunda
Fits the systems you run
Each kind of integration, e.g. delivery pipelines, sign-in, secrets, language models and security monitoring, is reached through one vendor-neutral contract, with each product a thin adapter behind it. Changing product does not change the tool.
Runs where you need it
The same software runs on your own infrastructure or hosted for you alone.
In the manual: deployment models
For architects
- Documentation as HTML, PDF or AsciiDoc; Confluence publishing.
- Models as files (export, import); BPMN and DMN for Camunda 8 (import).
- Delivery pipelines gated on the approved model, on GitLab CI and Azure Pipelines, with contract tests generated from it.
- Sign-in through any OIDC provider; leavers from a SCIM or Keycloak directory.
- Secrets from HashiCorp Vault or Azure Key Vault.
- Language models through any OpenAI-compatible endpoint, a self-hosted one included.
- The audit log and sign-ins streamed to your SIEM.
- Two container images, with all state in one data directory.