Every resource, one owner.
Instance ids, ARNs, Azure resource ids, Google resource names, OCIDs, OpenStack UUIDs and host names: each resource keeps its identities and its account, and tag rules assign customer, business group and contract.
Cloud and sovereign cloud
For providers that run customer estates in AWS, Azure, Google Cloud, OCI and OpenStack — their sovereign partitions included — beside their own halls: Rymvard discovers every resource with its identities and its account, gives it its customer, business group and contract by your tag rules, and shows per sovereign zone which flavors can still be sold and whether a region survives losing a zone.
Read-only. New in version 0.28 — the screens show an illustrative example estate, not a customer.

The same customer appears as an account id, a tag, a project and a name in the CRM. A resource found twice with two identities is either one server or two. And a sovereign region sells its flavors zone by zone — until a zone fails and the others must carry it.
Instance ids, ARNs, Azure resource ids, Google resource names, OCIDs, OpenStack UUIDs and host names: each resource keeps its identities and its account, and tag rules assign customer, business group and contract.
An identity that could belong to two resources is quarantined, never merged by a guess. A source past its freshness limit stays unknown.
For OpenStack regions: free capacity per availability zone, the largest flavor that still fits, quotas that promise more than is free — and whether each region survives losing a zone.
What Rymvard shows
Sovereign regions and their zones, resources with their owners, managed databases and storage, SAP in the cloud and the licences that move there — each figure traceable to the discovery run and the moment it was read.

AWS with its instance-type catalogue, Azure, Google Cloud and OCI with their sovereign partitions, and OpenStack — in the same ledger as your own clusters.
VMware in the hyperscalers, managed databases, buckets and recovery into the cloud, each with its account and its customer.
SAP systems on hyperscaler hosts and RISE with SAP contracts on the SAP & HANA page — kept apart from your own halls.
Bring-your-own-licence rules per cloud and the software declared on each cloud resource, counted in the same positions as on premises — by your rules.
Rymvard discovers what runs. It never changes a cloud account.
New in 0.28 · Workspaces
Sovereign cloud operations open Rymvard on their own home — regions that fail the zone-loss check, quotas above what is free, free capacity and flavors that fit nowhere, with AI that explains every number and suggests the next step. See the workspaces
Which flavors can we still sell per zone — and does every region survive losing a zone?
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
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
One cloud estate or one sovereign region, read-only: every resource with its owner, every zone with its headroom.