A workspace is a group of your projects. It gives you one place to see and create projects, one place to manage who has access to them, and one billing account that pays for all of them. Each project inside a workspace keeps its own API keys, sandboxes, templates, and plan.
Billing now lives on the workspace. Every workspace has one billing account for all of its projects, and existing projects were moved onto it automatically. API keys, sandboxes, templates, and project plans did not change.
What a workspace is for
- One place for all your projects. Switch between projects, create new ones for a new environment or product, and see everything your organization runs on E2B without signing in and out of separate accounts.
- One place to manage access. Add people to the workspace and they can use every project in it. If someone should only see one project, add them to that project instead. Inside a project, all members have the same permissions.
- One place for billing. The workspace has one default payment method, one billing email, one credit balance, and one monthly invoice for all of its projects. Each project still has its own plan and spending limit.
Workspace vs project
Billing
Every workspace has one billing account, and every project in the workspace is billed through it. You manage it on the workspace’s billing page in the E2B Console.
- One default payment method. The monthly invoice for all projects in the workspace is charged to the workspace’s default payment method.
- One billing email. The workspace has a single billing email, which you can change on its billing page.
- Shared credits. Credits on the workspace pay for usage in any of its projects.
- One monthly invoice. On self-serve plans, plan fees, add-ons, and usage for all projects in the workspace are billed together each month. A plan upgrade or add-on bought mid-month is charged when you buy it. Enterprise billing follows your contract.
- Plans stay per project. Each project keeps its own plan, add-ons, tier limits, and spending limit. Upgrading one project to Pro does not change the others, and each Pro project has its own monthly plan fee.
- Blocking. When a project reaches its spending limit, only that project is blocked. When a workspace without a payment method runs out of credits, every project in it is blocked shortly afterwards, until you add a payment method.
Existing projects
Every project that existed before workspaces was carried over as-is and placed into a workspace automatically:
- Self-serve accounts: projects were grouped together based on their billing data, so projects paid for under the same billing relationship share a workspace.
- Enterprise customers: projects were grouped according to the enterprise relationship. Workspaces were mapped by our team manually.
Project IDs, API keys, templates, sandboxes, volumes, template slugs, and regions are unchanged. Your code keeps working without any modification.
If a project should be in a different workspace, you can move it yourself when you are an owner of both the workspace it is in and the workspace it is going to. The project keeps its identity, API keys, templates, sandboxes, spending limit, plan, and add-ons through the move. If it is on Pro or has paid add-ons, the workspace it leaves has already paid for the current month and is not refunded, and the workspace it joins is not charged for them until the next monthly renewal on the 1st, so that workspace needs a default payment method. Usage before the move is billed to the workspace it left, and usage after the move to the workspace it joined. If your workspace does not look the way you expect otherwise, for example a project is missing, contact support@e2b.dev and we will fix the grouping for you.
Frequently asked questions
Do I need to change my code?
No. API keys are still scoped to a project and continue to work as before.
Why can a new member see all my projects?
Workspace members get access to every project in the workspace. To give someone access to one project only, add them on that project instead of the workspace.
Can I restrict what a member does inside a project?
Not yet. Inside a project, all members have the same permissions.
Will my bill change?
Plan prices stay the same, and each project keeps its plan. On self-serve plans, a workspace with several projects now gets one invoice for their plan fees and usage, and their usage draws from one shared credit balance.
Can projects in the same workspace use different cards?
No. The monthly invoice for all projects in a workspace is charged to the workspace’s default payment method. The one exception is the final invoice from a previous subscription, which is charged to the card that subscription used.
Can I move a project to another workspace?
Yes, if you are an owner of both workspaces. Move the project from the console and it keeps its API keys, templates, sandboxes, spending limit, plan, and add-ons. From then on its usage is billed to the new workspace. If it is on Pro or has paid add-ons, the old workspace has already paid for this month and isn’t refunded, and the new workspace pays for them from the next monthly renewal, so it needs a default payment method. If you are not an owner of both, ask an owner to do it or contact support@e2b.dev. 
