Multiple accounts

Size and Organize a VPS for Multiple Rithmic Accounts

Quick answer

Size a VPS for the applications, charts, history and automation it runs, not the number of account rows alone. Several accounts in one RTrader session can require less computing work than several separate charting applications. Measure the intended workload before selecting resources.

Educational software guidance. Trading involves risk. Read the financial and information disclaimers.

Inventory the workload

List each platform, supported connection, chart count, instrument subscription, historical-data load and locally managed strategy/copier. Record which applications depend on RTrader Pro plugin mode. A cloud receiver and a local desktop strategy have different hosting requirements.

Measure before buying more capacity

Measurement Interpretation
CPU during market bursts and history load Identifies sustained processing pressure; one busy core can matter
Committed memory and paging Helps distinguish adequate RAM from disk-backed memory pressure
Disk free space and write activity Logs/history can fill a small disk
Quote timestamps and application response Helps separate remote-display lag from delayed platform processing
Connection and order records Required to investigate routing delays; an RDP impression is insufficient

Use Windows Task Manager on the actual intended workload and keep headroom for bursts and updates. There is no verified universal rule that each account needs a fixed amount of RAM or that a Chicago VPS delivers one-millisecond orders.

Organize sessions and recovery

Use only platform-supported connection combinations. Do not bypass single-instance or data-session restrictions with copied installations. Keep account IDs distinct from connection labels and review each destination's state.

Keep the operating system supported, secure remote access, back up configurations and plan updates outside the intended trading session. Disconnecting an RDP viewer, signing out of Windows, rebooting and terminating a platform are different actions. Check which local order-management components would stop before ending the session.

Rithmic's desktop requirements describe Windows compatibility; they do not size a multi-platform workload. Compare current hosting quotes including Windows licensing, backups and management. Add software, data and copier fees separately for the actual intended configuration.

Screenshot references

Actual two-account Trader Dashboard on this VPS. Account IDs, names and balances are concealed; no account was traded or renamed.
Actual two-account Trader Dashboard on this VPS. Account IDs, names and balances are concealed; no account was traded or renamed.

Common questions

Does adding an account require another VPS?

Not inherently. It depends on the supported connection and workload.

Does a VPS prevent all disconnects?

No. Host, network, provider and application failures remain possible.

Should I leave RTrader running for plugin clients?

The supported plugin host must remain available to its clients.

Does cloud alert routing need my own VPS?

A cloud receiving service may host that path, but any separate local strategy or platform still needs its own host.

Financial and information disclaimers

Financial disclaimer

These guides explain software and workflows. They are for education, not financial, investment, tax, or legal advice. No example is a suggestion to buy or sell a product or use a trading strategy. Trading futures involves substantial risk and can lose money, including all funds you put at risk. Leverage can cause losses that exceed your starting funds. Automation can fail, send duplicate orders, or act late. Stop orders do not guarantee execution or a specific exit price; their behaviour depends on the order type and applicable exchange rules. Review your orders and positions, and consult a qualified professional for your own situation. Paper trades, examples, and past results do not predict live results or promise a profit.

Information disclaimer

This is general help based on the sources and check date shown on each page. Screens, settings, fees, data access, server names, error wording, menu paths, and product support can change or differ by app version, account, country, broker, prop firm, and FCM. The content may contain errors or become out of date; accuracy, completeness, and continuous service are not guaranteed. Check current Rithmic, broker, prop firm, and platform instructions before acting. Screenshots show where controls are located; they do not prove that an order test passed. These guides do not replace broker terms or risk notices. References to Rithmic, RTrader Pro, CME Group, NinjaTrader, Tradovate, TradingView, Apex, Topstep, TradeDay, Leeloo, Bulenox, Earn2Trade and other brands identify their products and do not imply any endorsement of this guide.

Documentation only. Live trading workflows are not certified or execution-tested.

Automate TradingView alerts to Rithmic

See the Rithmic integration