Each by its own unit.
Socket pairs, VMs, core pairs of worker nodes, nodes — every product counted by the unit your terms state.
Red Hat and SUSE subscriptions
Every node subscribed.Every provider month reported.
For providers running RHEL, OpenShift, SLES and SLES for SAP: Rymvard counts subscriptions the way your terms say — socket pairs, VMs, core pairs or nodes — and keeps each month's peak per customer for the Red Hat and SUSE provider programmes.
Read-only. New in version 0.27 — the screens show an illustrative example estate, not a customer.
OpenShift counts cores. RHEL counts sockets.
Every subscription counts something different, and a provider programme wants the month's peak. One OpenShift cluster that grew by a worker, or a virtual-datacenter host with a third socket, changes what you owe.
SLES for SAP, on the SAP hosts.
The HANA hosts Rymvard already knows carry their SLES for SAP subscription — counted once, next to their memory.
The month's peak.
Each night recorded; the provider report shows the month's peak and names the days that are missing.
What Rymvard shows
Every subscription, one count.
Positions per product, the hosts, VMs and nodes behind them and this month's provider reports.
Positions per product.
RHEL, OpenShift, SLES and SLES for SAP needed against owned, per customer or for your provider programme.
Hosts, VMs and nodes.
What each one counts and why — the socket pairs, the VMs per unit, the worker cores.
Provider reports.
The month for Red Hat and for SUSE as a CSV — customer, product, units. Counts only, never prices.
Infra nodes apart.
OpenShift infrastructure nodes are left out when you flag them, as your terms allow.
Read-only, from your platforms.
Rymvard reads hosts, VMs and nodes. It never changes a system.
- Hosts and VMs from the compute inventories; Kubernetes and OpenShift nodes through the read-only presets.
- Installs, rules and entitlements from CSV templates or the REST API.
- Licence rules, minimums and entitlements exactly as you enter them — your contract decides, Rymvard counts.
- Detailed records stay in their country; customer names are visible only to the people who need them.
New in 0.27 · Workspaces
A home for subscriptions.
Subscription management opens Rymvard on its own home — RHEL units, OpenShift core pairs and SLES units this month, and the positions that are short. See the workspaces
Red Hat & SUSE Subscriptions
Is every RHEL, OpenShift and SLES node subscribed — and what do we report this month?
- RHEL units this month
- OpenShift core pairs this month
- SLES units this month
- Subscription positions short
Screens from the running product on its example estate. Customer names appear only for planners and admins — findings never name a customer.
Across every vendor
Every licence, one table.
Oracle, Microsoft, Broadcom, Red Hat, SUSE and IBM positions side by side on Licences & Audit — what is short, what is unknown and what goes into this month's reports. Licence-aware placement
Report every subscription from one count.
Your estate, read-only: every node by its own unit, and the month's peak per customer.