Usage-based Billing

Usage-based Billing is currently in Early Access. Please contact us to request access, or send feedback.

Usage-based billing provides a flexible way for teams and individual users to pay for Gitpod.

Instead of pre-paying for yourself or for each team member every monthb, Gitpod will charge for usage based on how long each workspace runs, and its allocated resources.

With usage-based billing you will be charged only for the usage incurred during a billing period.

Credits

Gitpod usage is measured in credits. Your invoice will show the total amount of credits consumed in a billing period.

Larger workspace classes will use credits at a faster rate than smaller workspace classes. E.g. Standard workspaces use 10 credits per hour, whereas Large workspaces use 20 credits per hour.

Users or teams who have been granted free credits, or who have purchased credits in advance, will use those credits first, and only see charges for additional usage above that.

Configure team billing

Team owners can configure usage-based billing in their team settings.

Configure Team Billing

You can add a payment method with credit card details in Euros or Dollars.

Add payment details

Once billing has been configured, all team members’ usage will be billed to the team.

Active Team Billing

Configure a usage limit

Configuring a usage limit, in total credits, will prevent users from starting workspaces once the limit has been reached.

Active Team Billing

View usage details

Team owners can view usage details for their team for the current (unbilled) billing period, and for previous billing periods.

Active Team Billing

Good to know

  • Usage-based billing is an early-access (invitation only) feature.

  • You will need to cancel any existing (prepaid) team-plan before configuring usage-based billing.

  • Metered usage includes prebuilds.

  • The usage limit will prevent workspaces from starting, but it will not stop running workspaces.

  • Usage for running workspaces which span two billing periods will not be double-charged.

Was this helpful?