karta
// platform · the modern agent stack

Karta Platform.

Pick any model, compute, and harness. Karta operates the two layers above them: the Agent Cloud that runs your agent, and the Agent Productization layer that ships it to users and manages the fleet. Every subsystem has a managed option, or bring your own.

L4
Agent Project
harness engineering
doconfigure your harness with skills, MCP, hooks, subagents
useharness-native format, e.g. CLAUDE.md + .claude/ for Claude Code
L2
Agent Compute
isolated execution
Fully isolated per-session microVMs Bring your own compute
managedprovisioned and operated by Karta
solid = available now dashed = early access - talk to us
// every subsystem

Every subsystem: managed, or bring your own.

One platform, two planes. The control plane runs the fleet; the data plane is where your agents' durable computers live - in Karta Cloud, or in your own. Around that split, every subsystem ships with a managed option and a bring-your-own path.

Control plane · operated by Karta

Console and API · identity · releases and rollback · metering, budgets, and policy

Data plane · the durable computers

Workspaces, memory, and artifacts · isolated per-session execution · model traffic

runs in Karta Cloud · or your cloud account (early access)

// constants

What never changes.

Everything above is swappable because the spine is not. Swap any layer; your agents keep their memory, their users, and their history.

The durable workspace

Every end user's files, memory, and history persist across sessions, releases, model swaps, and harness swaps.

The identity model

The specialist and the verified end user are distinct, first-class primitives. Personalization, isolation, and spend attribution hang off them.

The execution contract

Sessions, approvals, event streams, and resume behave identically across every harness.

The deployment contract

A folder in, a versioned release out, rollback always.

The metering ledger

Usage counted per end user against immutable price versions. Whoever processes the payment, the count is neutral.

The isolation floor

Per-session isolation, plane boundaries, and deny-by-default posture that do not move when layers swap.

// enterprise controls

Who owns what.

Karta provides the platform controls; you configure the boundaries for your data and users.

Control Karta provides You configure
Data isolation Per-organization data-plane isolation Which organizations and tenants are separated
Encryption Encrypted storage; crypto-shredding with per-store keys (validating with design partners) Your own customer-managed keys (validating with design partners)
Deployment Managed cloud, or run the data plane yourself (early access) Karta Cloud today; your own cloud or on-prem (early access)
Identity Verified end-user identity model Your identity provider and token issuance
Spend Multi-layered hard spend caps Per-user and per-organization limits
Audit Audit log, role-based access, approvals Review policy, export, and access grants

Run your agent on Karta.

Read the docs to bring your first agent project, or join the waitlist.