Standards first, not a proprietary flowchart.
Finomium runs on Flowable under the hood: BPMN 2.0, CMMN 1.1, and DMN 1.3 - the same open standards, wired into a task inbox and incident-response tooling your ops team actually uses day to day.
curl -X POST https://api.finomium.co/api/v1/workflow-execution \
-H "Authorization: Bearer $TOKEN" \
-d '{"processKey": "provision-new-subscriber", "businessKey": "sub-48213"}'
# {"processInstanceId":"a1b2c3","status":"ACTIVE","startedAt":"2026-09-01T12:00:00Z"}BPMN 2.0 processes
Versioned deploys, suspend/activate, and full execution history and step tracing for every running instance.
CMMN case management
Plan items, sentries, and milestone tracking for work that does not fit a rigid flowchart - with per-case SLA status.
DMN decision tables
Evaluate any deployed table directly, or let one gate a real decision - like which role can claim or complete a task.
Task inbox with SLA
Claim, complete, and track due dates against business-calendar-aware service levels, not just a raw due-date field.
Business calendars
Office hours, working days, and holidays factor into every SLA and breach calculation - configurable, not hardcoded.
Event-driven triggers
Map Kafka events to BPMN/CMMN elements through a deployed event and channel registry - workflows react to your system, not the other way round.
Incident case management
A real CMMN case for delivery incidents: analyze, quarantine IPs, apply rate caps, canary test, and verify recovery - built for ops teams, not generic tickets.
Reporting
Real aggregation - duration percentiles, throughput, SLA compliance, and failure summaries - not a raw log dump.
DMN-driven, not hardcoded if/else
Which IP pool sends a message, how hard to retry, what priority it gets - each is a real, independently deployed DMN decision table your team can edit without a redeploy, chained together with a Java fallback so a decision-table outage never blocks a send.