Single path
Prompts, completions, tool calls.
Model Gateway
One path. No side door.
Every prompt, completion and tool call is addressed through the Model Gateway. You choose which model class may answer which data class. There is no side door to a public endpoint.
Before weights
Policy sees the request first.
Class routing
Which model may see which data.
Closed
No public inference endpoint.
What the Gateway enforces
Receive
The application sends a prompt or tool call. Nothing bypasses the Gateway.
Inspect
Policy, DLP and RBAC decide whether the call may proceed, and with which model class.
Serve
The Foundation runs the allowed model. Completions return on the same path.
Record
The audit log writes what was asked, which model answered, and which policy fired.
On the path of every call
Prompt path
Applications do not speak to weights directly. The Gateway is the address.
Tool calls
AgentLab actions go through the same path as a DocxIntel ask.
Model class routing
Vision, LLM, embeddings, reranking, assigned by policy, not by the caller.
No public endpoint
There is no BizfyLabs-operated URL in the path, because none was built.
Disconnect still works
Pull the cable. The Gateway still mediates. Audit still writes.
Same install
DocxIntel and AgentLab share the Gateway. Two apps, one control point.
Gateway controls
Ingress
- Application calls
- Internal chat
- Private API
- Scheduled runs
Every surface addresses the Gateway. None addresses the weights.
Decision
- Policy match
- DLP
- RBAC
- Model class
Allow, deny, or route to a human queue before inference.
Serving
- Open weights
- On your hardware
- No vendor endpoint
- Licence files on disk
The model that answers is one you already control.
Egress of record
- Immutable log
- Policy decision
- Model version
- Caller identity
What ran is written where it ran.
Why a single path matters
One path. No side door.
Side doors are the risk
A feature that calls a public model is a perimeter hole. The Gateway is how that hole is not designed in.
Applications stay thin
DocxIntel and AgentLab do not each invent their own policy engine.
Audit is in the path
If logging is optional, it will be skipped. The Gateway makes it structural.
Offline is the base case
A gateway that requires SaaS to function is not a gateway you can air-gap.
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.