Loading…
Questions
Everything teams ask while adopting this.
31 questions, grouped by what you are trying to settle. If you are still working out what Decionis is, start with why it exists — this page assumes you already know and are resolving a specific question.
Getting started
What it takes to try it, and what changes when you do.
- Do I have to replace my existing workflows?
- No. Decionis sits in front of the action you already take — your workflow, your systems, your approvers. It answers one question before execution, should this run, and hands the verdict back to whatever asked. Nothing is migrated into Decionis.
- Can I start without changing production?
- Yes. Shadow Mode evaluates your real traffic and records what it would have allowed, held, or blocked — while stopping nothing. When you turn on enforcement, what happens on a timeout or engine error is decided by consequence: gates in front of agents, payments, and margin floors fail closed, while retail checkout with a present buyer fails open so an outage never stops a sale. Either way the degraded decision is recorded, and no signed authority is ever issued for an action policy did not evaluate.
- Do my policies stay mine?
- Yes. Policies are versioned inside your own workspace and are never shared between customers. If policy cannot leave your network at all, the whole control plane runs in your own VPC with one helm install.
- How long does integration actually take?
- Minutes for the API, an SDK, or MCP — one call in front of the action you want gated. Native platform connectors take longer because they follow each marketplace's install and review path, and an enterprise rollout across several systems is measured in weeks, not minutes.
- Can I verify a decision myself?
- Yes. Every verdict produces an Ed25519-signed Decision Dossier, and you can check the signature against our published JWKS offline — no account, and no need to trust our code for the result to mean something.
- Can I try Decionis without an account or a sales call?
- Yes. The Decionis sandbox generates a real, signed Decision Dossier from a scenario of your choice in your browser with no account. Decionis is self-serve: install read-only Shadow Mode on your own store first, then turn on enforcement in one click — no demo required.
Protocol
What the decision layer is, and what it returns.
- Why doesn't approving every AI agent action work?
- Because at volume, approving stops being a decision. Anthropic measured that Claude Code users approve 93% of permission prompts, and shipped classifiers specifically to cut permission fatigue (Anthropic Engineering, 25 March 2026). A separate 40,000-run study by Scale X found people missed 1 in 3 genuine threats while clicking through, and 7% approved every prompt they saw. That leaves two bad escapes — approve everything by hand and get nothing done, or skip permissions and hope. Policy-based gating is the third option: your policy answers in under 120ms on the common path, and a named person is pulled in only when your rules require one, so the approvals someone does see are rare enough to deserve real attention.
- Who gave Decionis the authority to stop an action?
- You did. Decionis holds no policy of its own. It evaluates your organisation's policy — authored, approved, and versioned by your team, with the author barred from being their own approver — against each intended action at runtime. When your rules require a person, a named human in your organisation approves. Decionis has no opinion about what should be allowed; it applies the decision you already made, and proves afterwards which version of your policy was in force.
- How is this different from logic my own engineers could write?
- Any team can write a check inside one service. What is expensive is everything around it: policy authored and versioned outside the application, evaluated identically across every surface an action can leave from, maker-checker approval, a named human in the loop when the rules demand one, and a signed record anyone can verify afterwards. Decionis is the permission step as infrastructure, not business logic living inside a single app.
- What does Decionis do?
- Decionis is an inline, deterministic control plane that decides whether a high-stakes action is safe before it executes. In commerce it stops coupon-stacking, price-drift, and rogue-agent margin leakage and prevents multi-channel over-selling at checkout in under 120ms; the same control plane governs payments, ERP updates, ITSM changes, and AI-agent actions. It returns a proceed, hold, block, or escalate verdict and packages the proof into a signed Decision Dossier that links into a Decision Chain and Execution Ledger.
- What is the Decionis authority lifecycle?
- The Decionis authority lifecycle is Decision Dossier, Decision Chain, Execution Ledger, Override Dossier, Policy Drift, and Policy Evolution. It turns one certified verdict into durable institutional memory instead of leaving critical decisions scattered across logs, tickets, and screenshots.
- How does Decionis handle overrides and policy drift?
- Decionis treats overrides as controlled evidence. The original Decision Dossier remains intact, the exception is linked as an Override Dossier, and override patterns become Policy Drift signals that inform governed policy evolution.
- How is Decionis different from Guardrails AI, Lakera, or LangChain Guardrails?
- Guardrails AI, Lakera, and LangChain Guardrails focus on LLM safety, prompt controls, runtime protections, or agent behavior. Decionis operates one layer closer to business execution: it evaluates institutional policy against intent and signals, then decides whether a real-world action can proceed.
- Does Decionis only work for e-commerce checkout, or can it govern other workflows?
- Checkout margin protection is where Decionis runs live in production today — and it is not the limit. The same deterministic gate — the Universal Action Gate — governs any point of execution through a single API or webhook call, with no native integration required. Beyond checkout, it applies to vendor deals and procurement commitments, visa and eligibility submissions, and code deploys or infrastructure changes (for example, blocking a hard policy violation before a config change applies). Related verdicts link into a multi-workflow Decision Chain for cross-domain accountability. Checkout is live today; the other domains are deployable policy patterns on the same gate.
Commerce
The production wedge: margin, discounts, inventory.
- How does Decionis stop coupon and discount stacking at checkout?
- Decionis enforces a hard, cost-basis-aware margin floor inline at checkout. When stacked or unauthorized discounts would push an order below the floor, the order is blocked before the checkout token is issued — in under 120ms — and the decision is recorded as a signed Decision Dossier. Unlike native Shopify discount rules, it computes net margin against a verified cost basis and fails closed.
- How does Decionis prevent overselling the same item across Shopify and eBay?
- Decionis validates live inventory at the millisecond of checkout and halts double-sales before the order commits, so the same last unit cannot sell on two channels at once. This protects marketplace seller ratings — for example, keeping eBay out-of-stock cancellations below the Top Rated Seller defect threshold.
- What is a checkout margin floor or margin guardrail?
- A margin floor is a hard, deterministic minimum-profit rule enforced inline at the point of sale. Decionis intercepts each order, computes net margin against your live cost basis, and blocks or restrains any order that breaches the floor in under 120ms — then signs a tamper-evident Decision Dossier as proof.
Developers
Where you call it from, and what it integrates with.
- How does Decionis fit into a Google Cloud or Vertex AI stack?
- Decionis fits as a thin Vertex AI Extension or ADK tool surface that forwards agent intent into Decionis Protocol for the actual governed decision. Google Cloud and Vertex AI stay in the intelligence and distribution layer while Decionis preserves deterministic policy checks, human approval, kill switches, and audit-grade Decision Dossiers.
- What systems does Decionis integrate with?
- Decionis can sit across Slack, Microsoft Teams, Power Automate, Salesforce, ServiceNow, Google Cloud, Vertex AI, Jira, ERP systems, and API or webhook-driven enterprise workflows while keeping one policy boundary before execution.
- Can Decionis turn existing policy documents into executable policy?
- Yes. The policy draft endpoints take unstructured sources — PDFs, JSON, XML, transaction and audit logs, uploads — plus live policy-source connectors for Jira, Confluence, Notion, Google Drive, Git repositories, and SAP, and return either a reviewable strategy draft or an executable policy pack. Every synthesized rule is validated through the rules compiler before you see it; clauses that cannot become executable predicates come back as review items instead of broken rules, so you review, edit, and finalize rather than transcribe.
- What ERP and commerce systems does Decionis integrate with, and does it support NetSuite?
- Decionis governs commerce and workflow surfaces including Shopify (live), eBay (live), SAP (live), WooCommerce (live), Amazon, BigCommerce, Adobe Commerce, Shopware, Walmart, TikTok Shop, plus Slack, Microsoft Teams, ServiceNow, Salesforce, and GitHub — the full consolidated catalog with per-connector readiness and onboarding effort is on the integrations page. For ERP and systems of record, SAP is live and any backend — including NetSuite, Dynamics, and custom ERPs — is supported today through the ERP & webhooks path, which cross-verifies cost basis and inventory. A deeper native NetSuite connector is on the roadmap.
Security & compliance
What a reviewer needs before this can be adopted.
- Is Decionis legitimate and trusted for high-stakes execution?
- Yes. Public trust signals include Microsoft ISV Partner status, NVIDIA Inception participation, public docs and quickstart flows, security and governance materials, signed Decision Dossier verification, validation packs, and org-wide and per-decision kill switches.
- Does Decionis allow autonomous execution in regulated workflows?
- Yes. Decionis supports autonomous execution with policy gates, while still blocking, escalating, or restraining gray-zone decisions and exposing kill switches when teams need to halt execution immediately.
- How do I get my security and compliance team to approve Decionis?
- Decionis publishes the review path so security teams can evaluate it before a diligence cycle: the Trust Center states certification posture plainly (SOC 2 and GDPR formalization in progress, ISO 27001 planned, EU AI Act Art. 12 mapped); the Governance Controls page documents the Governor Layer — maker–checker policy approval, RBAC, OIDC/SAML SSO, signed audit trail, and kill switches; the Governor Playbook walks the lifecycle step by step with the SOC 2 / ISO 27001 control each step produces evidence for; and the sandbox generates a real Ed25519-signed Decision Dossier a reviewer can verify without an account. Nothing in Decionis requires enforcement authority to start: Shadow Mode is read-only.
Enterprise & GRC
How it sits beside the platforms you already run.
- Why choose Decionis over ServiceNow IRM or IBM OpenPages?
- Choose Decionis when your team needs confidence before a high-stakes action happens, not only documentation after the fact. ServiceNow IRM and IBM OpenPages are broader GRC platforms, while Decionis is optimized to sit in the execution path and return one signed recommendation before money moves or system state changes.
- What tradeoffs should a buyer understand versus ServiceNow IRM or IBM OpenPages?
- Decionis is a specialized execution authority, not a full replacement for enterprise GRC suites. ServiceNow IRM and IBM OpenPages are broader for program management, control administration, and enterprise risk workflows, while Decionis is narrower and stronger at deterministic pre-execution enforcement with signed audit artifacts.
- Can Decionis keep Microsoft Teams and Power Automate while adding Google Cloud or Vertex AI?
- Yes. Teams and Power Automate can remain workflow surfaces while Google Cloud and Vertex AI handle intelligence. Decionis stays in the execution path, returns one certified verdict, and keeps the Decision Dossier, validation pack, and approval proof model intact across both surfaces.
- Who approves a policy change in Decionis, and how does it fit our GRC program?
- Policy in Decionis is versioned and promoted through a maker–checker path: a material change is an explicit new version with its author, approval path, and effective window preserved, so a change can be proven to have followed the approved path (SOC 2 CC8.1) rather than edited in place. Access is role-based (RBAC) with OIDC/SAML SSO, AI reasoning is separated from execution, and every verdict is an Ed25519-signed Decision Dossier. Decionis is not a full GRC suite by design — it is the deterministic gate that produces signed evidence your existing GRC program (RSA Archer, OneTrust, ServiceNow GRC) consumes. SOC 2 and GDPR formalization are in progress and ISO 27001 is planned.
Proof
How claims on this site are substantiated.
- How do I keep a record of what my team decided without anyone maintaining it?
- Records that depend on someone writing them down decay. Teams abandon architecture decision records within weeks, and the products built on that habit have repeatedly failed — the pattern is well documented. Decionis never asks for the habit: it records a decision as a byproduct of authorizing an action. Every evaluation writes a row and a signed Decision Dossier, and every policy change is a dated, attributed revision that shows what it replaced. Run the gate for a month and you have a decision record whether or not anyone maintained anything.
- Who uses Decionis today, and are there customer case studies?
- Decionis is live in production. On commerce it is on the Shopify App Store with 100+ installs governing thousands of checkout gates. Two named design partners have published case studies: Simurox, AI-assisted global mobility operations — live in under a day; CoolDeal, agentic deal discovery, charge recovery & logistics — onboarded from the API docs alone (built and operated by an affiliate of the Decionis founding team). These are verifiable onboarding-speed proofs — Decionis does not attribute a fabricated margin percentage to any customer.
- How does Decionis prove the margin loss it prevents?
- Decionis reports a Governed Execution Value figure — the monetary value of the actions it evaluated before execution, including the value of blocked or restrained actions — computed from live governed decisions. The figure is gated: when the trailing-window sample is below a public-render threshold, the site shows an early-seed-cohort status instead of a number, so the prevented-loss figure is never fabricated. The full accounting method is published on the prevented-loss methodology page, and any team can model its own payback in the ROI calculator.
Still not answered?
The fastest answer is usually the product itself: the sandbox returns a real signed verdict without an account, and Shadow Mode answers “what would this have done to my traffic?” better than any paragraph here can.