Minimums, applied.
Per processor, per VM and per host — the minimums your rules state are applied to every host and VM; a rule that is missing is unknown, never zero.
Microsoft licensing and SPLA
Every core licensed.Every SPLA month reported.
For service providers that host SQL Server and Windows Server for their customers: Rymvard counts the cores your Microsoft rules require on every host and VM — with the minimums per processor, per VM and per host — and keeps each month's peak per customer and product for the SPLA report.
Read-only. New in version 0.27 — the screens show an illustrative example estate, not a customer.
The smallest VM can cost four cores.
A two-vCPU VM running SQL Server Enterprise is licensed for at least four cores. A Windows Server Standard host running five VMs is licensed three times. And the SPLA report wants the month's peak, not the last day.
Host or VM, by the rule.
SQL Server per physical or virtual core, Datacenter covering every VM on its host, Standard covering two VMs per licensing — counted, never guessed.
The month's peak.
Every night Rymvard records what is installed; the SPLA report shows each month's peak per customer and product — and says when a day is missing.
What Rymvard shows
Every Microsoft core, counted once.
Positions per product, the hosts and VMs behind them and this month's report — each count with the rule that produced it.
Positions per product.
SQL Server and Windows Server needed against owned, per customer or for your own SPLA licences.
Hosts and VMs counted.
Every host and VM with the cores it counts and why — the minimum, the stacking, the edition's compute limit.
A report you can file.
The SPLA month as a CSV — customer, product, edition, units. Counts only, never prices.
Shared hosts once.
A host licensed for all of its VMs is reported once, not once for every customer on it.
Read-only, from the platforms you run.
Rymvard reads hosts, VMs and installs. It never changes a customer system.
- Hosts and VMs from vCenter, Proxmox and Kubernetes inventories; SQL Server instances from the database model.
- Installs, rules and entitlements from CSV templates or the REST API.
- A night that was not recorded makes the month incomplete — the report says so instead of guessing.
- 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 Microsoft licensing.
Licence management opens Rymvard on its own home — SQL Server and Windows Server packs this month, positions short and hosts whose cores are unknown, with AI that explains every number. See the workspaces
Microsoft Licences & SPLA
Is every core licensed, and what do we report this month?
- SQL Server packs this month
- Windows Server packs this month
- Microsoft positions short
- Hosts with unknown cores
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
File the next SPLA report from one number.
One estate, read-only: every core counted by your rules, and the month's peak per customer and product.