Governed connections, not a raw credential in the request.
The platform composes tools, capabilities and connections: MCP, REST, SQL, GitHub, SSH, Ansible, Terraform, WinRM/PSRP and other deployed connections. Calls go through organization policy and sensitive credential references.
How connections work
Core tools, with extras when the account has them and they are deployed.
Tools and connections
Admin registers connections and publishes them as tools or MCP capabilities instead of pasting keys into an agent instruction.
MCP and REST
Upstream MCP servers and REST/SQL endpoints can be bound as governed tools on the same execution layer.
Ops connections
GitHub, SSH, Ansible, Terraform, WinRM/PSRP, VPN and data connections — used by automated processes, not as a shell on the laptop.
SSH
Allowlisted command profiles and tunnels. Not a free remote shell.
Ansible
Allowlisted playbooks, workspaces and optional AWX jobs.
Terraform
Allowlisted modules for Proxmox VMs, stack deploy/upgrade and environment prep — validate, plan, apply.
WinRM / PSRP
Governed Windows connections. Not a free remote PowerShell.
VPN
IPsec, SSTP or WireGuard path to private hosts. Download client profiles for iPhone, Android, Windows and Ubuntu from admin.
GitHub
PAT or GitHub App as a governed connection for operational processes.
SQL, REST, GraphQL
Data connections become tools after validation. Secrets stay on the connection.
Policy on the call
Organization, role, access and connection rules still apply before the tool runs.
Ready to move beyond the chatbot?
Build AI that understands your business, works with your knowledge, follows your processes and can actually finish the job. You decide which actions are allowed, when a person must step in and how much AI usage your organization can consume.