Guides / Access and automation
Read your usage and costs
Etorm meters the resources in your projects while they are Ready and records the result as Usage objects. Read them with kubectl or curl to see what your projects have used this month and what that comes to at the current prices. Amounts are integers in micro-units of your account's currency.
This is a meter you can read, not a bill. Nothing is invoiced or charged.
The objects involved
| Kind | What it is |
|---|---|
BillingAccount | who pays; its status.monthToDate is the total metered this month across its projects |
Project | the unit usage is attributed to; each project belongs to exactly one billing account (create both) |
SKU | one line of the price list: a kind of resource, a unit (hour) and a price |
Usage | one object per project, SKU and month: how long the resource existed and what it cost |
All four live in the platform cluster (api.etorm.com, the etorm kubectl context), not inside a project's cluster. The platform writes Usage and SKU, and you only read them. Every field is described on its resource page.
How amounts are written
Money is stored as integers. 1 000 000 micro-units are one unit of the account's currency, which is one US dollar or one euro. The account's currency says which, USD or EUR, and it cannot be changed. A SKU with priceMicros: 5000 costs 0.005 per hour. The API never returns decimals, so dividing by 1 000 000 is up to you.
Read the price list
kubectl --context etorm get skus kubectl --context etorm get sku network-vpc-hour -o yaml
curl -sS -H "Authorization: Bearer $ETORM_TOKEN" \ https://api.etorm.com/apis/billing.etorm.com/v1alpha1/skus \ | jq -r '.items[] | [.metadata.name, .spec.resource.plural, .spec.unit, .spec.priceMicros, .spec.currency] | @tsv'
A SKU names the resource it counts in spec.resource (API group and plural). The SKUs that count resources by the hour include:
| SKU | Counts |
|---|---|
network-vpc-hour | VPCs |
network-account-hour | VPC accounts (attachments) |
compute-process-hour | Compute processes |
edge-loadbalancer-hour | load balancers |
edge-ingress-hour | ingresses |
This page states no prices, because none are set. Read them from the API, which is the authority. A SKU for a service says nothing about access to it (see Service access), and a resource is only counted once it is Ready. Storage objects have no SKU. Databases and queues have SKUs for CPU-seconds and stored GiB-seconds (database-cpu-second, database-storage-gib-second, queues-cpu-second, queues-storage-gib-second), all at price 0.
How usage is metered
- Every 60 seconds, for each project and each SKU, the platform counts the resources of that kind whose
status.phaseisReady. A resource that isPending, failed or being deleted is not counted. - It adds count × seconds since the last sample to the
Usageof that project, SKU and calendar month (UTC). Two VPCs that stay Ready for one hour add 7 200 resource-seconds. - The amount is
seconds × priceMicros / 3600as an integer, rounded down. With a made-up price of 5 000 micro-units per hour, two VPCs that stay Ready for one hour come to 7 200 × 5 000 / 3 600 = 10 000 micro-units. - The account's
status.monthToDateis the sum of the month'sUsageamounts over its projects.
- Metering is by sampling, so it is accurate to about a minute. A resource that lives less than a sampling interval may not be counted at all, and the first sample of a month only starts the clock.
- A gap between two samples is counted for at most five intervals (5 minutes). We cap it so that time when the platform itself was not running is not billed to you.
- Each month gets a new
Usageobject, and its name ends inyyyymm. Usage goes to the billing account the project has at the time of the sample, so moving a project changes only later usage. - For networks, compute and load balancing we meter only how many resources exist over time. There is no metering of network traffic or requests.
Read this month's usage
A Usage is named <project>-<sku>-<yyyymm>. Its status has seconds (resource-seconds), amountMicros and lastMeteredAt.
kubectl --context etorm get usages
# BILLING-ACCOUNT PROJECT SKU PERIOD SECONDS AMOUNT-MICROS
# acme acme-prod network-vpc-hour 2026-11 7200 10000
kubectl --context etorm get usage acme-prod-network-vpc-hour-202611 -o yaml
kubectl --context etorm get billingaccount acme -o jsonpath='{.status.monthToDate}{"\n"}'
# {"period":"2026-11","amountMicros":10000}
The same with curl, summing one project's amount for a month:
curl -sS -H "Authorization: Bearer $ETORM_TOKEN" \ https://api.etorm.com/apis/billing.etorm.com/v1alpha1/usages \ | jq '[.items[] | select(.spec.projectRef.name=="acme-prod" and .spec.period=="2026-11") | .status.amountMicros] | add'
spec.period is YYYY-MM. In the console, Billing shows the same objects as labelled fields. The amounts above use a made-up price to show the format. They are not prices.
Who can read it
Two built-in roles are granted per billing account. billing-viewer reads billing accounts, projects, usage and prices, and billing-admin manages them. The owner of an account has both. A list shows only the objects you may read, so you never see other customers' accounts, projects or usage. Grant a teammate a billing role as in Give a teammate access.
What billing does not do
- There are no invoices, payments, credits, budgets or alerts. Nothing is charged to a payment method, and no resource is suspended for non-payment.
- Usage records no exact start and stop times per resource, and there is no usage export.
- Billing sets no spending limits per project or account.
- Prices are flat. There are no tiers, no per-region prices and no currency conversion.
Treat Usage as a running estimate of what the platform has metered. Prices can change.
Next
- Create a billing account and a project
- Delete things safely, so that what you no longer need stops being counted.
- Resources describes every field of
BillingAccount,Project,SKUandUsage.