Cleetus Core

Cleetus Core

The host behind Cleetus.

Give your agents a place to work. Core runs on the computer you choose, checks each request and keeps the original record of what happened.

The Cleetus robot at a terminal in its workshop

Inside Core

Execution stays with the host.

The IDE, terminal and supported phone connections request operations through versioned contracts. Core owns the workspace, checks the caller’s scope and records the result. Each client has its own supported operations.

From a client to an isolated workload
Phone or CLIRequests a scoped operation
Governed meshAuthenticates the selected peer
Selected CoreChecks current scope and capacity
Linux cgroupResource accounting
NamespacesHost-side isolation
Firecracker microVMOffline guest
Codex thread

Architecture example. Client access, mesh placement and the offline guest each require their own approval. The Linux hardware proof covers the illustrated guest boundary.

Native execution

Choose a platform.

Isolation depends on the backend, the reviewed workload and what the selected machine can verify.

For developers

Build on the same contracts.

Follow one request from the organization’s policy through local review, execution and recovery.

Open Core developers