Windows VPS Sizing for Remote Users: 1, 3, 5, 10 Users

In short

Windows VPS sizing for remote users starts with peak concurrent sessions and workload, not total employee count. Use current Raff VM tiers as planning anchors, then validate CPU, RAM, disk, and application behavior during real peak usage. For Raff-hosted RDS, budget the Windows Server licence separately and use RDS User SALs, not generic customer-owned RDS CAL assumptions.

A Windows VPS is a cloud-hosted Windows Server that remote users access through Remote Desktop Protocol, business software, files, or server-hosted applications. The correct size depends on what users actually do inside the server: light administration, accounting software, Microsoft 365 Apps, ERP tools, SQL Server, browser sessions, or a full Remote Desktop Services environment.

Raff Windows VMs provide administrator access, RDP access, NVMe storage, and 3 Gbps unmetered VM traffic with no VM egress fees. The main sizing questions are therefore usually CPU, RAM, storage, concurrency, and application behavior rather than transfer overage.

Quick sizing table for 1, 3, 5, and 10 remote users

Use this table as a planning baseline, not a user-count guarantee. Microsoft also treats session-host sizing guidance as a starting point that must be refined against workload and real telemetry.

Raff plans are fixed tiers. A sizing target such as 4 vCPU / 16 GB may be useful analytically, but if Raff does not currently sell that exact configuration, choose the nearest suitable live plan rather than treating the target as an available SKU.

Size by the number of users active at the same time. Ten employees with three concurrent users do not need the same Windows VPS as ten users working inside the server all day.

Remote user count and concurrent sessions are different

Size a Windows VPS by peak concurrent sessions, not payroll headcount. A 12-person office may only have 3 people logged in at once, while a 6-person accounting firm may have all 6 users active during month-end close.

Use this formula before choosing a plan:

Peak concurrent users = total users x expected same-time usage

Examples:

CPU and RAM pressure comes from active sessions and what those sessions run. A signed-in user with Outlook, browser tabs, QuickBooks, Excel, and PDF tools can consume far more resources than a mostly idle session.

Microsoft's current Remote Desktop session-host sizing guidance separates light, medium, heavy, and power workloads and explicitly recommends validating baseline assumptions against your real applications and users.

Admin RDP and RDS Session Host change the sizing and licensing model

A Windows VPS used by one or two administrators is not the same as a Windows VPS used as a shared desktop for employees. Default Windows Server RDP is for administration. Daily multi-user desktop access belongs in Remote Desktop Services with RDS Session Host and an appropriate licensing model.

For Raff-hosted Windows Server under SPLA, production licensing is currently $15/month per Windows Server Standard instance. When staff use hosted RDS desktop/RemoteApp sessions, Raff's hosted licensing model uses RDS User SALs at $8/month per user.

That is different from a customer-owned Microsoft licensing model, where Windows Server CAL and RDS CAL rules may apply according to the customer's licensing rights. See Windows Server Licensing and Multi-User RDP vs RDS before rollout.

Workload type changes the CPU and RAM requirement

Remote users are not equal from a sizing perspective. Five users checking a lightweight internal app can run on a much smaller server than five users running accounting software, Outlook, browser tabs, and reports.

The biggest mistake is buying by vCPU alone. Remote Desktop can feel slow when RAM is saturated, profiles are bloated, storage is busy, or SQL Server and user sessions compete on the same VM.

A 1-user Windows VPS is usually simple

For one administrator or one light application user, Raff's current 2 vCPU / 4 GB / 80 GB tier at $22.99/month is the practical starting anchor.

Move higher when the VM also runs SQL Server Express, IIS, accounting software, automation jobs, or several background services. A current 4 vCPU / 8 GB / 120 GB tier is $40.99/month.

Even one-user servers need backups when they hold business files, application databases, licence data, or customer records.

A 3-user Windows VPS needs workload headroom

For three light concurrent users, the current 4 vCPU / 8 GB / 120 GB Raff tier at $40.99/month is a reasonable planning anchor. If the workload is memory-heavy, do not pretend that a nonexistent 4 vCPU / 16 GB Raff SKU exists; move to a live tier that provides enough memory, such as 8 vCPU / 16 GB / 180 GB at $76.99/month, or test whether the 4/8 tier is sufficient.

If all three users need daily desktop sessions, use RDS Session Host rather than treating administrative RDP as a team-desktop solution.

A 5-user Windows VPS should be treated as production

Five active users depending on one server for daily work should be planned around continuity and real peak load, not just first-login performance.

For heavier shared business workloads, Raff's current 8 vCPU / 16 GB / 180 GB plan at $76.99/month is the safer live anchor. Lighter workloads may fit a smaller tier after testing.

If Raff hosts the Windows Server licence and all five staff need RDS sessions, an example monthly infrastructure/licensing stack is:

8 vCPU / 16 GB / 180 GB Windows VM: $76.99
Windows Server Standard SPLA:       $15.00
5 x RDS User SAL:                   $40.00
-------------------------------------------
Illustrative total:                $131.99/month

