Cloud Copy Trading:
How TradeCopier’s Hosted Router Works
Cloud copy trading moves the copier's routing work to a hosted service, but the complete trade path still depends on the source account, destination account and any connector required by their platforms. TradeCopier's router can continue when you close the browser dashboard. Whether a personal computer or terminal may also be switched off depends on the exact account connection, not the word “cloud.”
Publisher disclosure: TradeCopier publishes this explanation of its own hosted product. The current cloud product page and platform page were checked September 23, 2026. This article does not report an independent speed, uptime, fill-quality or cloud-versus-local comparison. It does not promise that every broker, platform direction, order action or account type is supported.
Which parts of the copying path are hosted?
A typical permitted setup has a designated source account, a TradeCopier routing layer and one or more connected follower accounts. The hosted layer evaluates eligible source events against the configured copy rules, symbol mapping and sizing, then routes a destination request through a supported connection. The broker or platform decides whether the request is accepted and how it executes.
| Part | Job | Question to verify |
|---|---|---|
| Source account | Provides the trade event | How does this broker and platform deliver the event, and what must stay connected? |
| TradeCopier hosted router | Evaluates and routes eligible activity | Which group, copy rule, mapping and filter were active for the event? |
| Platform connector | Provides the supported account path where one is required | Does this route use a hosted session or a terminal component that must stay online? |
| Follower broker | Accepts, rejects and executes orders | What order, fill or deal and final position actually appeared? |
“Hosted router” and “nothing runs locally” are different claims. TradeCopier says the router is hosted and a personal VPS is not required for routing, while a platform connection may still use a terminal component. Confirm the precise source-to-follower direction and connector location before shutting down any device.
Can you close the browser or turn off your computer?
The browser is the dashboard, not the hosted routing process. Closing it does not by itself stop TradeCopier's router. The source and follower broker connections and any required connector must remain available. If a required connector is on your computer, powering off that computer can interrupt that route even though the hosted service remains online.
For example, imagine two otherwise identical account groups. Group A uses a connection that remains available independently of the user's browser. Group B needs a terminal component on a local machine. Closing the browser alone need not stop either hosted router; switching off Group B's connector can stop new activity for that group. This is an explanatory scenario, not a measured TradeCopier test or a statement that a particular broker uses one route.
Before relying on unattended copying, record each platform, broker server, account mode, connection method, authorization lifetime and responsible operator. Check the connection status after a password change, platform update or network interruption.
What does a routed trade prove about execution?
A source event, a copier decision, a destination request and a destination fill are separate observations. TradeCopier's activity logs can help identify the events the service handled, but the destination broker's order, fills or deals and final position are the evidence of what the account actually holds. MetaQuotes' MT5 OrderSend reference likewise warns that a successful submission return does not by itself prove that a requested market operation executed.
| Stage | What to retain | Possible unresolved state |
|---|---|---|
| Source | Event ID or order reference, action, symbol, quantity and time | Event was not available to the copier |
| Router | Eligibility, rule version, mapped symbol and calculated follower quantity | Filtered, delayed or failed transformation |
| Destination | Request ID, broker response, order, every fill and resulting position | Rejected, partial, unfilled or unknown result |
Do not turn a routing-time claim into an “execution latency” claim. The source observation, copier processing, network delivery, broker response and final fill have different timestamps and owners. Their values vary with platform, network, broker, instrument and market conditions. An earlier live-traffic execution number on this page lacked a published measurement method and has been removed.
What changes compared with a personal VPS or local copier?
With TradeCopier, you do not need to operate a personal VPS solely to host the routing layer. A local or customer-managed VPS setup instead makes the operator responsible for that machine, its updates, monitoring and restart behavior. Neither architecture automatically wins on speed, availability, security or cost for every route. A cloud path can have different network legs; a local path can have its own broker distance and failure points. Compare end-to-end observed outcomes for the actual accounts rather than a generic millisecond estimate.
Cloud hosting also changes which party manages parts of the service and how account access is granted. Confirm the authentication method, trading permissions, credential revocation process, supported order actions and data visibility for your route. Copying never requires withdrawal permission, but you must verify the actual access granted to every connection.
If you are selecting among providers, use the separate hosted-copier comparison. This article explains TradeCopier's own operating path rather than ranking vendors or subscriptions to other traders' signals.
What should you do after an interruption?
The TradeCopier cloud page warns that a service or connection interruption can prevent new source trades from being copied. Positions already open at a broker generally remain there. Do not assume the missing event will replay, or that two accounts will reconcile automatically when the connection returns.
- Pause the affected copying route while the source, connector or follower state is uncertain.
- Compare source orders and positions with every follower's broker orders, fills and current positions. Include pending orders and protection changes.
- Match each event to the copier activity record and identify any missing or rejected request. Mark absent evidence as unavailable, not successful.
- Decide with the account owner whether a new order, close or correction is permitted. Each such action has its own execution risk; do not automatically retry an uncertain instruction.
- Verify the connection and account states before resuming, then retain the incident and reconciliation record.
The permanent Free plan currently includes one trading group and three total accounts, which can be enough to test a small permitted setup. Confirm the exact route and order actions first. The practical cloud setup and acceptance guide provides a separate connection worksheet; this page is the architecture and failure-path explanation.
Quick answers
Frequently Asked Questions
Find answers to the most common questions about this topic.
Does TradeCopier need a personal VPS?
Its routing layer is hosted, so a personal VPS is not required solely for routing. An individual account route may still require a terminal component or other connector to remain available.
Will copying continue when I close the browser?
Closing the dashboard does not by itself stop the hosted router. The source and follower connections and any required connector still need to work.
Can I turn off the computer that runs my trading terminal?
Only after confirming that your exact route does not depend on a connector on that computer. The location of required platform components varies by account connection.
Is cloud copying always slower than a local copier?
No universal comparison is established here. Both setups have different network and broker paths. Measure the same source-to-destination stages and actual fills for your accounts before drawing a speed conclusion.
Does a routed event mean the follower trade was filled?
No. Check the destination broker response, order, fills or deals and resulting position. A copier log or successful request is not proof of completed execution.
What happens to open positions if the cloud connection fails?
Existing broker positions generally remain at the broker; new copies may be missed. After reconnecting, compare source and follower orders and positions and do not assume missed actions replayed.
