Hosted business software · Sage 200 Professional
Sage 200 hosting, built to Sage's own requirements.
Sage 200 Professional can be hosted: Sage supports it on Remote Desktop Services with Windows Server 2022 or 2025, as long as the deployment follows its rules. We build and run the servers in London to those rules, and your Sage business partner installs and supports Sage 200 itself.
- spec sheet
- updated 21 October 2026
- Server location
- London, United Kingdom
- Windows Server
- 2022 or 2025, as Sage 2025 R2 requires
- Database
- SQL Server 2019, 2022 or 2025, Standard edition or above
- Remote access
- Session-based Remote Desktop with multi-factor sign-in
- Price
- Fixed monthly quote after sizing
- Human support
- Monday to Friday, 08:00 to 18:00 UK time
What Sage requires for Sage 200 Professional 2025 R2
Sage publishes a system requirements guide for each Sage 200 Professional release. These are the points from the 2025 R2 guide that decide how a hosted setup must look:
| Area | Sage's requirement | What it means for hosting |
|---|---|---|
| Server operating system | Windows Server 2022 or 2025. Support for Windows Server 2019 was removed in 2025 R2. | Servers still on 2016 or 2019 need rebuilding before the next upgrade. |
| SQL Server | SQL Server 2019, 2022 or 2025, Standard or Enterprise edition. Not on a domain controller. Collation Latin1_General_CI_AS, mixed mode authentication, TLS 1.2. | SQL Server Standard licensing is part of the cost. Express is not on the list. |
| Remote Desktop Services | Supported on Windows Server 2022 and 2025 using session-based desktop deployment with a published desktop. Virtual-machine based desktops are not supported; RemoteApp is not recommended. | Users get a full remote desktop, not a single published app. |
| Memory per user | At least 600MB per session for occasional tasks, 1GB per session for prolonged processing. | We size the Remote Desktop server from your real user count. |
| WAN and VPN | Running Sage 200 over a wide area network or VPN is not supported, because latency causes slow performance and database timeouts. | The Sage 200 client must sit next to SQL Server, which is exactly what a hosted Remote Desktop server does. |
How we build a hosted Sage 200 environment
- 01
Sizing call with you and your Sage partner
Number of users, modules, add-ons, database size, reporting tools and integrations. This decides how many servers you need and how big they are.
- 02
Servers to Sage's specification
A SQL Server and a Remote Desktop session host, or one combined server for small teams where Sage's rules allow it. SQL Server is never put on a domain controller.
- 03
Your Sage partner installs Sage 200
Sage 200 Professional is sold and implemented through Sage business partners. They install, configure and upgrade Sage 200; we give them the access they need and keep the servers healthy.
- 04
We run the platform
Critical and high-risk Windows and SQL Server updates within 14 days of release, in an agreed window; multi-factor sign-in for Remote Desktop; monitoring, backups of the databases and the servers, and help with restores.
Sage's guide also recommends running large batch processes and updates out of hours. With a hosted server, that is easy to schedule because nothing depends on an office PC being left on.
Day to day on Remote Desktop
- Log out of Sage 200 before closing the remote session. Sage's help says that if you close the session while logged in, Sage 200 will not show you as logged off until you reopen the session and log out. Disconnected logins can also block other users from a record until they are cleared; from 2025 R2, Sage 200 can remove them automatically.
- Excel and Power BI. Reports that open in Excel run on the server, so your Microsoft 365 plan must allow Office on a shared server; see the licensing notes.
- Printing. Remote Desktop can pass local printers through to the session; we test your main printers before go-live.
What it costs
Our Managed Windows Server starts at £119/month (list £149/month), with no VAT added. Sage 200 usually needs more than that base server: a correctly sized Remote Desktop host, SQL Server Standard licensing and sometimes a separate database server. We quote a fixed monthly price in writing after the sizing call, before you pay anything. Your Sage 200 subscription and your partner's services stay with your Sage partner.
Moving the data from your current servers is included, done together with your Sage partner and timed away from month end.
Price
Managed Windows Server
Standard
Windows Server with licence, managed by us.
£119/monthList price
£149/month- Free migration from your current host
- Critical and high-risk security updates within 14 days
- Remote Desktop with multi-factor sign-in
- Automated monitoring and recovery
- Backups with restore help
- Support in UK business hours
Prices in pounds. No VAT is added: we are not VAT registered. The lower price is our intro price for the first 50 customers; the struck-through figure is the list price. Licensing is confirmed with you before setup.
FAQ
Questions we get asked
Is Sage 200 supported on Remote Desktop?
Yes. Sage's 2025 R2 requirements list Remote Desktop Services on Windows Server 2022 and 2025 as supported, using session-based desktop deployment with a published desktop. Virtual-machine based desktops are not supported and RemoteApp is not recommended.
Can we use Sage 200 over a VPN instead?
Sage does not support running Sage 200 over a wide area network or VPN, because the latency between the client and SQL Server causes slow performance and timeouts. Remote Desktop keeps the client next to the database.
Which SQL Server edition does Sage 200 need?
Sage 2025 R2 lists SQL Server 2019, 2022 and 2025 in Standard or Enterprise edition. SQL Server Express is not on the list.
Do you replace our Sage business partner?
No. Your Sage partner keeps installing, upgrading and supporting Sage 200. We host and manage the servers it runs on and work with them during the move.
Our servers run Windows Server 2016. Is that a problem?
Yes, for two reasons: Sage 200 2025 R2 needs Windows Server 2022 or 2025, and Microsoft ends extended support for Windows Server 2016 on 12 January 2027. Moving to a hosted server solves both at once.
Sources
- Sage: Sage 200 Professional system requirements and prerequisites (2025 R2), PDF (opens in a new tab)
- Sage: Sage 200 installation guides and supported versions (opens in a new tab)
- Sage 200 Professional help: User Login Status (opens in a new tab)
- Sage 200 Standard help: System requirements (opens in a new tab)
Vendor facts were checked against these sources on 21 October 2026. Requirements change with each release; check the source for your exact version.
Sage, Pegasus, Opera, Microsoft and Access are trademarks of their owners. WharfCloud is not affiliated with or endorsed by them.
Read next
- GuidesSQL Server 2016 end of support: what to do nowSQL Server 2016 support ended on 14 July 2026. What it means for Sage 200, Opera 3 and other apps, the ESU dates, and upgrade paths to SQL Server 2025.
- ProductsHosted accounting software servers for UK firmsSage 50, Sage 200, Pegasus Opera 3 and other Windows business software on a managed London server, used over Remote Desktop. From £119/month, no VAT added.
- Migrations and reviewsWindows Server 2016 end of support migration planWindows Server 2016 extended support ends on 12 January 2027. Get a costed migration plan for up to five servers for £525 (list £750). No VAT added.
Start with a short conversation.
Tell us which software you run, which version and how many people use it. An engineer replies in UK business hours, confirms licensing and gives you a fixed monthly price before anything is set up.