Share and integrate

The model reaches the rest of the organisation as documents, as files other tools read, and through integrations that depend on what each is for, not on a particular product.

Generated documentation

HTML, PDF or AsciiDoc, from the whole model or any part of it, every diagram followed by what it shows in words (generated documentation), and published to Confluence with review comments flowing back.

Import and export

A model as a file (export, import), and its processes and decisions to and from BPMN and DMN for Camunda 8 (export, import).

One contract per responsibility

Each integration is reached through one contract per responsibility, with the products as thin adapters behind it:

• 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, and 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 the organisation’s SIEM.

Where it runs

The same software runs on the organisation’s own infrastructure, hosted for a single tenant (deployment models): two container images, with all state in one data directory.