Bring your own - subsystem options

Karta ships a managed option for every subsystem of the platform, with a bring-your-own path next to it. Use the managed option to get to production fast; bring your own where your stack, contracts, or compliance require it. This page maps each subsystem to its documentation.

Build

Subsystem	Managed option	Bring your own	Docs
Agent	Start from a template	Any agent folder in a supported harness format; Karta runs it as-is	Agent structure
Harness	Curated, readiness-gated versions	Choose Claude Code, OpenCode, DeepAgents, Goose, or Codex CLI; your harness config ships in your folder	Supported harnesses
Model	Platform models on Karta’s key	Your own provider key (BYOK) across `anthropic`, `openai`, `bedrock`, `vertex`, `openrouter`, `xai`, `google`; custom OpenAI-compatible endpoints and model IDs	BYOK
Tools	-	Your MCP servers and tools, declared inside the agent folder with credentials as agent environment variables	Agent structure, Skills
Surfaces	Hosted chat page and embeddable widget	Your own frontend over the session API, the React SDK, or the OpenAI-compatible adapters	Widget quickstart, Headless React, Adapters
Deploy pipeline	`karta deploy` and `git push karta`	Your own CI publishing releases; every deploy is a versioned release with rollback	Deploy loop, Releases and rollback

Run

Subsystem	Managed option	Bring your own	Docs
Observability	Console traces view for every org	OpenTelemetry GenAI export to your own backend	Observability
Audit	Immutable audit log in the console	API and CSV export into your own tooling	Audit log
Spend control	Budgets with hard enforcement	Per-end-user and per-organization caps you define	Usage and budgets
Cloud	Karta Cloud	Run the data plane in your own AWS account	BYOC

Serve your users

Subsystem	Managed option	Bring your own	Docs
End-user identity	Anonymous sessions with a public key	Your app asserts who the user is with backend-minted session tokens or verified embed identity; each user gets their own agent instance	Widget identity, Session tokens
Brand	Theme presets	Full visual and structural theming per embed key, matched to your product	Theming
Metering	Usage rolled up per organization	Usage attributed per end user, so you can see and package what every user costs	Usage and budgets

What stays constant

Whatever you swap, four things hold: each agent instance keeps its durable workspace and memory across sessions and releases; sessions and participants behave the same on every harness; every deploy is a versioned release with rollback; and tenancy boundaries do not move. Swapping a subsystem never costs an instance its files, memory, or history. For subsystems not listed here, contact [email protected].

Get started

Concepts

Agent project

The CLI

Deploy

Platform

Security

Enterprise

Tutorials

Bring your own - subsystem options

Build

Run

Serve your users

What stays constant

​Build

​Run

​Serve your users

​What stays constant

Build

Run

Serve your users

What stays constant