RYMVARD

Cloud and sovereign cloud

Every cloud resource, owned.Every sovereign zone, checked.

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.

A cloud bill does not say whose it is.

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.

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.

Ambiguous stays apart.

An identity that could belong to two resources is quarantined, never merged by a guess. A source past its freshness limit stays unknown.

Sovereign, zone by zone.

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

One view of every cloud estate.

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.

Rymvard's Sovereign cloud page: free vCPU and RAM per availability zone, the flavors that still fit per zone and the verdict for losing a zone
Sovereign cloud: what each zone can still take, and whether the region survives losing one.

Five clouds, sovereign partitions included.

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.

Cloud databases and storage.

VMware in the hyperscalers, managed databases, buckets and recovery into the cloud, each with its account and its customer.

SAP in the cloud and RISE.

SAP systems on hyperscaler hosts and RISE with SAP contracts on the SAP & HANA page — kept apart from your own halls.

Licence mobility.

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.

Read-only, from the cloud APIs.

Rymvard discovers what runs. It never changes a cloud account.

  • Discovery for AWS, Azure, Google Cloud, OCI and OpenStack; CSV templates and the REST API for what a cloud does not report.
  • Connectors read with no transaction open and apply in one fenced step — a worker that lost its lease commits nothing.
  • Every source has its freshness limit; past it, a figure is unknown — never a guessed zero.
  • 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 sovereign cloud operations.

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

Sovereign Cloud Operations

Which flavors can we still sell per zone — and does every region survive losing a zone?

  • Regions that do not survive losing a zone
  • Regions whose quotas promise more than is free
  • Free vCPU (sovereign regions)
  • Zones where the largest flavor fits nowhere

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

Know what every zone can still take.

One cloud estate or one sovereign region, read-only: every resource with its owner, every zone with its headroom.

Write to contact@rymvard.com