Zoumadi

Requirements

What an evaluation or a deployment of Zoumadi needs, so the cost of trying it is clear before you ask for a demo.

Java and build baseline

Zoumadi builds and runs on Java 21.

Deployment prerequisites

Zoumadi expects infrastructure it does not bring with it, and each piece is one your platform team likely already operates: a NATS JetStream cluster to hold the command log and its projections, one or more external worker processes to carry out service tasks, a gateway in front of any traffic arriving from outside the deployment’s own network, and an OIDC identity provider for interactive Cockpit access. Backup and restore is a built mechanism on Zoumadi’s side; the storage, the authority to write to it and confirming that a restore works belong to your deployment.

Getting a copy to evaluate

An evaluation begins through the commercial contact route.

Java 21 (Temurin) is the current build and runtime baseline for Engine and Cockpit.

A NATS JetStream cluster is the one infrastructure dependency Engine needs: the replicated command log and its key-value projections live there, and no relational database is required for process state.

Service tasks are carried out by external worker processes that connect over NATS; the engine itself does not run your task code.

Zoumadi is designed for traffic from outside a deployment's own network to reach it through an APISIX gateway that the deployment provides and operates.

Cockpit is designed for people to sign in through your own OIDC identity provider, so Zoumadi keeps no identity directory of its own.

Zoumadi supports NATS subject-level authentication and permissions; your deployment authors and issues its own credential grants. — your deployment writes its own NATS credentials and grants.

Zoumadi has a built backup and total-loss restore mechanism; a deployment must still supply and prove its own storage authority and restore evidence. — your deployment decides who may invoke it.

Zoumadi can be embedded in a Java application through its own client API, rather than reached only over the network. — your deployment supplies the providers before production use.

Evaluation copies are delivered through the commercial process.