Loading…
Layer 4 — The surfaces
One protocol. Many ways to interact.
A surface is not an integration and not a logo — it is a place where Decionis becomes available. There are 22 of them, and they group into four families, which is a great deal easier to remember than a catalogue.
Four columns of surface, all reaching one protocol. Developer surfaces: MCP servers, SDKs and libraries, the GitHub Action, webhooks, and the sandbox. Enterprise surfaces: SAP, Salesforce, ServiceNow, Adobe Commerce, Microsoft, Walmart (in evaluation), and more. Consumer surfaces: Shield as a browser extension, with Sense on the web, mobile apps, and a macOS app planned. Learning surfaces: the Policy Exchange, documentation, examples, tutorials, and community. There are not twenty-five products; there are four families.
Developer Surfaces
For the engineers wiring agents and services to real systems. The protocol reached directly — from an agent's tool call, your own code, a pipeline, or plain HTTP. This is the shortest path from nothing to a first verdict.
MCP Server
LiveEvery tool call an agent makes can ask Decionis before it runs.
SDKs
LiveEvery function in your own code can ask Decionis before it commits.
GitHub Action
LiveEvery deployment can ask Decionis before it ships.
CLI
LiveEvery command in a terminal or a pipeline can ask Decionis before it executes.
Webhooks
LiveEvery system you already run can ask Decionis over plain HTTP.
Zapier, Make & n8n
LiveEvery automation step can ask Decionis before it fires.
Enterprise Surfaces
For the systems of record that already run the business. The protocol reached from inside the platform where the action originates — checkout, ERP, CRM, HR — so the check happens in the execution path rather than beside it.
Shopify
LiveEvery checkout can ask Decionis before the order is accepted.
eBay
LiveEvery listing, order and promotion can ask Decionis before it goes live.
SAP
LiveEvery vendor payment and purchase order can ask Decionis before it posts.
Amazon
BetaEvery price change and order can ask Decionis before it reaches the buyer.
ERP & Webhooks
LiveEvery system of record can ask Decionis without changing how it runs.
Workday
BetaEvery payroll run and HR business process can ask Decionis before it commits.
BigCommerce
BetaEvery headless checkout can ask Decionis before it captures payment.
Adobe Commerce
BetaEvery Magento order can ask Decionis before it clears.
Salesforce
BetaEvery Flow, Apex and Agentforce action can ask Decionis before it fires.
Consumer Surfaces
For individuals holding authority over their own transactions. The same protocol, pointed at decisions a person makes for themselves rather than ones an enterprise makes at scale.
Learning Surfaces
For anyone deciding whether this is real. The protocol reached in order to understand it — break it in a sandbox, fork someone else's policy, read the reference implementation.
Sandbox
LiveTry to break the protocol — overspend, bypass approval, delete production — and watch it hold.
Policy Exchange
LiveFork a decision recipe someone else already runs instead of authoring policy from scratch.
Open Reference Implementation
LiveRead the protocol schemas, policy packs, MCP samples and starter kits in the open.
Documentation
LiveGo from zero to a first verdict, then to a governed production surface.
One hosted protocol, many surfaces
Adding a surface does not add a policy engine. Authority is defined once and enforced everywhere, which is why the twentieth surface costs far less than the first.
One hosted Decionis Protocol at the centre, with surfaces orbiting it: commerce, ERP and finance, AI agents, pipelines, ITSM and HR, and consumer. Each reaches the same protocol, so authority is defined once and enforced everywhere rather than re-implemented per system. The hosted layer is highly available, low latency, secure by design, and enterprise ready. Decionis is a neutral layer across clouds, regions, and systems.
Surfaces are not connectors
Surfaces are where people encounter Decionis — Shield, the sandbox, the governance console, MCP, the GitHub Action.
Connectors are how systems reach the protocol — webhooks, Zapier, Make, n8n, Shopify, SAP, Salesforce.