Your hardware does the work.
The cloud keeps the score.
Aiva splits cleanly into a local tier that runs agents and a cloud tier that keeps everything durable, synchronized, and reachable from anywhere.
Small events up, durable state down
Agents emit compact events. The cloud projects them into typed, durable workspace state your UI can trust after any refresh, reconnect, or outage.
Live where it matters
Transcript deltas, turn status, and approvals stream live from the agent through the bridge to your browser — no polling, no refresh.
Durable where it counts
Sessions, transcripts, queued prompts, unread state, settings, and approvals are persisted in the cloud — so what you see after a refresh is what actually happened.
Large payloads on demand
File contents, full diffs, and archives are fetched through the bridge only when you ask for them — they are never streamed or stored as events.
What runs on your machine
- Agent API on localhost — sessions, runtime control, files, git, queues, approvals
- Worktrees and cached repository copies under your own storage
- Runtime integrations and credentials — Claude, Codex, Cursor, Grok, OpenCode
- Bridge client maintaining one outbound connection to the cloud
What runs in the cloud
- Workspace and session state, projections, and background workers
- The Blazor control plane you open from any browser
- Source-control, CI, and project-management integrations
- An MCP server that gives agents signed access to cloud operations
Connect your first machine
One bridge process is all it takes to make your hardware reachable from the cloud control plane.