The automated bot, BRS and signal strategies you already run in the DT Nexus
trading app — executing server-side, 24/7. Close the laptop. Lose the Wi-Fi.
They keep trading.
A browser tab is a terrible place to keep money working.
Every browser-run bot dies the same handful of deaths: the laptop sleeps, the
phone locks, the tab gets throttled in the background, the Wi-Fi blips, or the
socket drops and the engine stops mid-progression — leaving an open contract
nobody is watching.
DT Nexus Cloud moves the whole engine onto a server that does not sleep, does
not throttle, and treats a disconnect as something to recover from rather than
a reason to quit.
In the browser
Laptop sleeps → bot stops
Tab backgrounded → ticks throttled
Socket drops → engine halts
Open contract → unwatched
Progression state → lives in localStorage
In the cloud
Runs on a server, always awake
Full-rate tick stream, always
Re-authorizes and resumes the loop
Contracts re-subscribed on reconnect
State persisted, resumed after deploys
How it works
Four steps, then you close the laptop.
No new account, no new credentials to remember, no software to install.
01
Sign in with DT Nexus
The same email and password as the trading app. Logging out on any device revokes cloud access too — sessions are checked live, not just signed.
02
Link your Deriv account
Paste one API token. A pat_ access token links every account you own — demo and real — in a single paste. Tokens are encrypted before they touch the database.
03
Configure a bot
Market, contract, stake, progression, take-profit, stop-loss — or hand the whole decision to a signal ladder. The same settings you already know.
04
Press start, walk away
The engine authorizes its own socket, streams ticks, places trades and settles them. Watch live from anywhere, or don't watch at all.
Built for unattended trading
The parts that matter when nobody is watching.
Recovery, not surrender
A dropped socket triggers exponential backoff, a fresh authorization, and re-subscription to every in-flight contract — then the loop resumes where it left off. Bots that were running when the service restarts come back up on their own.
Three execution speeds
Normal settles on is_sold, Fast on the exit tick, and Ultra reconciles locally off the tick stream — with a contract poller that verifies and repairs every local settlement.
Martingale & stake lists
Multiplier progressions with a start-after threshold, or an explicit stake ladder. Stop at the cap or restart the progression — and always stop at take-profit or stop-loss.
BRS windowed targets
Hit a profit target inside a time window, then pause until the next one opens. Ladders carry over across rollovers, and a stop-loss arms a six-hour cool-down.
Signal-driven entries
Resolve each trade from the Digit Edge feed or the local DAT analyser — market, digit and contract chosen at placement time, gated behind entry conditions you define.
Every fill, recorded
The browser app never persisted a single contract. Here, every buy and settlement is written down — stake, payout, profit, entry and exit spot — so a session can be reviewed long after it ends, per bot and per run.
Strategies
Two engines. Everything you already run.
Automated bot
Set the trade, set the risk, let it cycle.
Pick a market and contract — Even/Odd, Over/Under, Matches/Differs, Rise/Fall, or a paired mode that alternates or randomises sides. Then define how it escalates on a loss and where it must stop.
A windowed engine: trade until the window's profit target is reached, bank it, and wait for the next window to open. Scout with Differs then step to Over/Under, or drive it from a custom signal ladder.
Broker tokens are encrypted with AES-256-GCM before they reach the database and
are decrypted only in memory, at the moment a bot opens its socket. They are
never sent back to a browser — not even to you.
Live session checks. A signature alone isn't enough — every request confirms the session still exists, so a logout anywhere cuts cloud access everywhere.
One socket per bot. Each bot authorizes its own connection. Nothing is shared, pooled, or proxied between users.
Least privilege. Link a demo account and nothing else can be touched. Unlink at any time and the stored token is destroyed.
You keep the keys. Revoke the token at Deriv and the link dies instantly, with no action needed here.
Deriv API tokena1-••••••••••••••••••••
AES-256-GCM
Stored9f3c a20e 77bd 41ee c018 ‧‧‧
Never returned to a client
FAQ
Questions worth asking.
Do I need a subscription?
No. Every DT Nexus account can run cloud bots. A subscription only raises how many bots you can run at the same time.
Is this a different bot from the one in the trading app?
No — it's the same engine, ported to run headless. The progression maths, settlement handling, execution speeds and contract rules are carried over deliberately unchanged, so a strategy behaves the same in both places.
What happens if the service restarts while my bot is running?
It comes back. Bots record what they were asked to do, and on boot the engine restarts anything that was running — with its progression state and session profit intact, rather than starting over.
Can I test with a demo account first?
Yes, and you should. A pat_ token links your demo and real accounts together, and you choose which one each bot trades on. Point it at the demo account until you trust the configuration.
Can I still use the trading app at the same time?
Yes. The cloud runs its own connection and won't interfere with a browser session. Just remember both are trading the same real balance if you point them at the same account.
What stops a bot from running away?
Take-profit and stop-loss are enforced by the engine itself, and hitting either stops the bot rather than pausing it. Progression caps stop it too, and BRS adds a six-hour lock after a stop-loss. You can also stop anything instantly from the dashboard.
Put a bot on a server that never sleeps.
Sign in with the DT Nexus account you already have, link a demo account, and watch it trade without you.