What Kind of Platform Is QuNetra?
Where QuNetra fits in the enterprise technology stack — and how Decision Infrastructure relates to middleware, iPaaS, BPM, workflow automation, decision systems, and AI governance.
QuNetra is delivered as software and integrates with the systems you already run, so it is easy to file it under a category it only resembles. This page draws the line precisely.
Placing QuNetra precisely
Category
Position
Between Decision Systems and Execution.
Delivery models
Adjacent categories
QuNetra resembles the adjacent categories but is equivalent to none of them. Category, delivery model, and architectural position are different dimensions — this page keeps them separate.
The Short Answer
QuNetra is a Decision Infrastructure platform.
It governs whether decisions remain admissible, executable, and accountable at the moment of action.
Decision Infrastructure is the category. QuNetra is the platform implementation of it. For the company-level introduction, see What Is QuNetra?
Category vs Delivery Model
A category is not a deployment model.
CRM is a category.
Salesforce is a platform.
SaaS is a delivery model.
Decision Infrastructure is the category.
QuNetra is the platform.
SaaS, private cloud, or customer-managed are delivery models.
Where It Sits
QuNetra operates at L6 — between the systems that produce decisions and the moment those decisions become irreversible.
L5 · Decision Systems
Produce and route the decision.
ServiceNow, Pega, Appian, FICO, Salesforce, loan origination systems
L6 · Decision Infrastructure
QuNetra — governs whether the action may execute now.
Execution
The action commits and becomes consequence.
L7 · Consequence Intelligence
Learns from the outcomes of governed execution.
See the full placement on Where Decision Infrastructure Fits.
How QuNetra Differs
QuNetra is adjacent to several familiar categories, but equivalent to none of them. Each does a different job; QuNetra governs the act.
Full category comparisons: vs Middleware, vs iPaaS, vs BPM, and vs Workflow Automation.
How QuNetra Is Deployed
QuNetra is integrated into existing environments. It does not ask you to migrate or replace anything.
- integrated into existing environments through standard enterprise integration
- does not replace systems of record, decision systems, or workflow platforms
- operates at the execution layer, in the path of the consequential action
- evaluates runtime admissibility against current state, authority, and policy
- returns a verdict on each action, with evidence captured in line
How QuNetra Is Consumed
QuNetra is consumed as an enterprise platform that integrates with existing systems and evaluates actions at execution time. Organizations typically deploy it incrementally — beginning with a single workflow, decision type, or execution boundary before expanding to broader governance coverage.
How QuNetra Is Bought
Organizations adopt QuNetra to reduce execution risk, governance gaps, and policy drift between approval and action.
The buyer is rarely solving a connectivity or workflow problem — those are typically already handled. They are solving the problem of decisions that were approved correctly but executed under conditions that had since changed: the decision-to-execution gap. Deployments start narrow — a single workflow or segment — and expand as the evidence and governance value compound.
Decision Systems determine what should happen.
Decision Infrastructure determines whether it may happen now.
Consequence Intelligence learns from the outcomes of governed execution.
Frequently Asked Questions
Is QuNetra middleware?
No. Middleware connects applications and passes messages between them; QuNetra governs whether the action a message triggers is admissible at the moment it executes. They operate at different layers — transport versus control. See Decision Infrastructure vs Middleware.
Is QuNetra SaaS?
QuNetra can be delivered as SaaS, private cloud, or customer-managed deployment depending on operational and regulatory requirements. SaaS is a delivery model; Decision Infrastructure is the category. QuNetra is a Decision Infrastructure platform.
Is QuNetra iPaaS?
No. iPaaS connects systems and moves data between them; QuNetra governs whether the action moving between those systems should execute. Connectivity is not control. See Decision Infrastructure vs iPaaS.
Is QuNetra BPM?
No. BPM models and orchestrates processes and moves work to the action; QuNetra governs whether that action is admissible when it commits. Orchestration is not governance. See Decision Infrastructure vs BPM.
Is QuNetra AI Governance?
No. AI Governance defines what models are allowed to do; QuNetra enforces whether those permissions still hold on each individual action at execution. AI Governance sets the rules upstream; QuNetra governs the act.
Is QuNetra a decision engine?
No. Decision engines determine outcomes, recommendations, risk scores, or next-best actions. QuNetra governs whether those decisions remain admissible at execution. Decision engines determine what should happen; QuNetra determines whether it may happen now.
Is QuNetra a system of record?
No. Systems of record remain authoritative. QuNetra reads the state, policy, authority, and signals it needs from existing systems and returns execution verdicts. It governs execution without becoming the authoritative source of business data.
Where does QuNetra sit in the enterprise stack?
QuNetra operates between Decision Systems and consequential execution. Decision Systems produce and route decisions. QuNetra evaluates runtime admissibility and returns Allow, Hold, Deny, or Escalate verdicts before execution occurs. This position is often referred to as the L6 Decision Infrastructure layer.
Does QuNetra replace my existing platforms?
No. QuNetra does not replace systems of record, decision systems, or workflow platforms. It integrates into existing environments and operates at the execution layer, returning Allow, Hold, Deny, or Escalate verdicts — with evidence — on the actions those systems take.
Reference Surfaces
Reference Surfaces
Understanding a category requires more than comparisons. These reference surfaces explain the core concepts, architecture, vocabulary, and placement of Decision Infrastructure within the enterprise stack.
Definition
What Is Decision Infrastructure?
The canonical introduction to the category. Defines Decision Infrastructure, execution governance, runtime admissibility, and governed execution.
- Category definition
- Execution governance
- Runtime admissibility
- Governed execution
Placement
Where Decision Infrastructure Fits
Where Decision Infrastructure sits between Decision Systems and Consequence Intelligence in the enterprise stack.
- L4 Decisioning
- L5 Decision Systems
- L6 Decision Infrastructure
- L7 Consequence Intelligence
Architecture
Decision Infrastructure Architecture
The architecture that enables execution governance — how Decision Infrastructure operates across enterprise systems.
- Commit boundaries
- Runtime validation
- Execution control
- Evidence generation
Vocabulary
Decision Infrastructure Glossary
The canonical vocabulary of the category — the lexicon analysts can quote precisely.
- Runtime admissibility
- Commit boundary
- Execution governance
- Governed execution
- Evidence at action
Related Comparisons
Related Comparisons
Use these comparisons to understand how Decision Infrastructure differs from adjacent categories, systems, and governance models.
Decision Infrastructure vs Middleware
Middleware passes messages between systems; Decision Infrastructure governs whether the action a message triggers should execute.
Decision Infrastructure vs iPaaS
iPaaS connects systems and moves data; Decision Infrastructure governs whether the action between them should execute.
Decision Infrastructure vs BPM
BPM orchestrates the process and moves work to the action; Decision Infrastructure governs whether that action should commit.
Decision Infrastructure vs Workflow Automation
Workflow automation runs the sequence; Decision Infrastructure governs whether each action in it should commit.
Decision Infrastructure vs Decision Systems
Workflow-and-approvals systems exit before execution; Decision Infrastructure governs the act itself.
Decision Infrastructure vs AI Governance
AI Governance defines what should be allowed. Decision Infrastructure governs whether those permissions remain valid at execution.