Decionis Auto

Governed automationPlanned

Automations you can answer for.

Decionis Auto runs your business automations with guardrails your risk team writes, approvals from the right people, and proof of every step.

Decionis Auto is Planned. Routing a step from the tool you use today through your gateway is in private beta.

  1. Trigger
    Refund requested in Shopify
    1
    Any order
  2. Condition
    Refund is over $500.00
    2
    and the customer has fewer than 2 orders
  3. Approval
    Ask a Finance lead
    3
    Approve with a passkey · expires in 24 h, then decline
  4. The gate checks Gate · refunds.v3
  5. Step
    Refund in Stripe
    4
    Amount from step 1 · runs once
    Runs under refunds.v3Shadow
Illustration: a refund workflow with the gate before the step that moves money. Decionis Auto is Planned.

What you can answer for

Every step authorized, approved, proven and contained

Automation tools compete on how many apps they connect. Decionis Auto is for the automations where someone has to answer for what happened.
  • Authorized

    Every step that moves money or changes a system is decided before it runs: ALLOW, ESCALATE or BLOCK.

  • Approved

    When your policy asks for a person, the named approver confirms with a passkey. An ESCALATE is a person and a reason, never a spinner.

  • Proven

    Each decision is recorded in a signed record you can hand to an auditor, who can verify it without access to your systems.

  • Contained

    Credentials stay on your gateway, not in the workflow. New workflows run in shadow first, so you see what they would do before they act.

How it works

Three steps from a sentence to a run you can prove

The same flow for every automation. See the details.
  1. 01

    Describe it

    Say what the automation does and what it must never do, in plain words. Decionis Auto drafts the workflow and its guardrails; your risk team reviews the guardrails as a policy.

  2. 02

    Run it in shadow

    New workflows start in shadow. Every step reads “would have”: what it would have done and what your policy would have decided. Nothing is sent.

    • Would allowThe step would have run, once.
    • Would escalateA named person would have been asked.
    • Would blockThe step would have been stopped.
  3. 03

    Enforce

    Switch it on. Before each step that acts, the gate decides. You get a signed record of every run.

    • AllowThe step runs, once.
    • EscalateA named person decides, with the reason in front of them.
    • BlockThe step stops. Nothing reaches the system.

Runs on the Decionis Protocol

Decionis decides. Decionis Auto runs the steps.

Decionis Auto has no policy engine of its own. Every step is decided by the Decionis Protocol, the same authority behind AgentSafe, Commerce and Shield. A step that changes something runs only under a single-use grant for that exact action, and every decision comes with a decision dossier you can verify.

Use your existing tool today

Govern a step in n8n, Zapier or Make now

Keep the workflow you already run. Point the step that calls your API at your Decionis gateway, and your policy decides it before your API sees it.
Shadow and enforcement on your gateway Private beta

In shadow, your step runs as before and the decision is recorded. When you enforce, BLOCK and ESCALATE stop the request before it reaches your API.

Approvals for a held request Planned

Today an ESCALATE on a hosted gateway is held and reported, and nobody can release it. Branch to a person and stop the step.

Read the setup for n8n, Zapier and Make

Automations you can answer for.

Tell us which automation you have to answer for. In the private beta you route its steps through your own gateway from the tool you use today, and move to Decionis Auto when it opens.

Join the private beta

Decionis Auto PlannedYour existing tool Private beta