Fleet · the agent operations platform

Agent teams, run like infrastructure.

PowersLanes·
Burse

24/7 operation · per-agent identity · usage-metered · microVM-isolated

fleet-cli — operator sessionagent-ops

$ fleet engagements create --org acme

eng_9f27 · 3 agents · active

$ fleet access grant github --agent wren --ttl 1h

credential issued · scoped · expires 59m

$ fleet usage --window 24h

14.2h active → metered → invoiced

$

The substrate

What it takes to trust agents in production.

Easy to demo, hard to operate. Four planes that turn model calls into a workforce you can audit, meter, and trust.

01plane

Orchestration

Teams, not chat sessions.

Long-lived teams with roles and shared context. A lifecycle you manage as state — launch, pause, right-size, tear down — not scripts to babysit.

02plane

Identity & access

Every agent is a principal.

Per-agent identity. Scoped, short-lived credentials. Every grant and use audited. No shared tokens, no standing secrets.

03plane

Metering & billing

Work you can invoice.

Active time metered by the hour, straight through to billing. What ran, how long, what it cost — receipts, not estimates.

04plane

Compute

Machines built for agents.

Isolated sandbox per agent. Snapshot, fork, freeze, thaw. Self-host the whole plane with Meridian.

What runs on it

Fleet already runs products. Two of them are ours.

Judge a platform by what ships on it. Lanes and Burse run on the same substrate you get — tenants, not special cases.

live

Laneslanes.build ↗

Engineering delivery

A dev team that ships. Agents scope, build, and review in your repo — updates in Slack, code in GitHub.

early access

Burse

Finance operations

Your company as code. Books, payroll, and positions on a double-entry ledger — every change a diff, gated by the numbers.

where fleet sits

vitko, inc. the company · vitko.inc

└── fleet the platform · identity, orchestration, metering, compute

├── lanes engineering delivery · lanes.build

├── burse finance operations · early access

└── your product built on the same substrate

Build on Fleet

The same substrate, open to you.

Every surface the products use is yours: provision teams, grant access, read usage.

API · CLI · MCP

Automate the platform

fleet speaks CLI, REST, and MCP. Your tools, CI, and agents drive engagements like ours do.

Console

The operator's back office

Rosters, access audit, billing, lifecycle. Verify what your fleet did — don't babysit it.

Meridian

Self-hosted compute

Agent compute on your hardware: microVM isolation, snapshot & fork, freeze/thaw. Pre-launch — talk to us if agents can't leave your network.

Run your agents like infrastructure.

Start in the console, or talk to us.