Workspace classes

Gitpod workspaces can be configured to use workspace classes that suit your needs. Each workspace class has different level of resources and a different billing tier. For more demanding tasks, choose a larger workspaces class. By default, the smallest workspace class is selected for all new workspaces. Available workspace classes may vary based on the installation.

Available Workspace Classes

Only workspace classes defined by the owner of an Organization in the Organization-level workspace class policy are viewable by members.

Based on these, members can define workspace classes at the Repository-level.

Pay-as-you-go

The following workspace classes are available for Pay-as-you-go:

• Standard: up to 4 cores, up to 8GB RAM, 30GB storage
• Large: up to 8 cores, up to 16GB RAM, 50GB storage

Enterprise

The following workspace classes are currently available for Enterprise. If you require something different, contact sales:

• Standard: up to 4 cores, up to 8GB RAM, 30GB storage
• Large: up to 8 cores, up to 16GB RAM, 50GB storage
• XLarge: up to 14 cores, up to 30GB RAM, 75GB storage
• XXLarge: up to 30 cores, up to 54GB RAM, 100GB storage

Workspace Class Defaults

The default workspace class is Standard (up to 4 cores, up to 8GB RAM, 30GB storage).

Note: the default class can be disabled within the context of an organization or repository. This means new workspaces will start with a smaller workspace class by default. If no such class is available, a larger one will be used instead.

Repository level

It is useful to set a default workspace class when a repository requires more resources to reduce cognitive load from developers. You can set custom default workspace classes per Repository. Setting a repository level default acts as a “nudge” towards the preferred workspace class for that repository.

Select a workspace class for your workspace

You can select a workspace class directly from the Gitpod Dashboard. You can do so by clicking on the New Workspace button. Then, you will be prompted for a class besides the context URL and Editor inputs.

Good to know

• Large workspace classes use credits at a faster rate. Standard workspaces use 10 credits per hour, whereas Large workspaces use 20 credits per hour.
• Prebuilds currently use the same workspace class as regular workspaces.

FAQs

Why it selected a different workspace class than my previous selected default?

The default class can be disabled within the context of an organization or repository. This means new workspaces will start with a smaller workspace class by default. If no such class is available, a larger one will be used instead.

How to select Large workspace type for extended storage and CPU

Add a Repository on Gitpod and from its settings select a larger workspace class.

Is it possible to build (android) AOSP source on Gitpod?

It is not quite feasible to build an entire AOSP tree right now due to current storage capacity limitations. Please react with a ”👍” on https://github.com/gitpod-io/gitpod/issues/13950 and comment your requirements.