What is Kibotos
Kibotos gives AI Agents WorkspacesA complete Linux environment for an AI Agent, running in its own MicroVM. Agents read and write files, run processes, and start services in it without affecting the host or other Workspaces.: complete Linux environments, each running in its own MicroVM. You create, use, and delete Workspaces through an API, and the deployer runs them on their own Linux hosts.
Overview
Inside a Workspace, an Agent reads and writes files, runs commands and long-running processes, opens a terminal or a desktop, starts services, and delivers its results. None of this can affect the host or any other Workspace, and you never need to know which machine a Workspace runs on.
Kibotos is currently in an internal production trial. To see which interfaces carry compatibility commitments and how changes are announced in advance, see Guarantees and limits.
What a Workspace provides
- Files: upload, download, list directories, move, delete, and watch directories for changes. See Uploading and downloading with kibo and data-plane services.
- Processes and terminals: run commands or long-running processes, reconnect after a disconnect and receive the missed output, and open interactive terminals. See Commands and terminals.
- Persistent volumes: a VolumeA persistent volume that exists independently of any Workspace. A Workspace binds at most one Volume, mounted at /data by default. stores data independently of any Workspace and can be bound, rebound, and expanded. See Volumes.
- Desktop: a Workspace with a graphical interface that you view and operate in a browser. See Desktop.
- Services: connect from your machine to a port inside the Workspace, or serve it to others through a public URL. See Port forwarding and Public URLs.
- Network control: allow or deny outbound traffic by destination, send it through your own proxy, and choose your own DNS servers. Your own proxy and DNS servers require a
v0.3.0or later deployment. See Network policy. - Lifecycle: stop and start, set an expiration time, and adjust CPU and memory. See Expiration and Adjusting resources.
- Export and restore: export a Workspace to an archive, then import and restore it elsewhere. See Export, import, and restore.
Every Workspace is created from a TemplateThe system image a Workspace is created from, such as a minimal system, a programming toolchain, or a desktop environment.. The Template determines what comes preinstalled in the Workspace, such as a minimal system, a programming toolchain, or a desktop environment. The deployer publishes the available Templates.
Ways to connect
| Method | Suited for | Details |
|---|---|---|
kibo command line | Manual operations, scripts, and troubleshooting | kibo CLI |
| Go SDK | Go programs that need the full feature set. It handles certificates, retries, and data-plane credentials | Go SDK |
| Native API | Programs in other languages that need the full feature set and compatibility commitments | API overview |
| E2B SDK | Programs already written against the E2B SDK, switched over without code changes | E2B compatibility |
kibo, the Go SDK, and the native API use an Operator identity issued by the deployer. The E2B SDK connects through an E2B gateway that the deployer runs, using the gateway's API key.
Here is the same task, creating a Workspace and running a command in it. The Go SDK makes the native API calls for you; see examples/go/quickstart.
workspace_id=$(kibo workspace create --template "$template_id" -q)
kibo workspace exec "$workspace_id" -- /bin/echo ready
kibo workspace delete "$workspace_id"The E2B gateway covers the basic E2B capabilities and returns an explicit error for anything it does not provide. See E2B compatibility. For capabilities unique to Kibotos, such as rebinding a Volume or a caller-owned egress, use the native API or kibo.
Unsuitable use cases
Some workloads need capabilities that Kibotos does not currently provide, such as keeping memory state across a stop and start. Check Not currently provided before you choose Kibotos.
Next steps
- Quickstart: create your first Workspace in a few minutes, run commands, and transfer files.
- Core concepts: Workspaces, Templates, Volumes, and states.
- Architecture: which components your requests pass through, and how that affects the way you call Kibotos.
- Guarantees and limits: which data is kept under which conditions, and what you see when something goes wrong.
- To deploy Kibotos yourself, start with Installation.