An organization owns instances, Run Jobs, network volumes, templates, registry credentials and credit. This page covers creating and switching organizations, members and roles, and compute quotas.
When you sign up, you get a personal organization. To create another one, open the organization menu at the top of the sidebar, click New organization, enter an Organization name, and click Create organization. You become its owner.
Switch organizations from the same menu. The console, and API keys you create, act in the active organization.
| Role | Can |
|---|---|
| Owner | Everything an admin can, plus manage payment methods, auto top-up and the low balance alert. |
| Admin | Invite and remove members, change roles, change organization settings, manage registry credentials, and edit or delete shared templates. |
| Member | Deploy and manage instances, Run Jobs, network volumes and their own templates, and add credit. |
Owners and admins can invite people.
Invitations expire after 7 days. The person must accept with the email address you invited.
To change a member's role or remove them, use the Members tab. A removed member loses access to the organization's resources immediately.
In the Organization tab of the Settings page, owners and admins can change the Organization name and the Billing time zone. The time zone decides how usage and charges are grouped into days.
Each organization has limits on how much compute it can use at once. Instances and running Run Jobs count together.
| Limit | Default |
|---|---|
| GPUs in use | 16 |
| vCPUs in use (CPU compute) | 64 |
| GPU instances and Run Jobs at once | 16 |
| CPU instances and Run Jobs at once | 32 |
| Run Jobs waiting at once | 1,000 |
Run Jobs wait until they fit. Ask us on Discord to raise your limits.