Datacenter operations · metering and billing

Carry every service from usage to invoice.

Attribute consumption to the correct organisation, project, service and plan, then keep customer reporting and finance reconciliation on the same commercial record.

Metering · tenant Meridian AGInstance hours1,284 hAccelerator hours312 hBlock storage18.4 TBEgress2.1 TBAPI requests1.8 MPlansyour pricesInvoiceNº 2026-0912Total€8,420reconciled · paidAPI · EVERY ACTION IS A CALLGET /v1/tenants/meridian/usage?period=2026-09POST /v1/plans { "name": "gpu-hourly", "price": 2.40 }GET /v1/invoices/2026-0912 → 200 · total 8420.00 EURPOST /v1/projects/erp/instances { "size": "m.large", "count": 4 }
Measure
Resource-level
Compute, GPU, storage and network
Attribute
Tenant & project
Every unit has an owner
Price
Operator-defined
Plans and commitments
Reconcile
Traceable
Invoice back to usage
Scope

Commercial operations grounded in delivered service.

Metering begins with the resource and remains connected through budgets, reports and invoices.

Usage records

Capture service consumption in the unit appropriate to each resource.

Attribution

Tie every record to tenant, project, service and location.

Budgets and alerts

Give teams visibility before the billing period closes.

Invoice reconciliation

Trace charges back to the plan and measured events that produced them.

Operating workflow

One commercial record from delivery to finance.

The operator and customer see consistent usage throughout the billing cycle.

  1. 01

    Measure

    Record consumption against the running resource.

  2. 02

    Attribute

    Assign usage to its tenant, project and commercial plan.

  3. 03

    Present

    Show current consumption and budget status in the portal.

  4. 04

    Reconcile

    Issue and export the invoice with usage traceability intact.

Two connected responsibilities

Operator control and customer action stay explicit.

Operator responsibility

What commercial teams manage

  • Plans, units and price lists
  • Commitments and reservations
  • Billing periods and invoice records
  • Exports and finance integration
Service consumer

What customers understand

  • Current resource consumption
  • Project and service breakdown
  • Budget position and forecast
  • Issued invoices and supporting usage
Operational outcome

What this changes in the working model.

Outcome 01

Fewer disputed numbers

Operator and customer work from the same metering record.

Outcome 02

Product flexibility

Different resource types can carry different plans and units.

Outcome 03

Auditable revenue

A charge can be traced back to service and usage.

Return to datacenter operations overview
Partner with us

Connect your cloud service to the commercial record.

We will map metering units, plans, billing cycles and finance integration around the services you sell.