Kamatera Windows VPS: licensing, sizing and RDP

The reason a licensed Windows VPS is hard to find under $30 a month is licensing, not hardware. A host cannot legally rent you Windows Server without a service-provider licensing agreement with Microsoft, and plenty of budget providers simply do not have one — which is why their answer to "can I run Windows?" is "bring your own licence", which for most people means no. Kamatera deploys Windows Server and Windows Desktop images with that handled, and that is the whole reason this article exists.

What follows is what a Windows build on Kamatera actually needs, and where the money goes. We built and ran these configurations; we have not published latency figures, because RDP responsiveness depends almost entirely on the distance between you and the data centre, and a number measured from our desk would tell you nothing useful about yours.

What Windows licensing costs here

Kamatera does not publish a Windows rate card. Select a Windows image in the configurator and the monthly total moves; that difference is the licence. It is visible before you pay anything, and it scales with the vCPU count the way Microsoft's per-core licensing does, so a bigger server costs more in licence as well as in hardware.

Practically, this means you cannot compare Windows pricing across hosts from a table — you have to build the same machine on each configurator. Annoying, and worth knowing before you plan a migration around a number somebody quoted you. Our pricing guide covers the published rates for everything that does have one.

Sizing: do not run Windows on 1 GB

This is the single most common mistake, and it is understandable — the $4 plan is what the marketing says, so people buy the $4 plan and add Windows to it. Windows Server will boot in 1 GB. It will then spend its life paging, and your RDP session will feel like it is being delivered by post.

A build that behaves:

• Memory: 4 GB minimum. Windows Server idles around 1.5–2 GB before you have run anything. 4 GB gives you a usable desktop and room for one real application; 8 GB if several people will be connected or you are running SQL Server alongside.
• CPU: two cores, Type B. Type A's shared budget pool is where Windows updates go to take an hour. General Purpose is the right default. Type D dedicated cores are worth it only if something is pinned — a trading terminal watching live feeds qualifies, a remote desktop for occasional admin does not.
• Disk: 60 GB and up. A Windows Server install plus updates eats through 20 GB on its own, and the boot volume can never be shrunk later, so leaving no headroom means an expansion you cannot undo. Our setup guide explains why that one is permanent.

The counterweight to all that memory: Kamatera lets you buy exactly it. A host with fixed plans would make you take four cores to reach 8 GB of RAM, and charge Windows licensing on all four. Choosing two cores and 8 GB is cheaper here than the same shape almost anywhere that sells fixed sizes.

What actually makes RDP feel good

Three things, in order of how much they matter:

1. Distance. Round-trip time dominates everything. A modest server in the city you live in will feel sharper than a fast one on another continent, because every keystroke waits for the round trip. Kamatera's 18 locations are the useful feature here — pick the nearest one to whoever is connecting, not the cheapest or the nearest to your users, which may be a different place entirely.
2. Memory headroom. A machine that is paging makes the session stutter in a way that reads as network lag. This is the problem the 1 GB build actually has.
3. CPU class. A distant third. Type A contention shows up as occasional pauses, not constant sluggishness, and moving to Type B usually settles it.

If you are connecting from a managed corporate network, test before you commit: some networks shape or block RDP on 3389 outright, and the answer is usually a VPN rather than a different host. Our VPN comparison covers the ones that handle that cleanly.

What people actually run on these

Four uses come up repeatedly, and they want different machines:

• A line-of-business application that only ships as a Windows binary. Accounting packages, practice-management software, industry tools written in the 2000s and never ported. Usually light on resources and heavy on "it must not go down". Two Type B cores and 4 GB, and spend the saving on backups.
• A shared remote desktop for a small team. Workable, but budget per person rather than per machine — each concurrent session wants 1.5–2 GB on top of the base, so four people is 8 GB and not 4. Also note that Windows Server's default licensing covers two administrative sessions; more than that needs Remote Desktop Services CALs, which is a Microsoft cost and not a Kamatera one.
• SQL Server. Kamatera offers SQL Server editions as add-ons, licensed per vCPU. That interacts badly with the instinct to add cores for performance — every core you add is licensed twice over, once for Windows and once for SQL. Memory is almost always the cheaper lever.
• A .NET build agent. One of the few cases where Type D dedicated cores earn their price, because a build is CPU-pinned for its whole run and contention shows up directly as slower pipelines.

What Kamatera does not have, and the hyperscalers do, is Active Directory as a managed service. If you need a domain controller, you are building and maintaining one on a server of your own — which is fine, and it is work.

Trading terminals, and the thing people get wrong about them

A common reason to rent a Windows VPS is to keep a trading platform running when your laptop is not. It is a reasonable use, and Kamatera handles it, but the optimisation most people reach for is the wrong one.

Buying more CPU does not reduce the latency between your platform and your broker. What reduces it is putting the server geographically near the broker's own infrastructure — which, for a lot of brokers, means somewhere in Europe rather than wherever you happen to live. Kamatera's location list is broad enough to get close to most of them. If you are weighing this up as part of a wider setup, our prop trading firm comparison covers who actually requires what.

What you still have to do yourself

A Windows server is unmanaged on the same terms as a Linux one. Windows Update is yours. The firewall is yours. If the box is reachable on 3389 from the whole internet, it will be found and attacked within hours, so restrict RDP to known addresses at the cloud firewall — the firewall guide covers IP sets, which is the right tool for exactly this.

Kamatera's managed tiers ($50 Pro, $150 Premium per server per month) will take that on. On a Windows build those figures are a smaller proportion of the total than they are on a $4 Linux box, so they are a more reasonable proposition here than the headline comparison suggests.

Is it worth it?

If you need Windows, the shortlist of hosts that will legitimately sell it to you at this price is short, and Kamatera is on it with the ability to pick your memory independently of your core count — which, with per-core licensing, is a real saving rather than a convenience.

If you do not need Windows, do not buy it. A Linux server does the same job for a fraction of the memory and none of the licence, and the main review is the better starting point. The 30-day trial covers a server up to $100, which comfortably fits a 4 GB Windows build for long enough to know whether the session feels right from where you sit.