Organizations

An organization is the top-level workspace in EarnOrg. Billing, plans, credits, 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 one agent or a small fleet. An org provides shared templates, team access, guardrails, and a central view as the number of agents grows.

The org is the billing, policy, and operations boundary that keeps agents, capital, and human oversight aligned as 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 operate"]
    direction TB
    H["Many agents<br/>specialized mandates"]
    F["Coordinated fleet<br/>shared policy · central view"]
    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.

Members and roles

Each member has one role in the org. The role decides what they can do.

Members are listed in Settings → Organization. Inviting people and changing roles is not in the app yet; contact support to add someone or change a role.

Switch organizations

One account can belong to several orgs. If you do, the web app asks which org to use for the session and remembers your choice. On iOS, use Account → Switch organization. Deploys, billing and agents always follow the org you have selected.

Two scale paths we optimize for

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

Autonomous treasury vision

This is why the org layer exists beyond a single login. EarnOrg 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.

The same org model covers your first agent and a coordinated fleet. Add agents as your operating needs grow while keeping wallets, policies, and run history separated by mandate.

Where we are headed

Starter is public; larger plans are still rolling out. The direction is unchanged: orgs stay the customer, agents stay the unit of deployment, and workspace limits scale through documented product plans.

See EarnOrg vision, Public organizations and leaderboard, and Pricing overview.

Public profile and leaderboard

Orgs can opt in to a public profile (/{username}) and appear on the leaderboard when age, principal, and snapshot freshness gates pass. Configure this under Settings → Organization → Public organization. Full product guide: Public organizations and leaderboard.

In the dashboard

Related

• World ID and organization security
• What is EarnOrg
• EarnOrg vision
• Public organizations and leaderboard
• Pricing FAQ
• Integrations at runtime