Products

Organizations

Teams, roles, member invites, shared keys, and budgets — managed in Profile, on hosted and self-host alike.

An organization is a team that shares ownership and governance across the ecosystem. Organizations are managed in AgentKitProfile — Profile is the system of record for orgs on both hosted and self-hosted installs. Market still owns kit ownership and visibility, but it resolves org membership from Profile.

What an org gives you

Shared membership — invite teammates and manage their roles.
A shared Anthropic API key — one org key Auto and Forge can fall back to.
Spend governance — a per-run budget override plus monthly usage limits.
Private kit catalogs — kits owned by the org can be kept private (in Market).

Roles

Every member of an org has one of three roles:

Role	Can do
Owner	Everything an admin can, plus manage owners and delete the org. The creator is the first owner.
Admin	Invite and remove members, change member roles, set the org API key, and set the per-run budget and monthly limits.
Member	Belongs to the org and can use its shared resources (e.g. the shared API key and org-owned kits) within the org's limits.

Inviting members

Owners and admins invite teammates by email from the org management UI. An invite is claimed on login: when the invited person signs in with that email for the first time, they are added to the org with the role you chose. This works the same on hosted and self-host (where identities come from your OIDC IdP).

Org Anthropic API key

An org can hold a single shared Anthropic API key. Auto (and Forge) fall back to it when a member has not supplied their own key. Key resolution follows a clear precedence:

member's own key  →  org shared key  →  operator key

A member's personal key always wins; the org key is the team fallback; and the operator key (configured by whoever runs the install) is the last resort. The shared key is stored encrypted at rest in Profile.

Per-run budget

An org can set a per-run budget override that bounds the cost of each individual Auto run. This is a guardrail on a single run and is independent of the monthly limits below — both apply.

Monthly limits

Owners and admins can set monthly usage limits for the org. Two pools are available, each expressed in dollars and/or active-minutes:

Org-wide pool — a cap across all members combined.
Per-member cap — a cap each individual member may use.

Leave any field blank for unlimited. Limits reset at the start of each calendar month (UTC). A new Auto run is blocked before it starts (a pre-run gate on the run's estimated cost) when any set cap has been reached; the per-run budget continues to bound each run that does start.

Self-host & fail-open. Monthly limits apply on self-hosted installs too, as governance over each run's estimated cost. Enforcement fails open — if Profile is unreachable, runs are never blocked.

Private kits

Kit ownership and visibility stay in Market. A kit owned by an org can be marked private — excluded from the public catalog and visible only within the owning org. Market resolves who is "within the org" by checking membership in Profile.

Self-hosting

Organizations are part of the open-core stack and work on a self-hosted install. Profile is the org system of record there too; deploy the agentkitprofile chart and wire Market, Auto, and Forge to it. See Self-hosting on Kubernetes and the full deploy/SELF_HOSTING.md guide.