Documentation
On-premise and legacy systems
Many business systems cannot be reached from the internet. That is why some TeraBrain NX nodes run on a company machine, next to the systems they need to talk to.
No openings to the outside
The code runs where the systems are, so there is no need to expose them.
Ideal for software houses
Bring agentic features into software already installed at customers.
How it works
TeraBrain NX
- Agents
- Governance
- Logs
Company machine (site)
- Connector at your site
- Machine at your site
Local systems
- ERP
- Databases without a public address
- Shared folders
- Legacy applications
- Register the machineIt is added as a site in the organization's Sites section, by installing the TeraBrain NX agent on the machine.
- Choose the nodeConnector at your site for TypeScript functions close to the systems, Machine at your site to run commands and read files.
- Write the functionsAs in a normal connector: every exported function becomes a tool.
- Connect to the agentsAs with any tool, with the privileges needed and no more.
The two nodes
- Connector at your site. Node.js runs on the machine and the code is kept in the platform's repository. It is for an ERP on the local network, a database without a public address, a shared folder.
- Machine at your site. Runs commands and reads files on a machine of your own: a Linux server or a Windows PC (sh or cmd shell).
Related pages
Code and integrations
TypeScript connectors, sandboxes, remote and hosted MCP servers: how to connect agents to business systems.
Security
Roles, groups, credentials, enterprise sign-in and least privilege: how to protect an agent system.
Governance and audit
Versions, rollback, activity log and tracing of every conversation: knowing what agents do.
Have an agent to take to production?Letβs talk.
We show you TeraBrain NX on your case: systems to connect, access and controls.