This excludes application licences such as QuickBooks, Microsoft 365 Apps, SQL Server, or third-party business software.

A 10-user Windows VPS needs a real capacity plan

For ten active shared-desktop users, a current Raff 8 vCPU / 32 GB / 240 GB tier at $137.99/month is a practical starting anchor, not a universal guarantee. Heavy accounting, ERP, reporting, browser-heavy work, or SQL Server on the same VM may justify 16 vCPU / 32 GB / 360 GB at $174.99/month or splitting roles across servers.

A hosted RDS cost example for ten users is:

8 vCPU / 32 GB / 240 GB Windows VM: $137.99
Windows Server Standard SPLA:        $15.00
10 x RDS User SAL:                    $80.00
--------------------------------------------
Illustrative total:                 $232.99/month

Again, application licences and optional storage/backup services are separate.

At ten users, track peak CPU, available RAM, disk latency, login waves, profile growth, and application-specific bottlenecks before assuming more vCPU is the only answer.

CPU, RAM, and storage should be measured after launch

Avoid hard-coded rules such as “CPU above 70% means upgrade.” A short CPU spike can be normal, while a sustained queue during the exact workload users care about may indicate real CPU pressure.

Use Windows Server Performance Monitoring to capture CPU, memory, disk, and network behavior with PerfMon and Data Collector Sets.

A practical RAM model is:

Total RAM needed =
Windows Server baseline
+ active session memory
+ application memory
+ database/cache memory
+ security/backup overhead
+ operating headroom

There is no universal “2-4 GB per user” truth across all workloads. Browser-heavy, Outlook-heavy, accounting, ERP, and database-backed users can vary dramatically.

Storage sizing should include Windows, profiles, downloads, AppData, business files, application databases, logs, temporary files, and backup staging. Raff VM plans include fixed local NVMe storage; additional volumes are available at $0.08/GB/month, while snapshots/backups are $0.06/GB/month.

Network quality affects RDP even when the VPS is sized well

A correctly sized Windows VPS can still feel slow if the user's network path is unstable. Check latency, packet loss, Wi-Fi quality, RDP display settings, and whether the problem affects one user or everyone.

Raff VM traffic uses a 3 Gbps unmetered connection with no VM egress fees, but the end-to-end Remote Desktop experience still depends on the user's connection and route.

Use RDP Performance Tuning after the server has enough CPU and RAM.

Licensing must be planned before user rollout

Use this split:

Customer-owned licensing is a separate path and may involve Windows Server CALs/RDS CALs depending on the customer's Microsoft rights. Do not mix those customer-owned CAL rules with Raff's hosted SPLA/SAL model.

Recommended starting plans use current Raff tiers

These are planning anchors, not performance guarantees. Validate with the actual software vendor's support matrix and monitor production usage.

Common sizing mistakes

Sizing by total employees

Size by peak concurrent users and workload type.

Treating admin RDP as team desktop access

Use RDS Session Host when staff need daily desktop or RemoteApp sessions.

Treating resource targets as live Raff SKUs

A theoretical 4 vCPU / 16 GB target is not automatically an available Raff plan. Map the target to current live tiers.

Ignoring application behaviour

QuickBooks, Outlook, ERP, SQL Server, browsers, and tax software can have very different CPU/RAM patterns.

Buying too little RAM

Memory pressure and paging are common causes of poor RDP responsiveness.

Forgetting profiles and storage growth

Outlook caches, downloads, browser data, logs, reports, and company files grow over time.

Running every role on one VPS forever

As contention becomes visible, separate SQL Server, application, file, or RDS roles where appropriate.

Validation scope

This September 2026 refresh is a planning and source-of-truth update, not a fresh Raff benchmark claiming a fixed number of users per plan. Current Raff VM tiers, Windows Server SPLA pricing, RDS User SAL pricing, network terms, volume pricing, and snapshot/backup pricing were revalidated. Microsoft session-host sizing guidance was also rechecked. Always validate final sizing with the actual applications and peak-user behaviour.

What's next

• Windows Server Performance Monitoring — measure CPU, RAM, disk, and network before resizing.
• Multi-User RDP vs RDS — understand the two admin sessions vs RDS Session Host split.
• Windows Server Licensing — compare SPLA, SALs, customer CALs, and BYOL.
• RDP Performance Tuning — improve Remote Desktop responsiveness after sizing is correct.
• Raff Windows VM — review current plans.
• Raff pricing — confirm current pricing before deployment.

Sources

• Microsoft Learn — Session host virtual machine sizing guidelines for Azure Virtual Desktop and Remote Desktop Services
• Microsoft Learn — Performance tuning Remote Desktop Session Hosts
• Microsoft Learn — License Remote Desktop Services with Client Access Licenses
• Microsoft Learn — Choose how you pay for Remote Desktop Services
• Raff — Windows Server Licensing
• Raff — Windows VM
• Raff — Pricing
• Sources revalidated: 2026-09-09