Before weights
Policy and DLP decide first.
Controls in the path
What runs between your data and the model.
Enterprise buyers ask what policies the stack enforces in process. This page is that inventory. Applications inherit these controls. They do not invent a second path.
One path
Model Gateway. No side door.
Human on write
Named approver for consequential actions.
Local evidence
Immutable audit on the same install.
How a request moves
Arrive in perimeter
Data stays in air-gap, customer tenancy or bare metal. Inference does not need a network path out.
Enter the Gateway
Every prompt, completion and tool call uses one controlled path. No public BizfyLabs endpoint.
Policy before weights
RBAC, data class, model class, DLP and allow, redact, deny or hold. Then inference or tool call.
Write the evidence
Who, what, model version, policy decision and outcome are written locally. Pull the cable and they still write.
Controls the runtime enables
Customer perimeter
Air-gapped is the base case. No required egress for inference. Nothing calls home.
Customer-held keys
Encryption keys stay with you in every tier that touches your data.
No production custody
BizfyLabs LLC licenses software. You are controller and processor. We do not hold production data.
No default training on your data
Your documents stay in your environment. No send-to-public-model path is designed in.
Model Gateway
Single path for prompts, completions and tool calls. Policy sees the request before weights do.
Policy engine
Allow, deny, redact or hold. Model class routing by rule, not by the caller.
DLP and redaction
Fields that must not leave unmodified. Redaction is logged. Originals are preserved.
RBAC
Who may invoke, who may approve, who may read the log. Named, not implied.
Human-in-the-loop
Consequential AgentLab actions wait for a named approver. Nothing silent-posts to ERP or core.
Immutable audit
Written where the workload runs. Survives a pulled cable. Fields are listed in the security pack.
Citations and confidence
DocxIntel maps fields back to source regions with confidence so a human can decide.
Open licences on disk
Apache 2.0 and MIT only. Licence text and an SBOM covering models and code ship per release.
Grouped by stage
- Perimeter
- Customer keys
- No BizfyLabs custody
- No required egress
Where data sits and who can open it.
- Model Gateway
- Policy
- DLP
- RBAC
- Model class routing
What fires before a weight sees the prompt.
- Human-in-the-loop
- Named approver
- No silent write
- Shared audit
How AgentLab inherits the same controls.
- Immutable logs
- Licence files
- SBOM
- Security pack under NDA
What counsel and security can read without a slide deck.
How to read this list
This is product capability, not a certificate wall
We describe controls the install enforces. We do not claim a government stamp you cannot verify.
Buyer regimes are why these controls exist
Health ICT rules, CBUAE outsourcing, PDPL where in scope, and free-zone data rules are why buyers need an in-path stack.
Applications stay thin
DocxIntel and AgentLab attach to Foundation. They do not each invent policy.
Deep dives live next door
Gateway, governance and deployment pages stay the detailed product pages. This page is the inventory.
The full stack on one machine, disconnected from the network.
In your office, on your documents, with the cable pulled out. No competitor's sales engineer can do this.