Product architecture
One product, three responsibilities that should not be confused
The Cockpit helps people understand and decide. The Core applies policy deterministically. The Gateway is the real point of passage for connected AI traffic.
Current DUBSAR status
The private stack is proven in stages
A private portal journey and local Gateway contracts have been demonstrated. A public multi-tenant product and general production enforcement are not yet claimed.
Product architecture
The Cockpit is the human control surface
Responsible people use the web interface to see connected scope, alerts, pending reviews, decisions and evidence. It should translate technical events into accountable business information.
The Cockpit does not enforce network traffic by itself. Its authority comes from the policies and decisions applied by the Core and Gateway.
Product architecture
The Core is the deterministic authority
The Core evaluates a versioned policy against a bounded request context. It returns an allow, deny, redact or review decision without delegating final authority to a language model.
Agents may assist with analysis, but they cannot silently replace the rule or approve their own sensitive action.
- Versioned policy
- Bounded context
- Explicit decision and reason
- Receipt tied to the authorised request
Product architecture
The Gateway makes the decision real
A selected workflow changes its AI endpoint so the request reaches DUBSAR first. The Gateway asks the Core, applies any authorised transformation and only then forwards the request to the approved provider.
If a flow bypasses the Gateway, DUBSAR cannot claim to have controlled it. That boundary remains visible in the Cockpit and documentation.
Frequently asked questions
What to know before going further.
Is the Gateway the whole DUBSAR product?
No. It is the enforcement point. The product also includes discovery, deterministic policy, human oversight, evidence and the Cockpit interface.
Do customers need a Windows desktop application?
No for the first web product. A technical desktop may be reconsidered later, but it is not required for the current Cockpit-and-Gateway journey.
Read next
Continue with another DUBSAR guide.
The portal remains in private testing. These guides explain what DUBSAR is proving — and what it does not yet claim.