Feedback Issue: Usage-based billing

[jldec]

Invite comments and questions from early access users of usage-based billing.
See #9036 for more details.

[david-bakin]

Feature improvement request: Per-project setting of workspace class. Because different projects have different needs.

Bonus points: Allows more than one project for same repo: Because different uses of the same project have different needs. (I.e., large workspaces may only be needed for certain regression runs, or certain debugging situations, or whatever.)

(See related #10963.)

[david-bakin]

Feature improvement request: Per-launch setting of workspace class. Because different projects have different needs and also different uses of the same project have different needs. (See above comment, except this is an alternate/additional way to go about it. I wouldn't my specifying for each launch (e.g., from a dropdown part of the button) but it could be combined nicely with defaults too.)

(See related #10963 which, if combined with the highly desirable feature mentioned in this comment of processing all of .gitpod.yml for environment variable expansion + passing env vars in a url would work great.)

[david-bakin]

Feature improvement request: Prebuilds to be able to use a different workspace class than interactive workspaces. For example, I only need a "standard" workspace to build my large C++ project and the "large" workspace" - with twice the cores an RAM and cost - wouldn't build in half the time. But I might like that project to use the "large" workspace when actually doing work in it.

(See related #10963.)

[david-bakin]

(Giving each suggestion as a separate comment so they can be "voted" on separately by people giving feedback here ...)

[david-bakin]

Feature improvement request: Being able to keep a Professional plan (unlimited hours on "standard" workspaces) but being able to boost to a "large" workspace on demand (e.g., at workspace launch) - billing for the credits used.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.