Which service is spending your cloud budget?
Connect AWS, GCP, or Azure. Use costTags to map resources to the services that use them. Read cost per service beside the rest of its engineering context.
Provider bill
Compute
Service=payments
Database
Service=payments
Queue
Service=payments
Service view
payments-service
Compute + database + queue
Attributed spend
One service total
The bill has the resources
It does not have the architecture.
Instances, buckets, and queues arrive as separate line items. The service that caused the spend, the team that owns it, and the product path it supports are missing.
# Ownership expressed as a rule costTags: - service: payments-service match: tag: Service: payments Env: prod - service: search-indexer match: tag: Team: discovery
Explicit, not guessed
The mapping belongs in the repo.
costTags decide which resources roll up into each service. The rules are reviewed in a pull request, versioned with the code, and updated when ownership changes.
Cloud connections
AWS / GCP / Azure
Match cloud tags
Review every rule
The rollup
Read spend in the shape of the system.
Resource spend becomes a service total, beside the owner, APIs, models, and docs already attached to that service.
Attributed to
payments-service
Shown as
Cost per service
Continue through the graph
The number arrives with context.
Built for platform teams, engineering leads, and FinOps
Frequently asked questions
Still have a question about Costs & Infra? The docs cover cloud connections, costTags, and service attribution in detail.
Read the docsMake every service carry its share of the bill.
Connect a cloud account, declare the rules, and read spend where engineering work happens.