Release gate
Let your pipeline ask Milita first.
Before a release goes ahead, your pipeline can ask Milita to prove the processes that must survive it — and wait for the answer.
Preview. The trigger API exists and is being confirmed in production before we document it publicly.
How the gate behaves
Held
Every required business result held. The pipeline continues.
Changed
A result differs from the last good Proof. The gate reports what changed,
when it last worked, and what happened in between.
Inconclusive
Milita could not establish the result — infrastructure trouble, or a
control she wasn’t sure of. Reported as inconclusive, never as a business failure.
What it is
A Proof, on demand, from the pipeline
The gate doesn’t run a test suite. It asks Milita to perform the whole business process in a fresh cloud session, as the required people, with fresh test data — exactly as she would on her own schedule.
- Ask for a Proof of one Promise, or of every Promise covering a release
- Wait for the verdict, or start it and collect the result later
- An inconclusive result never masquerades as a pass or a failure
- Available on Pro and above
A gate is only as good as what it checks. Milita gates on business results — whether the quote actually reached Finance Review — not on whether a script finished running.
Prove it before you ship it.
Start free, then add the release gate when one Promise isn’t enough.