Apr 25, 2023
A Guide to Gitpod's New Approach to Organizations
Gitpod has recently made changes to its approach to organizations, billing, and cost attribution. In this blog post, we will explain the new changes and clarify how they affect organizations, billing, and cost attribution.
Gitpod is always listening to its users’ feedback to improve the platform. Based on this feedback, Gitpod has made changes to its approach to organizations, billing, and cost attribution. In this blog post, we will explain the new changes and clarify how they affect your experience.
Previously known as teams, Gitpod has renamed and reimagined them to make their purpose clearer. An organization (org) now equates to a company and serves as a “tenant.” This means that resources, including workspaces, projects, settings, and Single Sign-On (SSO) users in the near future, are fully owned by the org and are bound to its lifecycle.
The workspace list will soon start showing only the workspaces that belong to the currently active organization. Orgs will be able to have SSO configured and manage/own their users. This new approach to organizations sets clear boundaries for resource usage, allowing users to group their resources effectively.
Personal accounts have been deprecated and automatically turned into an organization with the same name. Billing is moved from the user settings and will be part of the org settings. New users are already observing this behavior. This change helps streamline the billing process and makes it easier to manage.
Currently, cost attribution is complex, taking into account whether the organization has credits. If not, the Default Billing Account, which is hidden in the user settings, is used. However, in line with Gitpod’s vision of self-containment for orgs, the cost of usage will soon be attributed to the org that owns that resource. If there are no credits available, no fallback is used. This change will make cost attribution clearer and easier to understand.
In line with this new approach, Gitpod has also made changes to the create workspace page. The “Always Create with Options” changelog post describes how Gitpod has changed the page to make it clearer in what org the workspace is starting.
Gitpod will roll out this change over the next few weeks and will inform users within the product when this happens. You don’t need to do anything. If you have any questions or need assistance, please reach out to Gitpod’s support team.
You might also like
LocalStack x Gitpod - Run cloud applications with LocalStack and Gitpod
Developing and running cloud applications is simplified with Gitpod and LocalStack ✨ Gitpod’s fully automated, ephemeral workspaces provide a great developer experience. LocalStack accelerates your dev and test feedback loop.
Sep 15, 2022
VS Code Desktop and SSH explained
Understand how VS Code establishes SSH connections, the different approaches, and understand common gotchas setting up VS Code Desktop and Gitpod via SSH.
Jul 22, 2022
Stay in the loop
Get a weekly email with our latest thinking, news, and insights.