What is Decionis, in plain terms? #1
|
A question we hear from nearly every engineer who first looks at the project: what does Decionis actually do? Is it an approval workflow, an audit log, a policy engine — or something else? Capturing the answer here so it's easy to find. |
Replies: 1 comment
|
Decionis is a software control plane for high-stakes executions — a control-and-prevention mechanism that sits with your runtime the way BIOS sits with a computer. Think of it as a master agent that manages approval of actions autonomously and produces unit evidence for every decision, called a Decision Dossier. The clearest way to see it is a banking-hall scenario:
The rules behind steps 4–6 are policies, and in most organizations they live half in the manager's head and half scattered across files on desks, Jira, GitHub, Word documents, and PDFs. Decionis encodes those policies and versions them, then combines the work of the teller, the branch manager, and the auditor into one control plane. It automatically evaluates policy against an intent (the withdrawal) and decides whether to allow, block, or escalate — and it produces tamper-proof dossier evidence showing what, who, when, and in which context, ready for auditors to review. Banking is just the walkthrough. The same mechanism applies to e-commerce, HR, medical systems — anything that involves changing a sensitive record. Related: Where Decionis sits in the stack · How policies are managed and versioned · How Presence relates to Decionis Have a different architecture or integration question? Start a new discussion — we answer publicly whenever we can. |
Decionis is a software control plane for high-stakes executions — a control-and-prevention mechanism that sits with your runtime the way BIOS sits with a computer. Think of it as a master agent that manages approval of actions autonomously and produces unit evidence for every decision, called a Decision Dossier.
The clearest way to see it is a banking-hall scenario: