Decionis
Start Now

Integrations

Connect the action you need to govern.

Start with one workflow. AgentSafe covers the developer integration path; Commerce Gate documents the controls available on each commerce platform.

How does Decionis connect to my systems?

Decionis evaluates a proposed action before your connected system executes it. AgentSafe provides the runtime and developer integrations for agents, APIs and infrastructure. Commerce Gate documents platform-specific commerce controls. Start with one supported workflow in Shadow Mode, review its verdicts, and check the integration’s coverage and failure behavior before enabling 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.
Review integration failure behavior

Availability and enforcement coverage vary by connector. A listed integration does not imply that every platform action is covered.

Decionis products

Which actions do you need to govern?

Decionis is the Execution Authority platform. AgentSafe applies it to agent and infrastructure actions. Commerce Gate applies it to commerce. Presence verifies a named human when policy requires approval. All use the same decision and evidence model.

Decionis · Execution Authority

Your policy → ALLOW, ESCALATE or BLOCK → signed decision evidence

Presence verifies the person when your policy requires approval for a specific action.

Decision Dossier preserves the verdict, policy context and signed evidence for independent verification.

AgentSafe is open-source. It enforces the hosted Decionis authority’s verdict; it does not decide policy locally. Hosted authority and production Enforcement are commercial services.

What should I check before connecting a workflow?

Choose the action

Identify the financial, operational or infrastructure commitment that needs policy control.

Check availability

Review the released app or integration and its current setup requirements.

Test the boundary

Confirm action coverage, timeouts and failure behavior before enforcement.

Common questions

What do integration status labels mean?

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.

Commerce connector availability

How long does integration take?

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.

AgentSafe installation

Which system executes the action?

The connected runtime or downstream application executes the action. Decionis evaluates policy and issues the authority verdict and evidence. AgentSafe enforces that hosted verdict at the boundary; it does not decide policy locally. Each commerce connector documents how its platform applies the result.

Review the AgentSafe gateway

What happens if Decionis cannot be reached?

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.

Failure behavior by integration

Updated · Published by Decionis, Inc. · Contact the team