Is Zoumadi a fit?
Zoumadi runs a linear execution model, so the quickest way to tell whether it suits your estate is to look at the shape of your processes rather than at a feature list.
The shape that fits
A process built as a chain of external service tasks and call activities — do this, then call that, then do the next thing — is what Zoumadi executes today. Estates with a large number of such models, and workflow state that has outgrown a single relational database, are the closest match.
How an assessment works
An assessment is a conversation, not a self-service tool. Under an agreement you share representative models, and you get back a model-by-model answer: what runs unchanged, and what would need to change first. Engine’s own deploy-time validator is the authority on what executes, so the answer you get is definite rather than an estimate.
Start that conversation when you are ready to share models.
Zoumadi runs a declared subset of Camunda 7 dialect models — none start/end events, external service tasks and call activities — without converting them. Compatibility is assessed model by model, and anything outside the subset is refused at deploy time rather than run incorrectly. — for the supported linear subset.
A process can call another process as one linear step, naming the callee by its process id and copying typed variables in and out by name. — by static process id, with latest, version or deployment binding and ordered typed variable copies.
Modeler draws the full standard BPMN palette, and Engine's own deploy-time validator determines what it will run. — the engine's own validator decides what can execute.