Decionis
Start Now
Enterprise operations

Enterprise operations

Enforce authority across the systems that already run the business.

The same authority — who may spend what, on whose behalf, up to which limit — is usually re-implemented in four systems with four drift rates. Define it once and enforce it at each point of execution, with a signed record an auditor can read.

Run a live decision — no account

First verdict in 15 minutes — no connector required

The sandbox above needs no account. When you want the verdict from your own workspace, this is the guided path: one ERP-shaped evaluation against the live protocol endpoint, in shadow, before any connector is installed.

POST /v1/protocol/evaluate-decision · shadow
curl -X POST https://api.decionis.com/v1/protocol/evaluate-decision \
  -H "Authorization: Bearer $DECIONIS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "decision_type": "PROCUREMENT_RELEASE",
    "mode": "SHADOW",
    "context": {
      "actor": "erp.integration.svc",
      "resource": "purchase_order",
      "amount": 48200
    }
  }'

Create a workspace to mint your key — evaluations run in shadow by default. Start free

On Salesforce? Install it in your org and approve once; there is nothing to paste. Rolling out in SAP, ServiceNow or Workday? Request an install link for your instance.

What goes wrong

The specific actions teams tell us they are afraid of. Each one is a decision that happens faster than a human can review it.

  • A vendor payment posting without segregation of duties
  • A purchase order above delegated authority
  • A payroll run with an unapproved change
  • An access change granting root scope
  • A termination or compensation change out of band
  • An ITSM change bypassing review

Where the decision goes

One deterministic check between the intent and the effect — ALLOW, ESCALATE or BLOCK, with a signed record either way.

The Decionis Thesis — Decionis decides what has authority to happen.An intent — from an AI, a user, or a system that wants to act — reaches Decision, where the Decionis Protocol evaluates the action. The evaluation returns one of three verdicts: ALLOW, meaning authorized; ESCALATE, meaning it needs approval or more information and is routed to whoever holds the authority; or BLOCK, meaning it is high risk or out of policy. An allowed action reaches Execution, where it is executed safely and recorded; an escalated action reaches it only once approved; a blocked action never does. Decionis is the neutral execution authority between intent and execution.INTENTAI, User, or Systemwants to actDECISIONDecionis Protocolevaluates the actionALLOWAuthorizedESCALATENeeds approvalor more infoBLOCKHigh risk orout of policyEXECUTIONAction is executedsafely and recorded
An intent — from an AI, a user, or a system that wants to act — reaches Decision, where the Decionis Protocol evaluates the action. The evaluation returns one of three verdicts: ALLOW, meaning authorized; ESCALATE, meaning it needs approval or more information and is routed to whoever holds the authority; or BLOCK, meaning it is high risk or out of policy. An allowed action reaches Execution, where it is executed safely and recorded; an escalated action reaches it only once approved; a blocked action never does. Decionis is the neutral execution authority between intent and execution.

What to do next

The same five steps every time. Nothing else on this page competes for your attention.

  1. Simulate this recipe

    Run the policy against a realistic action in the browser. Push it past what the rules allow and watch the verdict come back. No account.

  2. View the signed Decision Dossier

    See exactly what was decided and why: the rule that fired, the evidence it read, the policy version in force, and an Ed25519 signature you can verify yourself.

  3. Deploy in shadow mode

    Measure what the policy would have caught on your own traffic without touching the live path. Every recipe defaults to shadow, so the first deployment carries no execution risk.

  4. Connect a real workflow

    Point the same policy at the system where the action actually originates — a checkout, an ERP posting, a Zap, an agent's tool call.

  5. Share the verified result

    Publish the proof: a public verification link, an embeddable badge, a PR comment, or an anonymized shadow-mode finding. This is how the next person discovers Decionis.