Used, unused — or unknown.
Each commitment's FOCUS rows give its use per month. A month counts only when every day is covered; a gap leaves it incomplete, never complete.
Cloud commitments
Every commitment used.Or brought back in time.
For providers and enterprise IT that buy reservations, savings plans and committed-use discounts: Rymvard sets every commitment against the FOCUS cost exports of the clouds — used, unused or unknown — shows back what each customer and business group runs, and compares renewing with bringing the workload back to your own capacity before a commitment ends.
Read-only. New in version 0.28 — the screens show an illustrative example estate, not a customer.
A commitment is paid whether it is used or not.
Savings plans and reservations are bought for years and charged every hour. When the workload moves, shrinks or never arrives, the commitment keeps billing — and the renewal date comes before anyone has looked.
Showback per customer.
Cost rows get their customer and business group from the resource, the tag rules or the account; rows without one are counted and named, not spread.
Renew or bring back.
Before a commitment ends, Rymvard compares renewing it with running the workload on your own capacity — and checks whether that capacity fits.
What Rymvard shows
Every commitment, against its cost rows.
Commitments with their provider, owner, customer, term and last complete month, the ones ending without a decision and the ones above their unused threshold — each figure traceable to the FOCUS rows behind it.
FOCUS, as it comes.
Cost and usage exports in the FinOps Foundation's FOCUS format, and a commitments template for what an export does not carry.
Expiry without a decision.
Commitments ending within 90 days whose renewal is still open — urgent from 30 days.
Who owns, who pays.
A provider's shared savings plan, a customer's own reservations, a subscription the customer owns and the provider pays — each kept apart.
Amounts for admins.
Costs and the shares derived from them are for admins; everyone else sees which commitments run above their threshold and when they end.
Read-only, from your cost exports.
Rymvard reads what the clouds bill. It never buys, sells or changes a commitment.
- FOCUS cost exports and a commitments template; accounts and resources from discovery.
- Rymvard holds no exchange rates: commitments billed in another currency are never added to euros.
- A month with a missing day stays incomplete — never counted as used.
- Detailed records stay in their country; customer names are visible only to the people who need them.
New in 0.28 · Workspaces
A home for cloud commitments.
FinOps and cloud teams open Rymvard on their own home — commitments in force, those above their unused threshold, those ending without a decision and cost rows without a customer, with AI that explains every number. See the workspaces
Cloud Commitments
Which cloud commitments go unused — and should we renew or bring the workload back?
- Commitments in force
- Commitments above their unused threshold
- Ending within 90 days without a decision
- Cloud cost rows without a customer
Screens from the running product on its example estate. Customer names appear only for planners and admins — findings never name a customer.
Across every estate
One customer, every spelling.
The customer registry resolves every name in the ledger — contracts, racks, cloud accounts, licences — to one customer with its aliases and business groups, and billing and energy statements count it once. Takeover without migration
Decide before the renewal does.
Your FOCUS exports and commitments, read-only: what was used, what was not, and what to renew.