how it works
How a signal becomes an order on your own PC
Six stages from chat message to broker result: read locally, parsed deterministically, guarded, queued durably, delivered over loopback, and reported back with the broker's own result code. No cloud server sits on the execution path.
Free 7-day trial · Windows 10/11, no payment method
A mechanism reference, not a setup guide
This page describes the pipeline every signal travels, whatever the source: what happens at each stage, where it happens (your device or the cloud), what can stop a signal there, and what gets recorded. It is deliberately source-agnostic — Telegram and Discord enter at the same boundary and everything downstream is identical.
If you want the concrete setup sequence for one route — installing the app, signing in, mapping symbols, watching the first demo order land — that walkthrough lives on its own page and is not repeated here.
Where each stage runs
Read, parse, guard, queue, deliver, and the broker result all run on the Windows PC that hosts the desktop agent and your MetaTrader terminals. The agent's Rust core owns the source sessions, the parser, the routing gate, the durable queue, and the loopback bridge; the cloud is never in the trade-execution path, so a cloud outage does not stop routing: the agent keeps trading on its last verified licence policy, which is re-issued about every 15 minutes and stays valid for up to 60.
The cloud's scope is licensing and pairing plus the dashboard mirror: parsed signals, trades, account snapshots, journal notes, and symbol mappings sync up so you can review them in a browser. Message content never leaves your PC — the dashboard holds metadata, never message text.
The pipeline: from message to broker result
Six stages in order. A signal that cannot pass one stage never reaches the next, and every stop has a recorded reason.
01Read the chats you selected
The app holds your own Telegram session locally via TDLib (QR code or phone number) and your Discord connection (bot token recommended; own-account token only as a fallback that Discord's terms prohibit, opt-in, with account-termination risk). Only new text messages from the chats and channels you picked enter the pipeline — history, images, and captions are never imported. Each source runs independently, so a source that fails to start is recorded as a diagnostic while the other keeps delivering. Message text is stored only in the local database, capped at 8 KiB per message and purged after seven days.
02Parse the message into an order
A versioned deterministic parser turns each new message into a structured order: side, symbol, entry, stop-loss, and take-profit. Entry messages become open or pending-order intents; replies to earlier messages resolve into management intents (modify, break-even, partial or full close, cancel). A stop on the wrong side of the market is rejected, anything ambiguous is held for review instead of guessed at, duplicates are deduplicated, and stale signals are refused by a freshness window.
03Pass the routing gate
The gate starts closed and opens only on your explicit typed confirmation. Each signal is then rechecked: an active licence allowing new entries, a fresh connected terminal session, a fresh signal, an explicit mapping from the provider's symbol to your broker's symbol, and a fixed volume inside the broker's min/max/step limits. The moment you arm the gate is recorded, and signals that arrived before it stay review-only forever — execution is never retroactive. Per-channel trade-management consent stays off unless you enable it.
04Admit the command to the durable queue
A signal that passes the gate is atomically claimed and linked to exactly one command — one normalized signal can never create two. Admission is durable in local storage through RECEIVED, VALIDATING, and then QUEUED_FOR_EA, REJECTED, or EXPIRED, so a restart loses nothing and every refusal carries a readable reason. Each command also passes the destination's declared capability check, and routing is tracked per destination: a signal that reached two of three terminals is reported as partially routed, never as routed.
05Deliver to MetaTrader over loopback
The app installs its packaged Expert Advisor (MT5 `.ex5`, MT4 `.ex4`) into your terminal and verifies it. The EA pulls queued commands over the loopback address on your own computer, falling back to a sandboxed file channel under the same protocol and authentication if the loopback URL was never allow-listed. Sessions are short-lived bearer tokens bound to the terminal, account login, and broker; delivery is acknowledged, redelivery keeps the same command ID, and a changed account pauses the EA rather than trading the wrong one. The MT4 connector ships with the app but live verification on a real MT4 terminal is still pending — MT5 is the verified path today.
06Record the broker's result
The EA submits the order and reports what the broker actually did: filled, partially filled, cancelled, failed, or unknown-needing-reconciliation, always with the broker's own result code attached. Nothing is retried automatically — uncertain outcomes are held for review with their error category. Every transition from admission to broker response is persisted as an audit event, which is why a missing order always has a location and a reason. Results, account snapshots, and journal notes then mirror to the cloud for the dashboard; message content never leaves your PC, and no latency figures are published anywhere on this site.
shipped, not promised
What the current build does today
Every item below exists in the desktop app now. Roadmap items are not marketed here.
Local Telegram and Discord sessions
your own account · bot token recommended
Deterministic parsing with review inbox
side, entry, SL, TP · dedupe
Fail-closed gate, never retroactive
typed confirmation to arm
Durable per-destination queue
RECEIVED → broker retcode
Loopback EA delivery, MT5 verified
MT4 connector shipped · verification pending
Full audit trail plus dashboard mirror
metadata syncs · message text never leaves
If an order does not appear, read the trail in order
Start at the inbox: a signal sitting review-only arrived before the gate, failed to parse, or is a duplicate — each with its reason attached. Next the queue: REJECTED or EXPIRED commands say whether the mapping, the licence, the terminal session, or the freshness window stopped them. Then delivery: an unacknowledged command means the terminal is offline or the EA session lapsed. Finally the broker result: a FAILED outcome carries the broker's own code, which is a broker verdict, not a copier malfunction.
The usual causes are configuration, not malfunction: an unmapped provider symbol, a stop inside the broker's minimum distance, a terminal that lost its session, or a lapsed licence blocking new entries while leaving risk-reducing actions and dashboard visibility intact. Fix the cause and let the next new signal prove it — old signals never execute retroactively.
What the cloud does and does not do
The cloud handles device pairing and licensing — an Ed25519 device key protected by the OS, a one-time pairing token, heartbeats carrying a signed policy the agent verifies before storing — and it receives the dashboard mirror: parsed signal metadata, trades and execution results, account snapshots, journal notes, and symbol mappings, drained in batches of 50. Trade commands never travel to the cloud, source sessions and message text never leave the device, and your broker password is never read at all.
That split is why the pipeline above is described as local: the execution path in stages one through six touches only your PC and your terminal. The dashboard shows you what happened; it never takes part in making it happen.
faq
Questions worth asking
Will it place trades without my permission?
No. Routing is disabled by default, requires an active pairing and an explicit typed confirmation to enable, and only sends orders for signals that arrive after the gate is on. Anything received earlier stays review-only and is never executed retroactively.
Why would a signal be review-only instead of executed?
Because it arrived before routing was enabled. That is deliberate: the gate is fail-closed and non-retroactive. Send a new signal after enabling routing to see an order move through the pipeline.
Does my Telegram or Discord data go to your servers?
Your source sessions live on your Windows machine. Signal messages (Telegram chats, Discord channels) are read locally, and the trade path goes to MetaTrader over a loopback connection on that same machine. No one else's server is on the execution path, and source message bodies are never uploaded. Your account dashboard does mirror structured data from the agent: signals, trades, account snapshots, journal notes, and symbol mappings, so you can review them in the browser. It holds metadata, never message text.
How fast is execution?
We do not publish latency numbers yet. The desktop agent has a latency benchmark in progress, and this site will only state figures once they come from a measured run. Claims you see here are about what the software does, not how fast it claims to do it.
What happens if my provider edits or repeats a signal?
Messages are deduplicated so the same signal is not handled twice, and only new text messages are read. Images, captions, and history before the chat was selected are not imported. Edited messages are handled deterministically rather than treated as fresh orders.
What signal formats can it read, and what happens with a message it can't parse?
It reads new text messages and classifies each one with parser version 2 as an entry, a management instruction, or chatter. By default, an entry that names no stop is refused (a routing setting you can change) — and results-style recaps fall to ignored rather than parsing as fresh orders. Images, captions, and chat history are never imported. A message that does not fully match the expected shape is held for review in the inbox instead of being guessed at: nothing partial is ever ordered. Management instructions such as close or move SL act only on channels where you have turned trade management on, which is off by default.
Telegram to MT5: the full pipeline
the Telegram setup walkthrough
Features and safety model
every shipped capability
MT5 signal copier
the MetaTrader 5 side
Security model
why the trade path stays local
Try it on your own machine
Free 7-day trial, no payment method, full local signal pipeline on your own machine.