Use cases
Use cases
What teams use bastn for: fleets without SSH, internal tools as agent tools, approvals, audit.
Let an AI agent manage a VM fleet without SSH access
Give an ops agent named, typed actions on 100 hosts instead of SSH keys or a shell. One outbound connector per host runs the actions you approved.
ReadTurn any CLI or script into MCP tools without writing an MCP server
Describe a CLI once and serve it as typed, validated MCP tools, with a different set per agent and a connector on the host that runs the approved actions.
ReadGive an on-call AI agent read-only access to every host
Let an agent read logs, service status, disk, memory and network on your fleet with the read-only Linux pack. Nothing it can call changes a machine.
ReadLet an AI agent fix things, with you approving each risky call
Give a remediation agent restart and other write actions on your hosts. Destructive calls are held until you approve them, with the exact host and arguments in front of you.
ReadGive AI agents your internal APIs as tools
Import an internal service's OpenAPI spec and serve its operations as typed MCP tools, with a different set per agent and the service credentials kept off the agent.
ReadPut the MCP servers you already run behind per-agent policy
Front the internal MCP servers you already run with bastn. Each agent gets its own key and its own tool list, new tools wait for review, and every call is audited.
ReadLet an AI agent write a script, and run it only after you review it
When no action fits the job, an agent can submit a script. It is held for review, approval pins its hash, and the connector re-checks the hash before every run.
Read