PricingConsole

Accounts

Last updated 12 November 2026

View .md

Everything you create in Tonbo belongs to one account: its databases, streams, Machines, API keys and the balance that pays for them. An account is your personal account or an organization. Its members are people and Agents, and each member’s role decides what they, and every key that acts as them, may do (see Members and roles and Agents). How accounts, members, keys and regions fit together is in Concepts.

Personal accounts and organizations

Tonbo has two kinds of account, and they offer the same products. What differs is who can be in them and how they are paid for.

  • Your personal account is made when you first sign in, and is named after your username (change it on Profile). You are its one person and its owner; you can add Agents to it, but no other people. It gets the monthly free usage (see Usage and billing).
  • An organization is a team’s account, with its own databases, streams, Machines, keys, members and balance. You make one in the console: open the account menu in the top bar, beside the Tonbo logo, choose New organization and give it a name. You become its owner and invite the others (see Invite a person). A new organization starts with no credit: buy some on its Usage & billing page before it is used. Organizations are made only in the console; the CLI and the API have no step for it.

What a member creates belongs to the account, not to the member: a database a person created stays when that person leaves, and is billed to the account. The console shows an account at tonbo.dev/<account>, and its Settings page shows its kind, id and your role. An owner renames an organization there. To close your account, see Delete your account.

Nothing moves between accounts. A database, stream or Machine stays in the account it was created in, and a personal account does not turn into an organization. To move data, create the database or stream in the other account and copy the data over. If a team will share what you build, start it in an organization.

Choosing the account you act in

In the console, the account menu in the top bar switches between the accounts you belong to. Your tonbo login reaches all of them, one per command: the CLI acts in the account --account names, else TONBO_ACCOUNT, else the default tonbo account use set on this computer, else your personal account. The Tonbo SDK chooses the same way when it uses your login. An API key reaches only the account it was created in, so the API has no account to choose: GET /v1/account answers which one a key acts in.

tonbo account list
tonbo account use acme
tonbo account show

Which to use

You are trying Tonbo alone

Use your personal account: it exists once you sign in, and it gets the monthly free usage. Sign the CLI in with tonbo login and create a key of your own for each program.

Your team shares databases

Create an organization and invite the team. Give people the member role to create and delete databases and streams and run Machines, admin to also publish them, read usage and manage members and keys, and keep owner for whoever buys credit. Each person switches to the organization in the console, and with tonbo account use in the CLI. Give each shared program a key of an Agent, so it keeps working when a person leaves.

A coding agent that may spend at most $50 on its own Machines

Create an Agent with the member role, put it under an agent budget of $50, and give the coding agent a key that acts as it.

tonbo agent create coder
tonbo budget add coder --limit 50 --member coder
tonbo api-key create coder --member coder
  • The budget confines the Agent to the Machines it creates: it may wake, change and run commands in only those. It can still list, read, sleep and delete the account’s other Machines.
  • At the limit its Machines sleep, and none of them wakes or is created until the month resets or a person raises the limit in the console. As a member, the Agent can neither raise nor lower it.
  • As a member it reads no usage and publishes nothing, and like every Agent it creates no Agents, changes no roles and makes no keys.
  • Leave the key unnarrowed: a key narrowed to databases or streams neither manages nor calls Machines. The Agent then reads and writes every database and stream of the account, as its role allows; database and stream writes count toward the account budget, not the Agent’s.

Limits

  • An organization’s name is 3 to 40 lowercase letters, digits or single hyphens, starting with a letter. It can change once every 90 days, and earlier names stay reserved.