Protect the actions in the systems you already run.
Every integration below shows its status and what it can stop. Start with one in Shadow Mode: nothing is blocked until you switch an action on.
Every integration and its status
Production is released and installable today. Beta is installable with limits. Private beta is built and offered on request. Planned is not available yet.
Deterministic policy enforcement on refunds, discounts, oversells, and risky orders at Shopify checkout — every governed action becomes a signed Decision Dossier with a public verification link.
Synchronous checkout-webhook enforcement for Adobe Commerce / Magento — halts a margin-breaching order (op:exception) or lets it through, failing open on any engine error, with promo-hygiene checks and federated signed Decision Dossiers.
Stop loss-making Walmart orders before you acknowledge them: every purchase order clears a margin check (cost of goods, referral fee and shipping) first.
Dual-gate governed execution for SAP S/4HANA, BTP, and CAP-side workflows — vendor payment release, procurement approval, and finance controls checked before they execute, with a signed Decision Dossier written back to the governed document.
Scoped ServiceNow app (x_dec_decionis) that wires Decision Dossiers and Decision Drift evidence into incident, change, and risk-case workflows — a Flow Designer verify-intent action with shadow-mode observers.
Create a governed decision and signed Decision Dossier inside any Zap — OAuth connection, Shadow Mode by default, and idempotent replay for temporary service failures.
Evaluate an Action before the protected module runs — the native Decionis app is in Make listing review, and the documented HTTP recipe calls the same gate and returns the same signed Decision Dossier today.
Every automation step asks permission before it executes — add an HTTP Request node before the protected step, or start from four importable example workflows that use only built-in nodes.
Ask Claude whether an action is allowed before it runs: connect the hosted Decionis MCP connector with one OAuth approval and get authority evaluations, Shadow Mode checks, and signed Decision Dossiers in the conversation.
Give ChatGPT a permission step: connect the hosted Decionis MCP connector with one OAuth approval and every governed request returns an authority evaluation, a Shadow Mode option, and a signed Decision Dossier.
Carry an enterprise policy decision point's OpenID AuthZEN 1.0 answer into a Decionis evaluation as a material signal: the PDP decides access, Decionis decides whether this exact execution has authority, and the answer travels inside the signed inputs snapshot.
Buy Commerce Gate and the agent API through AWS Marketplace.
Private beta
How does Decionis connect to my systems?
You put the check in front of the action, and your connected system still executes it. AgentSafe covers agents, APIs and infrastructure; Commerce Gate covers your store and marketplace orders. Start with one workflow in Shadow Mode, review its decisions, and check the integration’s coverage and failure behavior before you switch on enforcement.
Choose the product that matches your workflow.
Check the integration’s published release status.
Confirm which actions it can observe or stop.
Test failure behavior before enabling enforcement.
Availability and enforcement coverage vary by connector. A listed integration does not imply that every platform action is covered.
Decionis products
What do you want to stop first?
Pick the product for the actions you want to stop first. AgentSafe checks your agents' API calls, MCP tools and deployments. Commerce Gate checks prices, orders, promotions and refunds on your store and marketplaces. Presence verifies a named human when policy requires approval. Both products use the same policy decisions and signed records.
One policy check before the action commits
Your policy → allow, escalate to a person, or block → a signed record you can check
AgentSafe
For your agents, APIs and CI/CD
Stop agent API calls your policy doesn't allow.
Put the gateway in front of your agents. Every write is checked before it is sent: it goes through once, waits for your approval, or is refused.
Agent tool calls, API requests, MCP tools, deployments and infrastructure changes.
Buy a plan direct, or install from the Shopify App Store, WordPress.org or the Walmart Marketplace App Store. Plans
Presence verifies the person who approves, when your policy asks for one, for that exact action.
Decision Dossier keeps the verdict, the policy in force and the signature, so you can check it without asking us.
AgentSafe is open source. It enforces the verdict of a Decionis authority: the hosted service, or one you run in your own cloud under a commercial licence (Private beta). The open-source gateway never decides policy by itself.
Production, Beta, Private beta and Planned describe different levels of availability. Production identifies a released integration; beta labels indicate a limited or developing release; Planned is not an available integration. Read the product’s current connector page for supported actions, setup requirements and any access restrictions.
A first developer test can be small: place a decision call before one action and evaluate it in Shadow Mode. Production rollout also depends on authentication, policy review, platform permissions and connector availability. Use the relevant installation guide to estimate work for your system; there is no single duration for every integration.
Your connected runtime or application executes the action. Your policy is evaluated by the Decionis authority, hosted or in your own cloud (Private beta), which returns the verdict and evidence. AgentSafe enforces that verdict at the boundary; the open-source gateway never decides policy by itself. Each commerce connector documents how its platform applies the result.
Failure behavior depends on the integration and mode. Check the published failure-posture page for the boundary you plan to enforce, then test timeouts and loss of connectivity before rollout. Shadow Mode observes without blocking; an enforcement integration must follow its documented grant and failure rules.