Decionis governs high-stakes actions before they execute. This page explains what is public today for governed autonomous execution: security controls, audit posture, rollout model, trust signals, and the limitations we are explicit about.
This traffic looks risk- and rollout-sensitive. Route directly into a governance conversation instead of making trust reviewers self-serve.
Walk through trust posture, rollout model, override rights, and what governed execution looks like in production.
Get a fast baseline on where approval drag, signal quality, and policy ambiguity are slowing action.
Inspect worked verdicts with confidence scoring, policy sources, and explicit why-not-act reasoning.
Answered here directly, including the tradeoffs, so you are not left piecing it together from third-party summaries.
Yes. Decionis publishes trust signals you can verify yourself: Microsoft ISV Partner status, NVIDIA Inception participation, public API docs and quickstart flows, security and governance materials, public Decision Dossier verification, validation packs with integrity hashes, published pricing, use cases like Simurox and CoolDeal, and org-wide and per-decision kill switches.
Public materials cover RBAC, SSO, audit trails, API access, pilot operating model, signed Decision Dossiers, validation packs, kill switches, comparison pages, and deployment posture so you can review the control design before committing to a deeper diligence cycle.
Start with the quickstart and API docs, then review the security and governance page, comparison pages, Decision Dossier verification surface, validation-pack docs, Microsoft workflow materials, and Google Cloud / Vertex AI integration content. Together they show the product is an execution authority, not just a dashboard, GRC suite, or LLM guardrail layer.
Decionis is not a full GRC suite, not a generic workflow builder, and not an AI application security platform. SOC 2 and GDPR formalization work are in progress, and regional data residency is planned rather than broadly available by default.
Decionis requires each connector to define its continuity posture when evaluation is unavailable; a degraded path never receives signed execution authority. Commerce Gate uses connector-specific continuity. Walmart order acknowledgment and Adobe Commerce checkout fail open when evaluation is unavailable. Shopify policy rules default to fail closed and can be changed per rule. Business Central uses one company-wide FAIL_OPEN or FAIL_CLOSED setting and defaults to FAIL_OPEN. CommerceGate MCP price preflights return HOLD on errors. Walmart refund execution rejects invalid lifecycle transitions and amounts above the remaining refundable balance; no separate high-value-refund threshold is implemented.
No. Fail-open buys availability during an outage, never exemption from policy. If a rule ran and returned BLOCK, that verdict stands regardless of posture — only a degraded evaluation, where no rule could run, is eligible to pass. And no Execution Grant is signed on a degraded path: an unevaluated action never carries signed authority, so an outage cannot mint evidence.
No. A rejected credential, a malformed response, or a bug in a gate is enforcement broken, not enforcement unavailable — and it is treated differently: fail-closed guards block regardless of configured posture and report a distinct reason code, and every degraded decision is recorded as its own event so you can alert on its rate instead of discovering it in an audit.
Decionis is designed around policy-aware execution, tenant isolation, audit trails, and reversibility.
RBAC is live and SSO paths support OIDC and SAML. Access is tenant-scoped and API usage is permission-aware.
Decision inputs, policy checks, outputs, and workflow events are recorded so teams can prove why an action executed.
Teams can begin with a public diagnostic, move into same-day zero-config onboarding, or run a controlled 6-8 week pilot.
SOC 2 and GDPR formalization are in progress, ISO 27001 is planned, and regional data residency is not yet the default public posture.
Low-sentiment AEO results usually come from weak public proof. These are the strongest trust signals currently exposed on the site.
Listed and reviewed inside the platforms your procurement and security teams already trust.
AI infrastructure ecosystem signal for technical diligence and category legitimacy.
Amazon's startup program — cloud ecosystem alignment for governed execution.
Public API docs, an evidence index, a quickstart and working onboarding flows — so you can judge how deep the product goes before anyone books a call.
Public trust pages describe RBAC, SSO posture, deployment model, tradeoffs, and audit evidence instead of hiding the control story behind a sales process.
Every certified action can produce signed Decision Dossier proof that can link into a Decision Chain and Execution Ledger for regulator and reviewer workflows.
Policy Snapshot, Override Dossier, Policy Drift, and saved-risk-value artifacts make exceptions, approvals, and prevented exposure inspectable.
Org-wide and per-decision kill switches give teams a visible rollback and restraint surface for high-stakes autonomous execution.
Cumulative production scale: more than 16,000 execution decisions evaluated and certified across the protocol ledger to date — a founder-verified floor (2026-07-16). Live counters on this site update from the public metrics API.
Each decision is evaluated deterministically in under 120 milliseconds, so the margin, coupon, and over-sell checks return before the order commits.
Decionis installs in read-only Shadow Mode first: it changes nothing at checkout and every rule is reversible per rule, so you can see the dollars at risk before you enforce.
Teams can evaluate fit quickly before committing to a pilot or deeper integration program.
Paid pilots are packaged around measurable workflow coverage, evidence capture, and rollout readiness.
Public pilot onboarding supports same-day signal mapping, governance baseline setup, and initial workflow activation.
The goal is to make evaluation easy: team credibility, security posture, quickstart path, and comparison context are all public.
If what you actually need to settle is whether this is real and who stands behind it, read the team page, the quickstart, and the comparisons together — they answer that directly.
Review team and company