One customer, every spelling.
The customer registry holds each customer with its aliases and a tree of business groups. Every row in the ledger that names a customer resolves to it, and billing and energy statements count it once.
Takeover without migration
Take over the estate as it is.Every step to go-live, recorded.
For providers that take over a customer's estate — from a previous provider, from the customer's own data center or from the cloud: Rymvard reads what runs where it runs, resolves every name to one customer, and carries the takeover from the contract with its scope and billing basis through a transition with go-live checks and baselines to an exit with export and purge.
Read-only. New in version 0.28 — the screens show an illustrative example estate, not a customer.
Most of a takeover is finding out what you take over.
The previous provider's CMDB misses VMs, a server sits in two places, one customer has five spellings across contracts, racks and invoices. Migrating first and counting later turns every gap into a dispute.
Read the estate where it runs.
Nutanix, Red Hat Satellite, SUSE Customer Center, IBM ILMT, Hyper-V inventories, CMDB exports and SUSE RMT files on premises; AWS, Azure, Google Cloud, OCI and OpenStack in the cloud — nothing to migrate first.
From contract to exit.
A contract with its scope and billing basis, a transition plan with go-live checks and baselines, and an exit that exports and purges the customer's operational data — refused while the contract is open.
What Rymvard shows
Every resource, and who it belongs to.
Discovered, claimed, onboarding, managed, offboarding — every resource with its customer, account and environment, and a state that changes only when a person changes it.
Contracts with their scope.
Which customers, business groups, sites and accounts a contract covers, and the billing basis it counts.
Go-live checks and baselines.
A transition plan holds its waves, the checks each go-live needs and a frozen baseline to compare against.
Exit with export and purge.
An exit exports the customer's operational data and deletes it — its cloud commitments and their cost rows included — and keeps your own billing history. A purged customer can return as a new onboarding.
Collectors in the customer's network.
A collector is bound to the sites and accounts it may write for. Terraform modules for AWS, Azure and Google Cloud and a Helm chart install it, its configuration passed only as a secret reference.
Read-only, nothing to migrate.
Rymvard reads the estate. It never writes to a customer system.
- Connectors for Nutanix, Red Hat Satellite, SUSE Customer Center and IBM ILMT; Hyper-V inventories, CMDB exports and SUSE RMT files as templates.
- A name that matches no customer becomes an unconfirmed customer for an admin to confirm — never a silent new one.
- A VM nobody recorded or a server in two places becomes a finding — not a silent correction.
- 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 transition teams.
Transition managers open Rymvard on their own home — contracts in transition, resources onboarding, what is ready to take over and the go-lives of the next 30 days, with AI that explains every number and suggests the next step. See the workspaces
Transition
Where does every takeover stand — and what must happen before go-live?
- Contracts in transition
- Resources onboarding
- Ready to take over
- Go-lives in 30 days
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
Wherever the estate runs.
Your own halls, the hyperscaler racks in them, public and sovereign clouds, Kubernetes platforms and the commitments you buy — one ledger, read where each of them runs. Cloud, sovereign and takeover
Take over without the dispute.
One customer estate, read-only: every resource with its owner, and every step to go-live.