Build
Chat, canvas or code. Same artefact.
AgentLab
Agents on an install you already have.
AgentLab lands on Private AI Foundation you already run. Same Gateway, same audit, same perimeter. If you do not have that install yet, start with a DocxIntel proof of value.
Connect
Systems already inside the perimeter.
Observe
Traces, steps and exact failure points.
Control
Approvals, versions, rollback.
How an AgentLab action runs
Build
Describe the agent in chat, wire it on a visual canvas, or construct it in code and API.
Connect
Connector catalog, MCP tools and custom APIs into systems of record you already run.
Approve
Consequential tool calls wait for a named approver. Nothing silent posts to ERP.
Write
The outcome, model version, caller and policy decision are written to the Foundation audit log.
A private agent workspace
Build
Chat, visual canvas or code. All three produce the same versioned artefact: workflows, prompts, skills and tools.
Connect
Connector catalog, MCP tools and custom APIs. No public endpoint is required.
Context
Files, knowledge bases and structured tables stay next to the weights and the audit log.
Deploy
Private API, scheduled runs, internal chat. Inference and tools go through the Model Gateway.
Observe
Traces per run, step-by-step logs, full run history, exact failure points.
Control
Approval checkpoints, human-in-the-loop, versioned prompts and tools, rollback on exception.
Build through Control
Build
- Chat
- Visual canvas
- Code & API
- Versioned artefacts
Three paths. One object you can roll back.
Connect
- Connector catalog
- MCP tools
- Custom APIs
- No public endpoint
Agents talk to systems already inside the building.
Observe
- Run traces
- Step logs
- Failure location
- Full history
What ran, which tool, which policy decision.
Control
- Named approver
- Guardrails
- Rollback
- No self-serve signup
Sign in on an install you already run. This site does not offer self-serve signup.
Where this is different
Private first
Cloud agent platforms offer self-hosting as an option. AgentLab is a private deployment first, on a Foundation already inside the perimeter.
Same Gateway
A DocxIntel ask and an AgentLab tool call share one controlled path. There is no side door.
Regulated by design
Every action is logged, attributable and reversible. That is a constraint of the environment, not a feature list item.
Start with documents
If the Foundation is not installed yet, the proof of value starts on DocxIntel, one document type, in your environment.
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.