Cloud execution — complete reference

A full, technical walk-through of how the Cloud engine takes a Telegram signal and turns it into a managed broker position — every step, every setting, and every safety guard. For a gentler setup overview, start with Cloud Execution setup.

› 1 · Architecture

• Two providers, one engine. Cloud runs on either MetaApi (per-account / pay-as-you-go) or api2trade (a fixed monthly fee — no deploy/top-up cycle, always connected). You choose per account when connecting; the entire pipeline below (sizing, SL/TP, management, commands) is identical on both. See api2trade setup.
• MetaApi maintains a persistent terminal connected to your broker. We talk to it over its region-specific client API (new-york, london, singapore, vint-hill); the region is detected once and cached so trade latency stays at ~1 round-trip.
• BYO credentials. Each cloud account runs on its owner's own MetaApi token or api2trade API key (you pay the provider directly; we add nothing). Your key and broker password are encrypted at rest and never logged.
• No device dependency. Because the terminal lives in the cloud, your trades execute whether your laptop is closed or your phone is off.

› 2 · Connecting an account

1. Signal Copier → EA Accounts → Connect Cloud Account.
2. Pick your provider (MetaApi or api2trade) and paste that provider's key once. MetaApi is MT4/MT5/cTrader; api2trade is MT4/MT5.
3. Enter login, password (trading, not investor), server, and platform (MT4/MT5).
4. We provision a MetaApi account and deploy it (~30s). State moves UNDEPLOYED → DEPLOYING → DEPLOYED and the terminal connects to your broker.
5. Assign the account to one or more channels (Target Account in channel settings). Leave a channel's target blank to broadcast to every account.

Use a demo account first to confirm the connection before going live.

› 3 · The signal → trade pipeline

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

1. Parse — regex → AI fallback → OCR (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 (risk/lot/max-lot).
3. Pips → price — if the channel sends SL/TP as pip distances, they're converted to absolute prices using the per-instrument pip size.
4. Filters — excluded pairs, min-confidence, ignore-no-SL/ignore-no-TP, pairs whitelist.
5. Transform — reverse-signal (if on), entry mode, lot sizing.
6. Execute — market or pending order placed on the broker via MetaApi, with SL and the first TP attached.
7. Record — the broker position id is stored on the signal row (this is what powers channel-scoped commands and journaling).
8. Manage — breakeven, trailing, partial closes, and extra TPs are handled continuously after the fill.

› 4 · Lot sizing

› 5 · Entry modes

• Market — "now/market" signals fire immediately at current price.
• Pending — when the entry is meaningfully away from price, a LIMIT/STOP order is placed (with optional expiry). BUY LIMIT/SELL STOP etc. 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 multiple entries around the signal price.

› 6 · Stop loss & take profit

• Absolute prices or pip distances (auto-converted). Up to TP1–TP10.
• TP lot splitting — divide the position across TP levels (equal or custom %), so partials close 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 verify the confirmed position state.
• RR-derived TP — when a signal has no TP, derive it from the SL distance × your R:R ratio.
• Hidden SL/TP — for stealth, the broker order can carry no visible SL/TP while the engine enforces them server-side (with a fallback pip stop).

› 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 submission. It changes timing but does not prove manual activity or compliance.
• Randomize comment — avoids identical order comments.
• FIFO mode — closes oldest-first to satisfy US/NFA brokers.
• Max concurrent trades and correlation limits cap exposure.

A live view of every account vs its limits is on Prop Firm Monitor.

› 9 · Position management (after the fill)

• Breakeven — by pips, by R:R, or by $ profit.
• Trailing stop — follows price by a step once started; can advance the TP too.
• TP cascade — when TP1 partials close, move the remaining lots' 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. Critically, 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/dashboard is account-wide by design.)

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

› 11 · Latency & reliability

• Region is cached so each order is ~1 round-trip to MetaApi's nearest data center.
• SL/TP live on the broker server — your positions are protected even if our service or your internet drops.
• Measured signal→fill latency is published on /status (real fills, not advertising).

› 12 · Security

• Broker credentials and provider tokens are encrypted at rest and sent to the cloud execution provider selected for that account (MetaApi or api2trade). Do not reuse credentials and do not grant withdrawal permission.
• Use your trading password, not the master/investor password if you want read-only elsewhere.
• You can disconnect an account at any time; we undeploy and remove the MetaApi terminal.

› 13 · Troubleshooting