SaxoTraderGO vs SaxoTraderPRO on a VPS: What Each Setup Looks Like
The most common question we get from Saxo clients is some version of "how do I set up SaxoTraderGO on a VPS?" — and the honest first answer is that GO may not need one. GO is a browser application: it runs anywhere, installs nothing, and closes when the tab closes. The VPS case is about what happens when you want a session, a layout, or a piece of automation to outlive your laptop. Here is how the pieces fit for each front end.
Setting Up SaxoTraderGO on a VPS
Because GO is web-based, "installing" it on a VPS means opening it in a browser on the server — Edge is preinstalled on our Windows Server images, and Chrome takes a minute to add. The point of doing this is persistence: a GO session in a VPS browser stays logged in and rendering between your visits (subject to Saxo's own session timeouts), your watchlists and chart setups are always where you left them, and a spotty hotel Wi-Fi connection only has to carry a compressed RDP stream instead of live market data.
The Swing plan ($45/mo, 4 cores, 10GB RAM) is more than enough for a GO-in-browser setup, with room for a spreadsheet and a news feed beside it. This is also the right configuration for travelers: RDP from an iPad or MacBook into the VPS and your trading environment is identical from anywhere, on any network.
SaxoTraderPRO: Where the VPS Earns Its Keep
SaxoTraderPRO is a genuine Windows desktop application — detachable modules, multi-monitor layouts, depth trader, options chains, and the algorithmic order tickets. Rebuilding a six-module PRO workspace after every reboot of a home PC gets old quickly; on the VPS the workspace simply never closes. Our images support multi-monitor RDP, so a PRO layout spread across screens at home reconnects the same way from the same monitors.
PRO is heavier than GO but not extreme: Swing handles a focused PRO setup comfortably, and Momentum ($85/mo, 8 cores, 20GB RAM) is the right call if you run PRO with many streaming modules plus other software — an Excel model, a second platform, or an OpenAPI application — on the same server.
For European clients we recommend our London LD4 or Frankfurt FR4/FR7 locations; both are in the Equinix ecosystem where much of Europe's trading infrastructure lives, and both keep round trips to Saxo short. Asia-based clients can choose Singapore or Tokyo instead.
Automating Against Saxo's OpenAPI
Saxo doesn't host third-party bots, so anything you build against its OpenAPI — position monitors, rebalancing scripts, custom alerting, algorithmic execution — needs a machine that stays on. The VPS runs your Python or C# application around the clock next to your platform session, with the added benefit that your OAuth tokens and API sessions live on one stable machine instead of whichever laptop last ran the script.
A practical pattern our clients use: SaxoTraderPRO open for discretionary work and monitoring, an OpenAPI script running as a scheduled task for the mechanical parts, and the whole desk reachable by phone RDP when a position needs attention at an inconvenient hour.
