1. Sign in to this website once. Open Broker connections.
2. On the Windows execution host, install and open Exness MT5. Sign in to your Demo trading account and enable Algo Trading.
3. Choose Demo here. Enter the MT5 account number, trading password and exact Exness server from Personal Area. The website password is different.
4. Click Connect Exness. Verify Demo, account ending, server, balance and equity. A connected broker does not mean Kronos is running.

Use HTTPS on a deployed website before entering credentials. Never send passwords in chat. Real accounts are connection/view only in this workflow.

1. Check Gold / XAUUSD, Bitcoin / BTCUSD and/or Ethereum / ETHUSD. Only checked assets can open new setups.
2. Set the total lot explicitly for each enabled asset. The timeframe is fixed at 5M. At most two different assets may hold positions or pending setups; additional assets wait.
3. Check broker minimum lot and step. 0.02 splits into 0.01 / 0.005 / 0.005. If the broker requires 0.01 steps, this exact split is rejected. The app will not increase your lot. Choose a supported size yourself.
4. Accept demo-order execution and click Start Kronos demo · 5M. Check Running and a fresh model heartbeat, plus each asset's message. A signal is not guaranteed on every candle.

One asset has one active 5M setup. New analysis cannot replace it while its position or pending order remains active. Partial booking does not unlock it. Another enabled asset may trade independently within the two-asset limit.

• TP1: book 50% of original volume; after broker confirmation, move remaining SL to actual entry before costs.
• TP2: book another 25% of original volume; move SL to TP1.
• TP3: final 25% exits at the broker target.

Gaps, model processing and execution latency can skip intermediate stages. An uncertain partial response is not resent blindly. Existing older setups keep their saved exit policy.

Use Chart / orders view to select an asset. Its synchronized chart, signal ID, order ticket, booked percentage, remaining volume and red/green P&L appear below. The report refreshes every seven seconds while visible. Net includes reported commissions, swap and fees; break-even before costs may still be a net loss.

Order numbering restarts at 1 at 00:00 and 12:00 IST; old history stays available. Filled and unfilled counts are separate. UNVERIFIED means broker evidence is missing, not a win.

Daily limits use that day's initial account equity, including floating P&L. At +30% profit or −10% loss, new setups pause and owned pending orders are cancelled. For $250, the triggers are +$75 / −$25. Filled trades remain under SL/TP and trailing/scale-out management as configured. Limits reset at 00:00 IST and survive Stop/Start when storage is retained. They do not guarantee booked profit or a maximum realized loss.

Stop Kronos model prevents new submissions and stops trailing/partial management. Existing broker-side SL/TP stays active; Stop does not close positions. Review them in MT5.

• Not connected: check the exact Demo login/server, trading password, MT5 host and network.
• Connected but stopped: review settings, consent and Start. Check the model heartbeat; do not rely only on the connection badge.
• Unsupported split: explicitly choose compatible total lots or leave that asset disabled.
• Stale feed or closed market: wait for fresh broker candles; do not substitute another provider's levels.
• Uncertain order/partial close: inspect MT5; do not repeatedly Start to force another order.
• After backend restart: reconnect Demo and explicitly Start. Automatic unattended reconnect is not implemented.

• Keep Windows MT5, Algo Trading and the execution backend running on the cloud host, with persistent private runtime storage.
• Run one execution worker for this account. Do not run the same account's bot locally and in AWS together.
• Confirm Running, fresh checks and correct Demo account from the deployed portal. Observe a complete demo entry/exit cycle before leaving it unattended.
• Closing your browser does not stop the server loop. Shutting down the execution host or restarting its backend interrupts management and requires reconnect/Start.
• Keep the runtime database across deployments so daily locks and order/partial-close intents survive.

Cloud deployment and actual broker fills must be checked on that host; a GitHub push alone does not establish 24-hour operation.