Skip to content

Workspace cost metadata #15655

Open
@stirby

Description

@stirby

Problem

Currently, our quota features allow for functionally limiting the number of workspaces/resources that may be allocated within an organization. Administrators define an arbitrary currency, then assign daily_cost to each template's resources using the coder terraform provider. The sum of these costs equals the cost of the workspace. Each user in an organization is given a quota that cannot be exceeded by the sum of that user's owned resources.

However, customers have recently asked for fewer functional limitations or chargeback models and more visibility into the actual dollar cost of each workspace. Developers may use the quota system to understand what resources their team provides, but they are unclear on the expense they are incurring to the organization.

Many have requested modules or in-product tools that can call external services like Kubecost to show an exact dollar amount associated with an environment. Given the diversity of infrastructure, cloud providers, scaling tools, and FinOps tooling, a cost exposure suite may make the most sense as a series of modules run by the agent.

This feature is still in the discovery phase and will require much design. This thread will be used for product updates and as a hub to gather feedback from our community and customers as we advance.

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs decisionNeeds a higher-level decision to be unblocked.needs-rfcIssues that needs an RFC due to an expansive scope and unclear implementation path.roadmaphttps://coder.com/roadmap. Only humans may set this.roadmap-maybeIdeas we're considering! Only humans may set this.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions