Cloud execution — setup & complete guide

Updated 18 October 2026

Cloud execution uses a hosted broker connection, so you do not need to keep your own PC, VPS or MetaTrader terminal open. Eligible signals from your enabled channels pass through parsing, routing and risk checks before an order is attempted. Provider, broker and network availability still matter; dispatch is not proof of a fill.

› 1 · Set up everything in Cloud Workspace

1. Sign in and connect Telegram. Open Cloud Workspace or register here. Then enter your Telegram phone number and complete Telegram's code and two-step verification, if enabled. Never send login codes to support.
2. Check your Cloud plan. The separate Cloud pricing page shows Cloud Starter and Pro. Billing and offers stay outside the workspace. Cloud execution is not included in the free EA allowance. External provider charges may apply in addition to the plan.
3. Connect an isolated demo broker account. Choose a supported provider and platform. Enter the required provider key, broker login, trading password and exact server name in the connection form. Wait for the account's broker connection to be confirmed: DEPLOYED alone is not proof of broker connectivity or an executed trade.
4. Choose channels, save settings and verify. Search or show more channels, select one explicit Cloud destination, and review symbol mapping, lot/risk limits and TP selection. Save the channel configuration, then enable only the channel you intend to test. A channel is not enabled automatically. Moving an existing route replaces that route; the Cloud setup is not an instruction to broadcast to every account.

› 2 · How Cloud works

• Shared rules, provider-specific adapters. The engine applies channel settings, sizing and safety checks, then uses the selected provider. Available order types and management functions depend on the platform and adapter; check the compatibility matrix rather than assuming parity.
• Hosted broker connection. The provider connects to your broker. Provisioning, broker login, order acceptance and order fill are separate stages.
• Your own provider key. Provider credentials belong to the account owner. Review the provider's current terms and fees separately from your TradeJournal Pro subscription.
• No local terminal required. You can close your laptop, but the hosted services and broker must remain available. Check execution receipts and broker records rather than assuming a signal was filled.
• Idle accounts. An inactive hosted account may be suspended. Confirm its current connection state before resuming signals.

› 3 · The signal → trade pipeline

When a channel posts, the engine runs these steps in order:

1. Parse — regex, then the AI parser and OCR when needed (see signal formats). Commentary and analysis are rejected, not traded.
2. Route — the signal goes to the channel's target Cloud account(s), each with optional per-account overrides (lot, risk %, max lot, or off for that account).
3. Pips → price — SL/TP sent as pip distances are converted to prices with the instrument's pip size.
4. Map the symbol — the channel's symbol becomes your broker's exact name (symbol mapping).
5. Filter — excluded pairs, minimum confidence, ignore-no-SL/ignore-no-TP, pairs whitelist.
6. Transform — reverse signal (if on), entry mode, lot sizing.
7. Execute — a market or pending order is placed with its SL and TP attached.
8. Record — the broker position id is stored on the signal; this powers channel-scoped commands and your journal.
9. Manage — breakeven, trailing, partial closes and extra TPs are handled after the fill.

Other sources: Cloud Workspace focuses on Telegram setup. For TradingView, consult the webhook wizard and confirm your account's plan and route eligibility separately; do not assume every source or platform has the same capabilities.

› 4 · Lot sizing

Each channel has one Lot size mode, set in its Cloud channel configuration. The full explanation with worked examples is in lot size & risk management.

› 5 · Entry modes

• Market — "now/market" signals fire immediately at the current price.
• Pending — when the entry is meaningfully away from price, a LIMIT/STOP order is placed (with optional expiry). BUY LIMIT/SELL STOP and similar are honored explicitly.
• Range / all-price — an entry zone (2340–2345) splits the lot across the low/mid/high prices; Prefer entry keeps only the lower or higher side if you want.
• Smart entry / DCA — optional laddering of several entries around the signal price.

› 6 · Stop loss & take profit

• Absolute prices or pip distances (converted automatically). Up to TP1–TP10.
• Selected targets — choose All targets, One target or Custom. A missing selected target is not replaced with an unrelated target. Broker volume constraints and netting mode still apply.
• TP lot splitting — divide the position across TP levels (equal or custom %), so a part closes at each target.
• SL/TP override — OFF / IF_MISSING / ALWAYS with fallback pips. The executor requests the configured protection, but the broker can reject or modify an order, so check the confirmed position.
• RR-derived TP — when a signal has no TP, derive it from the SL distance × your R:R ratio.
• Hidden SL/TP — the broker order can carry no visible SL/TP while the engine enforces them server-side (with a fallback pip stop). Available on MetaApi only; MetaTrader API, Tickerall, FXAPIs and TradeLocker require broker-visible SL/TP.

