Most licensing guidance for Windows Server explains cores and CALs in the abstract and then stops right before the question you actually have: what does this cost me when Windows Server runs on a VPS instead of on a physical box in my office? The answers differ in three concrete ways — who holds the license, how “cores” map to vCPUs, and how your remote users are counted. This is the VPS-specific version of the rules.
Rule 1: On a VPS You Are Almost Never the License Holder
When you rent a Windows Server VPS, the provider licenses Windows through the Services Provider License Agreement (SPLA) or an equivalent hosted-services program. You are paying for the right to use a licensed instance, bundled into the monthly price. Practical consequences:
- You do not buy or transfer a Volume License for the OS. Your MAK or KMS key from a past physical deployment does not move to the VPS, and using it there is a licensing violation.
- You do not get to choose the edition freely. The provider offers what its SPLA agreements support — usually Standard and sometimes Datacenter or Essentials-adjacent SKUs.
- You are still responsible for your own RDS CALs and client CALs in most arrangements. The OS license being included does not mean your users are covered.
- Downgrade rights are limited — you generally cannot run Server 2016 on a plan provisioned for 2022/2025 just because you prefer it.
If the provider’s plan page does not state which edition and how many cores are licensed, assume Standard and ask. Datacenter licensing on a VPS is uncommon and typically only shows up on dedicated or high-density plans.
Rule 2: Cores Are Physical Cores, Even When You See vCPUs
Microsoft’s core-based licensing is defined against physical cores on the host, with a hard minimum of 16 cores per physical processor, 8 per processor for small instances under the SPLA model. Providers handle this for you, but it explains some plan pricing:
| What you see in the plan | What it means for licensing | Impact on you |
|---|---|---|
| “2 vCPU / 4 GB” | You get 2 virtual CPUs of a licensed host | Nothing to license yourself |
| “4 vCPU / 8 GB” | Still one licensed instance | Upgrading vCPU does not need a new OS license |
| Dedicated physical server | You (or the provider) must license all physical cores, min 16 | This is where core math really bites |
| Adding a second Windows instance | Standard allows 2 OSEs per license on the same host | Datacenter is unlimited OSEs |
The takeaway: on SPLA-priced VPS plans, the core minimums are the provider’s problem, not yours. Your cost scales with the plan size, not with a core-count formula you have to compute. That is the single biggest simplification of moving to a hosted Windows VPS. The underlying rules — per-core pricing, the 16-core floor, Standard vs Datacenter OSE counts — are the same ones covered in our core-based licensing explainer.
Rule 3: Your Remote Users Still Need CALs or RDS CALs
This is the part that surprises people. The OS license bundled with your VPS covers the server. It does not cover the humans and devices connecting to it. Two distinct CAL types matter, and they are not interchangeable.
Windows Server CALs (User and Device)
- Required for any user or device that accesses the server for file sharing, printing, or authentication against AD.
- A User CAL covers one person across unlimited devices; a Device CAL covers one device across unlimited users. Choose by the ratio that is cheaper for you — shift workers share devices (Device CALs win); mobile consultants share devices unequally (User CALs win).
- Not required for purely anonymous web access to an IIS site.
- Not required for an administrative RDP session used only for server management — that is covered by the server license itself, provided you are not running applications for end users.
RDS CALs (Remote Desktop Services)
- Required once you use RDP for end-user application access — a session host, RemoteApp, published desktops, or multi-user anything.
- Every user or device needs an RDS CAL on top of the corresponding Windows Server CAL.
- The free “2 sessions for administration” allowance is admin-only. Using it to run Office or a line-of-business app for staff is the most common licensing violation we see on VPS deployments.
- RDS CALs are purchased separately — usually not bundled by VPS providers, since they are tied to your user count, not the machine.
| Usage scenario on a VPS | Server CAL | RDS CAL |
|---|---|---|
| You RDP in to manage IIS/SQL | No | No |
| Public website hosted on IIS, anonymous visitors | No | No |
| Staff authenticate to a domain controller on the VPS | Yes (User or Device) | No |
| Staff connect to a file share on the VPS | Yes | No |
| Staff log into a session host to run a LOB app | Yes | Yes |
| RemoteApp publishing a single app to 12 staff | Yes | Yes (12) |
| External contractors given RDP sessions | Yes | Yes |
The Distinction That Costs the Most Money
“Administrative use” vs “end-user use” is the entire hinge. The same RDP connection is free if you are the administrator maintaining the server, and licensable if a non-admin uses it to do their job. If your VPS is really a multi-user desktop in disguise, you are running RDS and need RDS CALs — and if the provider sells you a “Windows VPS” for that purpose without mentioning it, the compliance gap is yours, not theirs.
Our RDS Session Host vs RemoteApp comparison covers which deployment model you are actually running, and the Remote Desktop Gateway vs direct RDP breakdown matters for the same reason: a gateway does not change the CAL requirement, only how users get in.
What to Ask a VPS Provider Before You Buy
- Which Windows Server edition is installed, and is it Standard or Datacenter?
- Is the Windows license included in the monthly price, or billed separately?
- How many cores are licensed on the plan, and what happens when I add vCPUs?
- Can I reimage to a different Windows version without a license change?
- Do you sell RDS CALs, or do I bring my own?
- Is the instance eligible for the license mobility rules I need for SQL Server?
A provider that answers all six clearly is one that has thought about licensing. InterServer’s Windows VPS runs licensed Windows Server with the OS cost inside the plan price, is price-locked so your renewal does not jump, and comes in at $0.01 for the first month with promo code TRYINTERSERVER. Plan specs and edition details across several providers are compared on windows-vps.org, so you can match the licensed edition to the role before you commit.
Practical Summary
- On a VPS, the OS license is the provider’s responsibility under SPLA — core minimums are not your calculation.
- You still own the CAL question: Server CALs for file/print/AD access, RDS CALs for multi-user application access.
- Admin-only RDP is free. End-user RDP is not. That one distinction drives most of your licensing cost.
- Adding vCPUs to a VPS plan does not require you to buy a new Windows license.
- Confirm the edition and CAL support with the provider before you design the deployment around it.
