Organizations

How EarnClaw orgs scope billing, agents, and team access, from your first agent to autonomous treasury and fund-style operations.

An organization is the top-level workspace in EarnClaw. Billing, deploy quotas, runtime plans, and agent fleets all attach to the org, not to an individual login. You pick the active org in the dashboard before you deploy.

Today most teams start with a handful of agents. The product model is built so one org and one operator can scale to hundreds or thousands of agents as plans and capacity grow, or run a smaller fleet that behaves like a coordinated fund: shared templates, org guardrails, and central observability.

EarnClaw is also preparing the ground for a longer horizon: organizations that run treasuries and large balances autonomously. The org is the billing, policy, and operations shell so capital, agents, and human oversight stay aligned as amounts and mandates grow.

flowchart LR
  subgraph org["Organization"]
    direction TB
    B["Runtime plan<br/>deploy quota · allowances"]
    T["Team members<br/>roles and access"]
    B --> T
  end
  subgraph fleet["Agent fleet"]
    direction TB
    A1["Agent wallets<br/>delegation · schedules"]
    A2["Templates and packs<br/>trading · yield · prediction"]
    A1 --> A2
  end
  subgraph scale["How teams scale"]
    direction TB
    H["Many agents<br/>specialized mandates"]
    F["Fund-style<br/>few agents · one strategy"]
    H --> F
  end
  org --> fleet --> scale

What an org owns

One org, many agents

Organization
 ├── Runtime plan        (shared billing and entitlements)
 ├── Members             (who can deploy and operate)
 └── Agents
      ├── Agent 1        (template · runtime · wallet · schedule)
      ├── Agent 2
      ├── Agent 3
      └── …              (scale toward large fleets on higher plans)

Users sign in with their own account. Membership decides which orgs they can access and what they can change. Deploy and billing routes always resolve to the selected org.

Before you open the wizard, confirm the correct org is active. See Create your first agent.

Two scale paths we optimize for

EarnClaw supports different operating styles inside the same org model. Both use the same templates, Thirdfy catalog integrations, and run receipts.

Large fleets

Many agents, often specialized by lane, venue, or schedule. Think hundreds or thousands of runtimes over time as capacity tiers and plans expand. Each agent keeps its own wallet and guardrails; the org shares billing and operator visibility.

Fund-style operations

Fewer agents running coordinated strategies with shared risk limits and a single operational view. Capital sits in agent wallets; mandates and templates express the strategy. You still get per-cycle preflight, delegation, and audit trails.

Templates as standards

Reuse certified templates across the org so new agents inherit the same packs, observability, and guardrail patterns. Marketplace publishing and certification extend this for builder orgs when those paths open.

Autonomous treasury vision

This is why the org layer exists beyond a single login. EarnClaw treats the organization as the unit that can eventually hold treasury-scale capital, run agent fleets on mandate, and keep operators in the loop through guardrails and receipts rather than manual execution for every move.

Treasury-scale capital

Agent wallets, delegation, and org policies are designed to support meaningful balances spread across a fleet. Capital stays scoped per agent while billing, limits, and observability roll up to the org.

Autonomous fund operations

Schedules, preflight, and fail-closed execution are the control plane for funds that run on their own between cycles. Operators set mandates and guardrails; agents execute inside those bounds and leave an audit trail every time.

Oversight without micromanagement

Run history, skip reasons, and allowance usage give org operators a single view across agents. That matters when balances are large and you need proof of what ran, what was blocked, and why.

Built for teams and mandates

Members, roles, and org-scoped deploy paths prepare for shared operation of serious capital: not one person with a script, but a workspace where policy, billing, and fleet health stay in one place.

You do not need treasury-scale capital on day one. The same org model covers your first agent and the path toward autonomous treasury and fund-style operations as plans, templates, and capacity mature.

Where we are headed

Public plan tables and CEO capacity tiers are still rolling out. The direction is unchanged: orgs stay the customer, agents stay the unit of deployment, and capacity scales with plan and token tiers rather than one-off scripts.

Today	Next
CEO-holder beta and org runtime entitlements	Public runtime plans and clearer capacity ladders
Agents list and per-agent observability	Fleet-level views and org policy presets as the product matures
Platform templates in the wizard	More builder templates and marketplace listings per org
Single-org beta operations	Treasury and fund-style org patterns as capacity and governance mature