A Nairobi accounting firm called us last quarter because Sage had started crawling on the tower under someone's desk, and the vendor would only support it on Windows Server. That is the exact situation this post is about: you have one application that must run on Windows, and you need it hosted properly instead of nursed in the office.
CloudSpinx hosts Windows-only business apps for companies across Kenya, so we have a routine for it. Whether it is Sage, a QuickBooks Enterprise build, Microsoft SQL Server, or a .NET line-of-business app tied to Windows, hosting a Windows app in Kenya comes down to five decisions, and we make them the same way every time.
First, confirm the app truly needs Windows
Before quoting a Windows build, we ask what the app genuinely depends on. Half the "Windows-only" apps we get sent turn out to run on Linux with no licence at all, which saves the client real money every month.
If it truly is Windows-only, we say so and move on. If it is not, we say that too. We cover that call in full in Windows vs Linux for a Kenyan business, so here we assume the app has earned its Windows licence.
Size the box for the app, not the brochure
The app decides the spec, and database-backed apps are hungrier than people expect. For an MSSQL-backed package serving around 30 concurrent users, we start at 8 vCPU, 32 GB of RAM and NVMe storage, then watch the real load and adjust rather than guess high. The four things that actually move the number:
- CPU cores, driven by concurrent users and report generation
- RAM, because SQL Server will use everything you give it for caching
- Storage on NVMe, since accounting and ERP work is IOPS-bound, not capacity-bound
- Headroom for the nightly backup window so it does not fight production
Everything here is what we have actually provisioned for Windows-only apps through mid-2026, on Windows Server 2022 and 2025.
The licences the app drags along
Windows Server is only the first licence. If the app runs on Microsoft SQL Server, that is licensed separately, either per core or as Server plus CALs, and for a busy database the SQL Server edition you pick changes the bill more than the hardware does. Standard covers most Kenyan SME workloads; Enterprise is rarely worth it below serious scale.
We fold the Windows licence, the SQL licence and the access licences into one monthly figure through per-use licensing, so there is no capital outlay and the cost tracks what you run. The full licensing breakdown sits in its own post if you want to see every meter.
Where a Windows-only app should live
A line-of-business app your staff use all day belongs close to them. We place it in a Nairobi datacentre for the shortest hop to the office, on a managed Windows build we patch and monitor. Nightly backups with a restore we actually test are not optional here, because this is the box that holds your ledgers.
Where the data carries compliance weight, we keep placement on the right side of the data-residency question rather than defaulting it offshore.
For the accounting firm, we staged Sage and its SQL database on a licensed Windows Server 2022 instance in a Nairobi datacentre, ran it in parallel against the old tower for a week, cut over on a Saturday, and had them working on it inside 24 hours of the go-live call. They now pay one monthly figure with the Windows and SQL licences already inside it, and nobody is keeping a tower alive under a desk.
Tell us the app, the number of people who use it, and whether it is backed by SQL Server, and we will come back with the spec and one monthly figure. Send it through the quote form or on WhatsApp at +254 719 246 379. The quote costs nothing.