StrategyQuant X · Use Case
StrategyQuant X research belongs on dedicated backtesting infrastructure.
Strategy generation, robustness testing, and large-scale validation are CPU-heavy research workloads · fundamentally different from running a live trading terminal. This page explains why, and where to find the right infrastructure for each stage of your workflow.
- CPU-heavy generation & validation
- Separate from live trading VPS
- Build → Validate → Deploy workflow
Why Different Infrastructure
StrategyQuant X is a research workload, not a trading terminal
The infrastructure choices that work for live execution are the wrong choices for large-scale strategy development. Understanding this distinction is the first step toward a stable, productive research environment.
Strategy generation saturates CPU cores
Running a strategy generation batch in StrategyQuant X can peg all available CPU cores for hours or days. This is a fundamentally different workload profile from a live trading terminal, which sits mostly idle and only activates on tick events.
Research and execution are different product categories
Live trading VPS environments are optimized for low-latency order execution, minimal process overhead, and continuous uptime for a single trading terminal. Backtesting infrastructure is optimised for compute throughput and long-running batch jobs · a different operational requirement entirely.
Workload isolation protects both environments
Running heavy backtesting workloads on the same server as your live trading terminal introduces resource contention risk. A large generation batch could degrade trading performance at the worst possible moment. Separation is not just operationally cleaner · it is safer.
Consistent uptime for long-running validation jobs
Walk-forward analysis, Monte Carlo robustness testing, and multi-pass validation can run for 12–72 hours. Interruptions reset progress. A dedicated research server provides the persistent environment these jobs require without competing with your personal machine or live trading setup.
Environment Comparison
Local PC vs. Dedicated Backtest Server
Running StrategyQuant X on your personal machine gets the job done in the short term. Over time, the friction compounds.
Local PC
Not recommended
- Uptime
- Interrupted by sleep, updates, personal use
- CPU availability
- Shared with OS tasks and daily workload
- Long-run jobs
- Fragile · restarts reset progress
- Remote access
- Not designed for persistent remote operation
- Scalability
- Limited to local hardware
- Isolation
- Research competes with live trading terminal
Dedicated Backtest Server
Recommended
- Uptime
- Remote environment, away from local sleep states
- CPU availability
- Planned around your research workload
- Long-run jobs
- Suited for extended generation batches
- Remote access
- Full Windows environment, accessible anywhere
- Scalability
- Upgrade compute resources as needs grow
- Isolation
- Separate from live execution environment
The right column is what Backtest Servers deliver. Plans, compute specs, and details are on the product page. See Backtest Server Plans
SQX Infrastructure Requirements
What StrategyQuant X workloads demand from their environment
These are the infrastructure characteristics that SQX research workloads require. A standard local machine or general-purpose VPS satisfies very few of them. Backtest Servers are built to satisfy all of them.
Built for CPU-heavy workloads
Compute-first infrastructure designed around the demands of strategy generation, not optimised for low-overhead trading terminals.
Separate from live trading infrastructure
Your backtest environment and live trading environment are isolated. Resource contention does not cross environments.
Long-running research jobs
Move research away from local sleep states, desktop restarts, and competing personal workloads. Multi-day generation and validation batches get a cleaner environment.
Remote Windows environment
Full Windows desktop accessible from anywhere. Install StrategyQuant X, configure your workspace, and connect when needed.
Scalable compute options
Select the resource level appropriate for your workload. Scale up for intensive generation runs, scale back for lighter validation work.
Cleaner research-to-production flow
Build and validate on dedicated research infrastructure. Move only proven, tested strategies to your live trading VPS for execution.
Planned research environment
Resources are sized around your research workflow instead of live trading terminals, so generation batches have clearer CPU and RAM expectations.
Designed for quant research operations
The infrastructure decision-making has been done for you. The environment is configured for the way StrategyQuant X actually works.
Backtest Servers are built to meet all of these requirements. They are a separate product category from live trading VPS, designed specifically for StrategyQuant X and similar CPU-heavy research workflows. Explore Backtest Servers
Use Cases
Workflows that belong on dedicated research infrastructure
If you run any of these workflows regularly, a dedicated backtesting server is the appropriate infrastructure choice.
strategy generation
Run extended automated generation batches that explore large strategy spaces · without interrupting your personal machine.
robustness testing
Monte Carlo analysis, stress testing, and multi-pass robustness checks on hundreds or thousands of candidate strategies.
validation batches
Run systematic validation workflows across multiple instruments, timeframes, and parameter sets without time pressure.
walk-forward workflows
Long-horizon walk-forward analysis requires uninterrupted compute time. A dedicated server handles multi-day runs reliably.
portfolio research
Develop and evaluate multi-strategy portfolios with correlation analysis and combined equity curve modelling.
heavy backtest sessions
High-resolution tick data backtests and optimisation sweeps demand consistent compute throughput over extended periods.
Recommended Workflow
From research to production, in the right order
Research infrastructure and execution infrastructure serve different purposes. This workflow keeps them cleanly separated throughout the strategy development lifecycle.
Build
Develop on dedicated research infrastructure
Use your backtesting server as the persistent workspace for all StrategyQuant X work · generation batches, parameter exploration, initial screening, and data-intensive research sessions. Keep your personal machine free.
Backtesting Server
Validate
Run rigorous validation before any strategy goes live
Walk-forward analysis, Monte Carlo robustness tests, out-of-sample validation, and multi-instrument confirmation · all on the same dedicated research environment. Only strategies that pass your full validation pipeline proceed.
Backtesting Server
Deploy
Move proven strategies to live trading VPS infrastructure
Once a strategy has passed validation, deploy it to a separate, dedicated live trading VPS · MetaTrader, cTrader, or NinjaTrader · where it operates in a low-overhead environment optimised for execution, not research.
Live Trading VPS
Infrastructure separation is a best practice, not a luxury. Running research workloads and live execution on the same server introduces unnecessary risk to both environments. Dedicated infrastructure for each stage of this workflow is the correct operational model.
Start with Backtest Servers Deploy finished strategies to a live trading VPS when ready.
Why Backtest Servers
How Backtest Servers answer SQX's infrastructure requirements
Backtest Servers are a separate product category · not a heavier trading VPS. Each characteristic below is a direct response to what StrategyQuant X research workloads actually require from their environment.
- Compute-oriented planning
- CPU and RAM planning are central to StrategyQuant X generation, robustness checks, and optimization workloads.
- Clean Windows Server workspace
- A Windows environment with full RDP access. Install StrategyQuant X, configure your data feeds, and reconnect to the same workspace when needed.
- Research-focused environment
- Separate research workloads from live trading terminals and execution infrastructure so each environment has a clearer role.
- Remote research continuity
- Research jobs run on the remote environment instead of your local machine, subject to platform state and normal infrastructure conditions.
- Separate product category
- Backtest servers are not the same product as live trading VPS. They have different specifications, different pricing structures, and different operational roles.
- Scale as your workflow evolves
- Start with the resource level appropriate for your current work. Upgrade when your workloads grow, without migrating to a different product.
Backtest Servers are the infrastructure product. Plans, specs, and details are on the product page. View Backtest Server Plans
Next Step
Your SQX workflow belongs on Backtest Servers.
Backtest Servers are the dedicated infrastructure product for StrategyQuant X research · persistent, compute-oriented, and completely separate from your live trading environment. See plans, specs, and everything included.
Once strategies are validated, deploy them to a live trading VPS · separate infrastructure built for execution, not research.
Live Trading VPS
Strategies validated? Deploy them live.
Once your strategies have passed your full validation pipeline, they belong on dedicated live trading infrastructure · not the same server where you built them. Choose the platform that matches your execution environment.
- MetaTrader VPSDeploy MT4 or MT5 Expert Advisors to a low-latency dedicated VPS, optimised for execution · not research. Purpose-built for live trading terminals.
- cTrader VPSRun cBots in a stable, isolated Windows environment. Separate live execution infrastructure designed for the cTrader platform.
- NinjaTrader VPSHost NinjaTrader strategies in a clean, dedicated environment. Optimised for execution, kept separate from your research infrastructure.
Keep environments separate. Live trading VPS plans are optimised for low-overhead execution · they are not suitable for running strategy generation or validation workloads. Use the right infrastructure for each stage of your workflow.
Checkout and setup clarity
What happens around StrategyQuant X infrastructure after you choose a plan.
The product pages help you choose infrastructure by workload. Checkout, billing, support, and software setup responsibilities stay clear before you commit.
Secure checkout
Plan selection and payment flow through the existing Stripe checkout path.
Dashboard and billing
Customers have a dashboard path for account, server, and billing context after order.
Support and status
Business-hours support targets and public status context are visible before checkout.
Uptime target
99.99% infrastructure uptime target for infrastructure availability, without trading-result promises.
No trading promises
Infrastructure guidance only. Trading software setup and market outcomes remain your responsibility.
Algo Hosting provides Windows VPS infrastructure, plan guidance, dashboard paths, and support context. You remain responsible for broker accounts, platform licensing, trading software configuration, and trading risk. Support during Central European business hours, Monday-Friday, excluding holidays and incident spikes.
FAQ
Common questions
StrategyQuant X → Backtest Servers
Build your edge on the right infrastructure.
Your research workflow deserves compute-oriented, persistent infrastructure · kept entirely separate from your live execution environment.
Questions? Get in touch and we will help you determine the right setup for your workflow.