The boundary is the customer’s decision
PDICON Intelligence is designed for three deployment postures: a managed environment for early design partners, a private single-tenant environment for customers with strict isolation requirements, and self-hosted execution where data residency or contract terms require the workload to remain inside customer infrastructure.
How it works
Every stage says what it includes and whether it is available today.
Fastest route to validating one procurement workflow with an agreed evidence scope.
Single-tenant environment for organisations that require dedicated isolation and retention control.
Sensitive inference and training executed inside customer infrastructure.
A consultancy may accept a managed environment, while an operator under confidentiality or residency obligations will require execution inside its own infrastructure. Both must be supported without redesigning the product.
Because applications request a capability rather than a hard-coded provider, the same workflow can run against a hosted model or a self-hosted runtime according to policy.
Before capture begins, the agreement defines retention, export format and deletion. A platform that cannot be exited cleanly should not be trusted with project evidence.
Operating matrix
The matrix separates source evidence, intelligence work, governing authority and the resulting artifact.
| Subject | Input | Intelligence operation | Human / policy control | Output |
|---|---|---|---|---|
| Managed | Pilot workflow evidence | PDICON-operated processing | Contractual scope limits | Fast validation |
| Private tenant | Enterprise project data | Dedicated environment | Customer retention policy | Isolated operation |
| Self-hosted | Restricted data | In-boundary execution | Customer infrastructure control | Residency compliance |
| Exit | Accumulated evidence | Export and delete | Written exit terms | Clean handover |
Controlled sequence
Each transfer preserves context, ownership and the human gate required before consequential action.
Design boundary
Credibility begins where automation stops and accountable professional judgment starts.
Managed pilots are the current route; private-tenant and self-hosted deployment are declared plans.
Scoped workloads do not silently call external inference services.
Export format and deletion terms are agreed before capture begins.
Questions answered
Open a question to inspect the operating position, not a marketing promise.
That is a declared plan supported by the model-routing design, and it is agreed contractually rather than presented as already generally available.
Retention, export format and deletion are agreed in writing before capture starts, so exit is a defined process.
Get started
Bring a workflow your team already repeats. We define the evidence, the approver and the outcome to measure, then instrument it end to end.
We are working with a small number of design partners across engineering and procurement workflows.