› 7 · Filters & signal safety

› 8 · Prop-firm guards

• Daily loss / drawdown / profit-target limits — block new entries once a threshold is hit (existing trades aren't force-closed); resets at 00:00 UTC.
• Execution delay — waits a randomized number of configured seconds before sending. It changes timing but does not prove manual activity or compliance.
• Randomize comment — avoids identical order comments.
• FIFO mode — closes oldest-first for US/NFA brokers.
• Max concurrent trades and correlation limits cap exposure.

A live view of every account against its limits is in Prop Firm Mode.

› 9 · Managing the open position

• Breakeven — by pips, by R:R, or by $ profit.
• Trailing stop — follows price by a step once started; can advance the TP too.
• TP-based triggers — where supported, choose exactly which TP starts breakeven or trailing. A selected trigger is not permission to trade an unselected TP. See Cloud management settings for the controls and route limits.
• TP cascade — when TP1's part closes, move the remaining parts' SL to breakeven.
• Partial close — take a % off at a % of the way to TP.
• Smart profit lock — after TP1 of a signal, close a % of all that signal's remaining positions.
• Drawdown recovery — optional lot adjustment after a losing streak.

› 10 · Commands & channel separation

A channel can also post management commands — "close all", "move SL to breakeven", "close gold" — with multilingual parsing and an AI fallback for less-structured phrasing. A command from a channel only ever affects that channel's own positions: Cloud fills are tracked by broker position id, so a "close all" in Channel A never touches Channel B's trades. (A command you send yourself from the bot or dashboard is account-wide by design.)

TP-level messages — "close tp1", "Coupez tp1", "tp1 hit" — close only that level's position of a TP-split signal, never every TP. A blanket "modify TP" is only applied when you give a new TP price with no level ("TP 2400").

› 11 · Receipts, analytics & your trade journal

After your demo signal, check the signal's execution receipt, then verify the order or position in your broker account. Received, parsed, dispatched, accepted and filled are different outcomes. A skipped or rejected signal is not a completed trade. The same workspace shows Cloud-scoped analytics and the journal of broker-linked executed trades; empty sections mean there is no matching evidence yet, not an invitation to invent results. Test a management command on the isolated demo position and check the broker's resulting state before using live funds.

› 12 · Latency & reliability

• Actual latency varies by parsing path, provider, broker, instrument, market hours and network. No fixed signal-to-fill time is promised.
• Broker-side SL/TP remains with the broker only after acceptance. Hidden stops, trailing and other hosted management depend on service availability. A stop does not guarantee its execution price.
• See service status and reliability evidence. Read the scope and sample behind any published metric; a health check is not a broker-fill test.

› 13 · Security

• Use only the broker credentials required by your chosen provider. An investor/read-only password cannot place trades. Check the credential's actual permissions with the broker; never grant withdrawal permission.
• Enter provider keys only in the authenticated connection form, not in Telegram messages, screenshots or support tickets.
• Use separate credentials where possible. Revoke a compromised key with the provider and contact support.
• Disconnect requests removal from the provider. If removal fails, the app reports an error so it can be retried. Confirm removal and billing status with the provider; disconnecting is not a command to close existing broker positions.

› 14 · Plans, limits & Cloud vs EA

Cloud execution needs a Cloud plan; the free allowance and EA plans connect EA accounts only. Cloud Starter supports 1 broker account; Cloud Pro supports up to 3. Cloud has no public lifetime plan. Monthly and annual plans are available; separate provider charges may apply. See Cloud prices & billing on the website and managing accounts.

Cloud Pro is $59/month or $564/year paid upfront, for up to 3 broker accounts. Prices above are subscription prices, not broker deposits or provider hosting fees.

Both lines use the shared parser, but execution and management capabilities depend on the route. Check compatibility before choosing.

When a Cloud trade fails, you get a message on your linked Telegram bot and a push notification with the reason and what to check — at most one per account every six hours, so a disconnected account doesn't flood you.

› 15 · Troubleshooting