Your MultiCharts strategy is monitoring several futures symbols when the computer running it enters sleep mode or loses its internet connection. Charts stop receiving prices, the broker connection closes, and the strategy cannot submit its next order. MultiCharts does not require a VPS, but a MultiCharts VPS is recommended when strategies and data connections must remain active without depending on a home computer.
Manual charting and strategy development can run on a normal Windows workstation. Automated execution, portfolio trading, multiple data feeds, and unattended position management create stronger uptime and resource requirements.
This guide explains what MultiCharts does, which workloads benefit from remote hosting, what server resources to choose, and how to move and test the platform before live use.
What Is MultiCharts?
MultiCharts is a charting and automated trading platform that lets traders build and run strategies in PowerLanguage or .NET across supported brokers and data feeds. It does not require a VPS, but automated and multi-symbol setups benefit from running on a stable Windows server throughout the trading week.
PowerLanguage is the scripting language used by standard MultiCharts. It is designed for high compatibility with TradeStation EasyLanguage, which allows many traders to reuse or adapt existing indicators and strategies.
MultiCharts .NET is a separate version built for traders who want to develop studies and automated systems with .NET languages. The platform supports C# and Visual Basic development through its .NET programming environment.
| MultiCharts component | Primary purpose |
| Charts | Display historical and real-time market data |
| PowerLanguage | Create indicators, functions, and automated strategies |
| MultiCharts .NET | Develop studies and strategies with .NET languages |
| QuoteManager | Configure symbols and market-data sources |
| Broker Profiles | Store broker connection settings |
| Portfolio Trader | Backtest and automate strategies across many instruments |
| Scanner | Monitor multiple symbols for defined conditions |
| Strategy Orders Monitor | Review strategy-generated order activity |
| Order and Position Tracker | Monitor broker orders, positions, and accounts |
| Optimization tools | Test different strategy parameter combinations |
MultiCharts describes its platform as software for charting, backtesting, strategy optimisation, and automated trading. Its PowerLanguage environment is stated to be 99% compatible with EasyLanguage. (Source: MultiCharts Features, 2026).
The platform does not supply every broker account or market-data subscription itself. Traders still need a compatible brokerage, data vendor, and the permissions required for the instruments they want to trade.
What Can You Do With MultiCharts?
MultiCharts can chart markets, test trading ideas, automate strategies, monitor portfolios, scan symbols, and route orders through supported broker connections. Its main strength is combining analytical tools with programmable execution inside one Windows environment.
A trader can use MultiCharts only for analysis or connect it to live brokerage accounts. The platform can receive data from one provider while sending orders through another supported broker.
| Function | How traders use it |
| Multi-timeframe charting | Compare price action across several intervals |
| Technical indicators | Apply built-in or custom market studies |
| Strategy backtesting | Test rules against historical data |
| Walk-forward analysis | Evaluate strategies across changing test periods |
| Parameter optimization | Compare different strategy inputs |
| Automated execution | Submit strategy-generated orders |
| Portfolio testing | Analyse one strategy across many instruments |
| Market scanning | Identify symbols that meet defined conditions |
| Manual chart trading | Place orders directly from charts |
| Data merging | Combine historical and real-time data sources |
| Custom development | Create PowerLanguage or .NET studies |
| Broker monitoring | Review orders, positions, and account activity |
The current MultiCharts feature set includes more than 280 built-in indicators, signals, and drawing tools. Advanced editions also include Portfolio Trader, walk-forward optimisation, matrix optimisation, and self-adaptive trading functions. (Source: MultiCharts Purchase Comparison, 2026).
Chart analysis and live execution are separate decisions. A strategy that performs well in historical testing still needs realistic assumptions for commissions, slippage, liquidity, and order handling before it is used with a live broker.
How Does MultiCharts Handle Automated and Portfolio Trading?
MultiCharts handles automated trading by applying a signal to a chart or portfolio and forwarding generated orders through the selected Broker Profile. Portfolio Trader extends this process across groups of instruments under shared capital and money-management rules.
Automated trading means that software evaluates defined rules and submits orders without requiring each action to be entered manually. The platform must remain open, connected, and authorised whenever the strategy is expected to act.
| Automated trading stage | MultiCharts function |
| Receive prices | Connects through the configured data source |
| Calculate strategy rules | Runs the applied PowerLanguage or .NET signal |
| Determine position state | Compares strategy and broker information |
| Generate an instruction | Creates the intended entry, exit, or modification |
| Apply quantity rules | Calculates the order size |
| Route the order | Uses the selected Broker Profile |
| Receive broker response | Updates order and position status |
| Record activity | Writes platform and strategy logs |
Portfolio trading applies strategy logic across several symbols instead of one chart. MultiCharts Portfolio Trader supports backtesting, forward testing, and automated execution across a portfolio of financial instruments. (Source: MultiCharts Portfolio Trader, 2025).
A portfolio can contain hundreds of stocks, futures contracts, forex pairs, or other supported instruments. Resource requirements increase with the number of symbols, historical bars, strategy calculations, and live subscriptions. (Source: MultiCharts Portfolio Trading, 2026).
Automated execution should be enabled only after the signal has been tested with the intended broker profile. A valid backtest does not confirm that live symbol mapping, order types, account permissions, and position synchronisation are correct.
Does MultiCharts Need a VPS for Reliable Operation?
MultiCharts does not need a VPS for basic charting or attended manual trading. A VPS becomes useful when the platform, strategy engine, broker connection, or data feed must continue running after the trader leaves the computer.
A virtual private server is a remote Windows environment with allocated CPU, RAM, storage, and network resources. The trader connects through Remote Desktop, but MultiCharts runs on the server rather than on the viewing device.
| MultiCharts use | Is a VPS needed? | Main reason |
| Historical chart analysis | No | Continuous connectivity is unnecessary |
| Strategy development | No | The user can restart the platform |
| Manual trading while present | Optional | The trader can respond to disruptions |
| Automated single-symbol strategy | Recommended | The chart and signal must stay active |
| Portfolio automation | Strongly recommended | Many instruments require continuous processing |
| Several broker connections | Recommended | Each connection must remain available |
| Overnight alerts | Recommended | Local alerts stop when the host shuts down |
| Unattended order management | Strongly recommended | Future strategy actions depend on the platform |
| Long-running optimization | Optional | High-resource local hardware may be faster |
A VPS protects the platform from home power cuts, router restarts, residential internet failures, and local sleep settings. It does not prevent broker outages, market-data interruptions, invalid strategy logic, or software errors.
The MultiCharts VPS setup process covers the practical difference between running the platform on a home computer and operating it through a remote Windows server.
Which MultiCharts Setups Benefit Most From a VPS?
Multi-symbol automation, portfolio trading, several broker profiles, and multiple data feeds benefit most from a VPS. These configurations require longer operating hours and more consistent access to processing, data, and order-routing services.
The need for remote hosting is determined by what would stop if the local computer went offline. A submitted broker-held order can remain active, while a future strategy decision cannot occur without a running strategy engine.
| MultiCharts workload | VPS benefit | Main dependency |
| Multi-symbol strategy | Keeps every symbol processing | CPU, RAM, and market data |
| Portfolio Trader automation | Maintains portfolio calculations | Continuous platform operation |
| Several Broker Profiles | Keeps order connections available | Network and authentication |
| Separate data and broker feeds | Maintains both connections | Stable routing |
| Overnight futures strategy | Operates beyond normal work hours | Server uptime |
| Forex strategy | Remains active through the trading week | Broker connectivity |
| Scanner with alerts | Continues monitoring symbols | Data feed |
| Several platform instances | Provides scalable resources | CPU, RAM, and storage |
Multi-Symbol Automated Strategies
A multi-symbol strategy evaluates data from several instruments, so its processing and subscription requirements increase with each added market.
A strategy can monitor one primary chart while referencing additional data series. Portfolio Trader can also apply strategy logic across a larger instrument list.
Resource use increases with:
- Instrument count
- Tick frequency
- Historical bars
- Strategy complexity
- Indicator count
- Calculation frequency
- Portfolio money-management rules
- Simultaneous broker orders
A strategy using 100 symbols creates a different workload from a strategy using two currency pairs. The server should be sized from the complete portfolio rather than one test chart.
MultiCharts is a multi-process and multithreaded application. Its 64-bit version can access available system memory more efficiently, which supports larger numbers of charts, studies, and data records. (Source: MultiCharts Technical Specifications, 2026).
Multiple Broker and Data Feed Connections
MultiCharts can use separate connections for market data and order execution, so both services must remain available for a live strategy to work correctly.
Data sources are configured through QuoteManager. Broker connections are configured through Broker Profiles inside MultiCharts.
| Connection | Configuration area | Main purpose |
| Data source | QuoteManager > Tools > Data Sources | Supplies historical and real-time prices |
| Broker Profile | MultiCharts broker configuration | Routes orders and receives account updates |
| Symbol configuration | QuoteManager | Maps instruments to the selected data source |
| Strategy broker selection | Strategy auto-trading settings | Chooses the execution destination |
| Account selection | Broker Profile or order interface | Identifies the trading account |
MultiCharts states that the data-provider connection must be configured in QuoteManager, while the broker connection is configured inside MultiCharts. A valid data connection does not prove that the broker session is ready to accept orders. (Source: MultiCharts Broker Profiles Overview, 2025).
A VPS can keep both connections active. It cannot correct expired credentials, missing market-data permissions, unsupported instruments, or provider-side maintenance.
When Is a Home Computer Enough for MultiCharts?
A home computer is enough when MultiCharts is used for attended charting, manual trading, strategy development, or backtesting that can be restarted after an interruption. The trader must be able to tolerate local power, hardware, and internet failures.
Local hardware can be preferable for research because it can support several monitors, larger storage capacity, and high-core-count processors. These advantages matter more for development and optimisation than for a lightweight live strategy.
| Home-computer workload | Why local operation can work | Main limitation |
| Manual chart trading | The trader remains present | A connection failure interrupts access |
| PowerLanguage development | Errors can be corrected immediately | Development can affect live processes |
| .NET strategy coding | Local tools are easy to access | Compilers can compete with live workloads |
| Backtesting | Continuous broker access is unnecessary | Large tests can consume the computer |
| Optimization | High-end local CPU can be used | The machine may become unresponsive |
| Chart review | No unattended action is required | Data collection stops after shutdown |
| Simulation | No live account is exposed | Infrastructure reliability is not fully tested |
A home setup becomes unsuitable when a required action may occur while the trader is asleep, travelling, or disconnected. The relevant question is whether closing Windows would stop an important trading function.
A reliable home environment also requires stable electricity, a wired connection, cooling, update controls, backups, and recovery procedures. A high-performance computer alone does not address these dependencies.
What Happens If MultiCharts Loses Power or Internet Access?
MultiCharts stops receiving live data and cannot submit new broker instructions when its host loses power or internet access. Orders already accepted by the broker may remain active, but locally calculated strategy actions cannot continue.
The outcome depends on where each order or rule is held. A server-side stop can remain active without MultiCharts, while a future strategy-generated exit requires the platform to receive data and calculate the condition.
| Component | Effect of power or internet loss |
| Real-time chart | Stops updating |
| Scanner | Stops evaluating new prices |
| Automated signal | Cannot process new events |
| New broker order | Cannot be submitted |
| Working broker-held order | Can remain active |
| Local trailing logic | Stops calculating modifications |
| Portfolio strategy | Stops processing the instrument list |
| Alert | Cannot trigger from new data |
| QuoteManager connection | Disconnects from the data provider |
| Broker Profile | Loses live order and account communication |
A temporary connection failure can also create a state difference between MultiCharts and the broker. The platform may miss an acknowledgement, partial fill, cancellation, or position update.
After reconnection, compare the Order and Position Tracker with the broker’s official records. Do not submit replacement orders until open orders, fills, and positions have been reconciled.
A VPS moves the active platform away from home-side failures. It does not protect against an outage at the broker, data provider, exchange, or hosting data centre.
What VPS Specifications Does MultiCharts Need?
A current MultiCharts VPS should start with at least 4 fast vCPU cores, 8 GB of RAM, and 40 GB or more of SSD or NVMe storage. Portfolio automation, many charts, and several data connections can require 16 to 32 GB of RAM and additional processor capacity.
MultiCharts lists a quad-core processor at 3 GHz or higher, 8 GB of RAM, and 30 GB of storage as its current minimum specification. Its recommended specification rises to an eight-core processor at 4 GHz or higher, 32 GB of RAM, and 100 GB of SSD storage.
| Workload | vCPU | RAM | Storage | Suitable use |
| Light manual setup | 4 | 8 GB | 40 GB NVMe | Several charts and one data source |
| Moderate automated setup | 4 | 8 to 16 GB | 60 GB NVMe | A few strategies and one broker |
| Portfolio trading | 4 to 8 | 16 to 32 GB | 100 GB NVMe | Many symbols and portfolio calculations |
| Several connections | 6 to 8 | 16 to 32 GB | 100 GB NVMe | Multiple brokers and data feeds |
| Heavy power-user setup | 8 or more | 32 GB or more | 150 GB or more NVMe | Tick charts, many studies, and optimisation |
| Large research environment | Dedicated CPU | 64 GB or more | Large NVMe storage | Intensive backtesting and development |
The official power-user specification reaches 16 processor cores, 128 GB of RAM, and 500 GB of NVMe storage. MultiCharts defines a power user as someone running at least five tick charts, ten interval charts, or fifteen indicators or signals on a chart. (Source: MultiCharts System Requirements, 2026).
These official figures cover broad platform use and can exceed the needs of a small live strategy. Measure the actual workload before selecting an oversized plan.
CPU and Memory Requirements
CPU speed controls how quickly MultiCharts calculates studies and strategies, while RAM holds charts, historical data, workspaces, portfolio state, and active applications.
MultiCharts can distribute several tasks across processor cores. Optimisation and multi-process workloads benefit from additional cores, while individual calculations still benefit from strong per-core speed.
Monitor these values in Windows Task Manager:
- Total CPU use
- Per-process CPU use
- Available memory
- Committed memory
- Disk active time
- Page file activity
- QuoteManager resource use
- Broker connector resource use
Memory pressure can force Windows to move active data to slower disk-based paging. Sustained CPU saturation can delay chart updates and strategy calculations during fast market periods.
The MultiCharts performance guide explains how excessive history, unstable feeds, and inefficient studies can make charts stop advancing even when the platform remains open.
Storage and Windows Compatibility
MultiCharts requires a supported 64-bit Windows environment and .NET Framework 4.8. Fast storage improves chart loading, database access, historical-data processing, backups, and application startup.
MultiCharts currently supports Windows 11 on Intel 64 or AMD64 processors. The exact Windows Server version should be confirmed with the current platform and every broker connector before deployment.
Storage demand increases with:
- Historical tick data
- Several data sources
- Large portfolio databases
- Extensive platform logs
- Optimization results
- Backups
- Multiple installations
- MultiCharts and MultiCharts .NET together
NVMe storage reduces local file-access delays. It does not shorten the network distance between MultiCharts and the broker.
Keep free space above the minimum required for installation. Historical databases and backups can grow after the platform enters continuous use.
How Do Charts, Indicators, and Strategy Calculations Affect Performance?
Charts, indicators, and strategies increase resource use according to their update frequency, historical range, symbol count, and calculation complexity. A small number of tick-based studies can create more load than many simple end-of-bar indicators.
A chart must process incoming data, update every applied study, redraw visual elements, and evaluate attached signals. Hidden workspaces can still retain data and consume memory.
| Platform item | Main resource effect | Practical control |
| Additional chart | Adds data and drawing work | Close unused charts |
| Tick chart | Processes frequent events | Use only where required |
| Long history | Increases memory and recalculation time | Reduce loaded history |
| Multiple data series | Synchronises several streams | Remove unused series |
| Complex indicator | Adds repeated calculations | Test each study separately |
| Portfolio signal | Runs logic across many instruments | Limit symbols to the strategy universe |
| Short update interval | Recalculates more frequently | Use a suitable interval |
| Custom DLL | Adds external code and dependencies | Test in isolation |
| Optimization | Uses substantial CPU | Separate it from live execution |
| Several workspaces | Retains more platform objects | Close inactive workspaces |
A strategy that recalculates its complete history after each update can consume resources even when its trading rules appear simple. Code efficiency should be reviewed before solving every slowdown with more hardware.
MultiCharts compiles PowerLanguage studies for efficient execution, but custom logic can still perform unnecessary loops, file operations, or repeated data requests. The platform cannot automatically correct inefficient user code.
Measure performance during an active session. Quiet-market CPU use does not show how the workspace behaves when tick volume increases.
Where Should You Locate a MultiCharts VPS?
Locate the MultiCharts VPS near the broker or order-routing server used for live execution. The trader’s home location matters only for Remote Desktop responsiveness, not for the platform-to-broker order path.
A data feed and broker can use different infrastructure. Traders using separate services should test both routes and prioritise the connection that is most sensitive to delay.
| Primary connection | VPS region to test first |
| New York broker infrastructure | New York |
| London broker infrastructure | London |
| Frankfurt broker or exchange service | Frankfurt |
| Amsterdam financial infrastructure | Amsterdam |
| CME futures connection | Chicago |
| Singapore broker server | Singapore |
| Tokyo broker server | Tokyo |
| Hong Kong broker server | Hong Kong |
Latency is the time required for a message to travel between two systems. A lower and more consistent round-trip time can improve broker acknowledgements, but it cannot guarantee a specific fill.
The MultiCharts automated trading setup explains why production strategy hosting should follow the broker location rather than the developer’s physical location.
Network routing should be tested after the broker profile is connected. A server in the correct city can still use an indirect carrier path.
How Do Broker and Data Feed Locations Affect Latency?
Broker and data-feed locations affect different parts of the MultiCharts workflow. The data route controls how quickly prices reach the platform, while the broker route controls how quickly orders and account updates travel.
Using one company for both services can simplify the path. Using a specialist feed for charts and a separate broker for execution creates two independent connections.
| Connection stage | Main latency effect |
| Data provider to QuoteManager | Determines when MultiCharts receives prices |
| QuoteManager to chart | Affected by local processing |
| Chart to strategy | Affected by calculation speed |
| Strategy to Broker Profile | Affected by local application resources |
| Broker Profile to broker | Affected by VPS location and network routing |
| Broker to exchange or liquidity venue | Controlled by broker infrastructure |
| Exchange response to broker | Controlled by venue and market conditions |
| Broker response to MultiCharts | Affected by the return network route |
A low-latency broker connection does not correct stale market data. A fast feed does not help when the broker endpoint is located across an ocean.
MultiCharts allows traders to select a broker for trading and a separate data source for charting. Both symbol definitions and session settings must align so that the strategy acts on the intended market. (Source: MultiCharts Data and Broker Connection, 2025).
A MultiCharts VPS should be placed around the live execution route, then sized around the full data and strategy workload.
Latency measurements should include variation over time. Jitter, packet loss, and reconnect frequency can matter more than one unusually low ping result.
How Do EasyLanguage and .NET Strategies Run on a VPS?
PowerLanguage and .NET strategies run on a VPS in the same way they run on a compatible Windows computer. The code is installed or imported into the correct MultiCharts edition, compiled, applied, connected, and tested before automated execution is enabled.
Standard MultiCharts uses PowerLanguage, which is designed for extensive EasyLanguage compatibility. MultiCharts .NET uses the .NET development environment for strategy and indicator creation.
| Development option | Platform | Main use |
| PowerLanguage | MultiCharts | EasyLanguage-compatible signals and indicators |
| C# | MultiCharts .NET | .NET strategy and application development |
| Visual Basic | MultiCharts .NET | .NET-based studies and strategies |
| Custom DLL | Supported environment | External calculations or integrations |
| Portfolio Money Management keywords | Portfolio Trader | Portfolio-level allocation and controls |
PowerLanguage studies can operate on charts, in Scanner, and in Portfolio Trader. The same script can therefore create different resource demands depending on where and how widely it is applied. (Source: MultiCharts Scripts, 2025).
MultiCharts .NET supports automated order execution after a strategy has been written, debugged, optimised, and enabled. Its auto-trading modes include synchronous and asynchronous operation. (Source: MultiCharts .NET Programming Guide, 2026).
Every external dependency must also exist on the VPS. This includes custom DLLs, database drivers, configuration files, API keys, and required .NET libraries.
Do not assume that successful compilation confirms live readiness. Test symbol mapping, order quantities, broker permissions, session behaviour, and restart recovery separately.
How Do You Install or Move MultiCharts to a VPS?
Install MultiCharts on the VPS from the official installer, then restore a verified backup of the required workspaces, studies, databases, and connection settings. Keep the original installation unchanged until the VPS environment has passed a complete test.
A clean installation reduces the risk of transferring damaged program files. The backup should contain user data rather than an uncontrolled copy of every temporary file.
| Step | Action | Required result |
| 1 | Connect to the VPS through Remote Desktop | Windows desktop opens |
| 2 | Apply Windows updates | Current security updates are installed |
| 3 | Confirm .NET Framework 4.8 | Platform requirement is available |
| 4 | Download MultiCharts | Official installer is saved |
| 5 | Install the correct edition | MultiCharts or MultiCharts .NET opens |
| 6 | Activate the license | Platform access is confirmed |
| 7 | Restore user data | Workspaces and studies appear |
| 8 | Configure data sources | QuoteManager connects correctly |
| 9 | Configure Broker Profiles | Broker login succeeds |
| 10 | Verify symbols | Charts load the intended instruments |
| 11 | Test simulation | Strategies create the expected instructions |
| 12 | Create a new backup | Working VPS state is recoverable |
MultiCharts provides dedicated Backup and Restore utilities and recommends backing up user data before migrations or major configuration changes. All MultiCharts components should be closed before the backup or restore process begins. (Source: MultiCharts Backup and Restore, 2025).
Check file paths after restoration. Custom scripts can fail when they reference a drive, folder, database, or network path that existed only on the original computer.
Restore one production environment before adding research workspaces. A smaller initial deployment makes connection and performance problems easier to isolate.
Will MultiCharts Keep Running After Remote Desktop Is Closed?
Yes, MultiCharts keeps running when Remote Desktop is disconnected without signing out of Windows. Signing out, restarting, or shutting down the VPS closes the applications in the active user session.
Remote Desktop is only the viewing and control interface. MultiCharts, QuoteManager, and broker connectors run on the remote Windows server.
| Remote action | MultiCharts result |
| Close the RDP window | Continues running |
| Select Disconnect | Continues running |
| Lose home internet access | Continues on the VPS |
| Lock the remote session | Continues running |
| Select Sign out | Closes with the user session |
| Restart Windows | Stops during the restart |
| Shut down the VPS | Stops completely |
| Session timeout logs off user | Closes with the session |
Microsoft states that disconnecting a Remote Desktop user leaves all applications running. Logging off ends the session and closes the applications. (Source: Microsoft Disconnect-RDUser, 2026).
Use Disconnect after confirming that MultiCharts, QuoteManager, data feeds, broker profiles, and automated strategies show the intended status.
Review Windows session policies before live use. A provider or administrator can configure a disconnected-session time limit that eventually logs the user off.
How Should You Manage Updates, Restarts, and Trading Sessions?
Schedule Windows, MultiCharts, broker connector, and strategy updates outside active trading periods. Treat every restart as a controlled recovery event that requires connection, strategy, order, and position checks.
An update can change platform behaviour, symbol definitions, broker APIs, .NET dependencies, or custom-study compatibility. Production software should not be updated minutes before an unattended session.
| Maintenance step | Required action |
| Review positions | Confirm open exposure and working orders |
| Disable automated execution | Prevent orders during maintenance |
| Save workspaces | Preserve current platform changes |
| Create a backup | Protect studies, data, and settings |
| Close MultiCharts components | Prevent database or file corruption |
| Apply updates | Install approved versions |
| Restart Windows | Complete operating-system maintenance |
| Start MultiCharts | Confirm normal application launch |
| Connect data sources | Verify QuoteManager status |
| Connect broker profiles | Confirm account and order-routing access |
| Reconcile positions | Compare platform and broker records |
| Re-enable strategies | Activate only after all checks pass |
Do not combine an operating-system update, broker-connector update, and strategy revision in one untested maintenance window. Changing one component at a time makes a failure easier to identify.
Market sessions also affect maintenance timing. Forex, futures, equities, and cryptocurrency markets have different breaks and weekend schedules.
Automatic startup can reopen supporting applications after a planned restart. Automated trading should not resume until the system has verified the correct account, positions, data, and working orders.
How Can You Test MultiCharts on a VPS Before Trading Live?
Test MultiCharts on the VPS with simulation or the smallest practical exposure before enabling full live automation. The test must cover data, broker execution, strategy state, disconnections, Remote Desktop behaviour, and server restarts.
A strategy that generates a simulated entry has passed only one part of the test. Live readiness requires every stage from market data to broker status to behave correctly.
| Test | Action | Passing result |
| Data source | Connect through QuoteManager | Real-time charts update correctly |
| Historical data | Reload required symbols | No unresolved gaps remain |
| Broker Profile | Connect the test account | Account and order status appear |
| Manual simulated order | Submit an entry and exit | Symbol and quantity are correct |
| Strategy signal | Enable in simulation | Expected instructions appear |
| Stop and target | Create protective orders | Order relationship is correct |
| Partial fill | Observe or simulate one | Remaining quantity stays synchronised |
| Data interruption | Disconnect the feed | Strategy follows the intended behaviour |
| Broker interruption | Disconnect order routing | No duplicate order appears after recovery |
| RDP disconnection | Close the remote window | MultiCharts remains active |
| VPS restart | Restart during testing | Recovery process restores the environment |
| Backup restore | Restore the tested backup | Workspaces and studies reopen correctly |
| Resource test | Run the full portfolio | CPU and RAM retain headroom |
Compare the strategy’s internal market position with the broker’s actual position after every interruption. A mismatch can create an unintended entry, exit, or reversal.
Record CPU, memory, disk, data latency, broker latency, and order acknowledgement times. Repeat the test during an active market because quiet conditions do not reproduce peak update volume.
Keep research and live execution separate during testing. Optimisation can use enough processing capacity to delay an automated strategy.
MultiCharts VPS Hosting: Automation, Connectivity, and Resource Essentials
MultiCharts VPS hosting should provide enough CPU and RAM for the complete strategy workload, stable access to every data and broker connection, and a tested recovery process. The server should be located near the order-routing endpoint and remain available through the required trading sessions.
A service-level agreement, or SLA, defines the provider’s committed availability. A 99.99% uptime SLA permits approximately 52.56 minutes of potential downtime per year, compared with about 8.76 hours at 99.9%.
| Requirement | Practical target | Why it matters |
| Uptime | 99.99% SLA | Reduces host-side interruptions |
| CPU | At least 4 fast vCPU cores | Supports MultiCharts calculations |
| RAM | At least 8 GB | Matches the current platform minimum |
| Portfolio RAM | 16 to 32 GB or more | Supports many symbols and strategies |
| Storage | SSD or NVMe | Improves database and history access |
| Windows | Compatible with 64-bit Windows | Supports MultiCharts and .NET |
| Data connection | Stable route to the provider | Maintains current strategy inputs |
| Broker connection | Low and consistent latency | Improves order communication |
| Remote access | Secured RDP | Supports monitoring and administration |
| Recovery | Tested restart procedure | Restores platform state safely |
| Resource allocation | Guaranteed CPU and RAM | Reduces shared-host contention |
| Backup | Current platform backup | Protects strategies and configuration |
A suitable Forex VPS plan should be selected from the full MultiCharts workload. A small charting setup and a 100-symbol portfolio should not use the same resource assumptions.
TradingFXVPS uses Microsoft Hyper-V with guaranteed resource allocation and a no-overselling policy. Available locations include New York, London, Frankfurt, Amsterdam, Chicago, Singapore, Tokyo, and Hong Kong.
The infrastructure cannot correct an inefficient strategy, invalid broker profile, or unsupported symbol. Performance, connection, and software problems must be diagnosed separately.
Keep MultiCharts and Your Strategies Running Around the Clock
Prepare the VPS around the complete MultiCharts environment, including QuoteManager, Broker Profiles, workspaces, strategies, portfolio calculations, custom files, and recovery controls. Test the full setup in simulation, verify resource headroom, and confirm that every required application remains active after Remote Desktop is disconnected.
TradingFXVPS can provide a Windows trading environment with a 99.99% uptime SLA, guaranteed Hyper-V resources, NVMe storage, and server locations near major broker and futures infrastructure. The appropriate plan depends on the number of charts, instruments, strategies, data feeds, broker connections, and MultiCharts editions running together.
For help choosing the right resources and server location, contact the TradingFXVPS team.
Frequently Asked Questions About MultiCharts VPS Hosting
Can MultiCharts run continuously on a Windows VPS?
Yes, MultiCharts can run continuously on a compatible Windows VPS. The Windows session, platform components, data sources, and broker connections must remain active.
Maintenance and external provider outages can still interrupt the setup. Test the recovery process before live automation.
How much RAM does MultiCharts need on a VPS?
MultiCharts currently lists 8 GB of RAM as its minimum. The official recommended specification uses 32 GB for more demanding charting and analysis.
A moderate automated setup can start with 8 to 16 GB when testing confirms enough headroom. Portfolio trading and large historical databases can require more.
Is a VPS necessary for MultiCharts automated strategies?
A VPS is not technically required, but it is recommended for unattended automated strategies. A home computer works only while its power, Windows session, internet connection, and platform remain available.
A VPS removes home-side dependencies. It does not replace correct strategy, broker, and risk configuration.
Can one VPS run MultiCharts with several broker connections?
Yes, one VPS can run MultiCharts with several supported broker connections when it has enough CPU, RAM, and network capacity. Each Broker Profile maintains its own settings and connection state.
Test every broker separately before combining them. Different brokers can use different symbols, sessions, APIs, and order rules.
Will closing Remote Desktop stop MultiCharts strategies?
No, disconnecting Remote Desktop normally leaves MultiCharts strategies running. Signing out of Windows or shutting down the server closes the platform.
Use Disconnect instead of Sign out. Check that no Windows policy automatically logs off disconnected sessions.
Can MultiCharts and MultiCharts .NET run on the same VPS?
Yes, MultiCharts and MultiCharts .NET can run on the same VPS when the server has enough resources and both installations are correctly licensed. Each edition creates its own platform, strategy, and connection workload.
Start with at least 16 GB of RAM for a moderate combined setup. Monitor CPU, memory, storage, and broker connectivity before adding more charts or strategies.