Design a workflow. Rehearse it. Then go live.
The Designer walks you from a plain-language description to a running, signed workflow in four stages — and lets you test against sample data before anything goes live.
Say what the process does, in plain language. The Designer turns your description into a candidate workflow.
See the participants, actions and disclosures the platform derived — and adjust them before you commit.
Run the workflow against sample data. Nothing is committed to the ledger; you're proving it behaves before it's real.
Publish only once rehearsal passes. Go-live is gated server-side on a rehearsal pass — you can't skip it.
Why rehearsal matters
A multi-party workflow touches participants, schemas, routing and disclosure rules. The Rehearse stage runs the whole thing against sample data so you can see exactly who would see what, and where the process would route, before a single real record is written. Because Go-live is gated on a server-side rehearsal pass tied to the exact workflow you tested, what you rehearsed is what goes live.
What you get when it's live
- Every participant signs their own actions with their own keys.
- Every action is written to an append-only, Merkle-chained register.
- Each party sees only the fields they're entitled to, enforced by per-recipient encryption.
- Counterparties and regulators can verify the record themselves — without trusting you as the operator.