Monolith

The CLI and Fleet API for developers who deploy AI agents at scale.

monolith
|
M O N O L I T H  v0.3.0
Fleet Management CLI
| monolith deploy --fleet production --replicas 3
› provisioning 3 agents in fleet "production"
› agent-001  ready  10.0.1.4
› agent-002  ready  10.0.1.5
› agent-003  ready  10.0.1.6
✓ fleet "production" deployed (3 agents, 4.2s)
| monolith status --fleet production
fleet: production   agents: 3/3 healthy   uptime: 12m
› agent-001  idle    0 tasks   mem 128M
› agent-002  active  2 tasks   mem 256M
› agent-003  idle    0 tasks   mem 134M
| monolith logs --agent agent-002 --tail 3
[14:22:01] task.start  id=t-4491  type=research
[14:22:03] tool.call   web_search "Q2 earnings"
[14:22:08] task.complete  id=t-4491  duration=7.2s
At a glance
81
API operations
13
Domains
1:1
VM-per-agent isolation
0
Secrets held by agents
Three surfaces
Same fleet. Terminal, API, or agent-to-agent.
Interface
01
CLI
Terminal-native fleet management. One command to provision, monitor, and deploy.
| monolith deploy
Programmatic
02
Fleet API
RESTful programmatic control. 81 operations across 13 domains.
POST /v1/agents/deploy
Agent-to-Agent
03
MCP Server
Any MCP-compatible client can manage fleet operations.
monolith-mcp
Design principles
Built for the operator.
One VM per agent
Each agent runs in its own LXD virtual machine — not a container, not a shared process. Kernel-level isolation with dedicated memory, networking, and filesystem. No lateral movement between agents.
Isolation architecture →
Secrets never touch agents
Agents receive placeholder credentials. A gateway proxy intercepts outbound requests and injects real secrets at call time. Agents call tools through MCP server interfaces — they never hold, see, or log actual keys.
Secrets model →
API-first, always
Every CLI command maps to a Fleet API endpoint. 81 operations across 13 domains — agents, fleets, deployments, logs, health, config, secrets, tenants, environments, tasks, tools, metrics, and auth. No hidden surface.
API reference →
Observable by default
Every agent action is logged. Every tool call is traced with input/output capture. Every token is counted with per-agent cost attribution. Structured logs, not string dumps — queryable from day one.
Observability →
Get started
Install Monolith. Deploy agents.
quickstart
# install
| curl -fsSL https://thisismonolith.com/install.sh | sh

# deploy locally
| monolith deploy --fleet dev --replicas 1
✓ fleet "dev" deployed (1 agent, 3.1s)

# or deploy to FleetOS for managed infrastructure
| monolith deploy --fleet production --target fleetos --replicas 3
✓ fleet "production" deployed (3 agents, 4.2s)

Monolith is free. Run agents on your own machine or deploy to FleetOS for managed infrastructure with VM isolation, secrets management, and observability built in.

Read the docs GitHub FleetOS