Binary Bot vs DBot and where Bot Forge fits

If you are looking at Binary Bot vs DBot, the short answer is that they are two generations of the same idea: a block based builder where you drag pieces together to describe a trade, save the result as a bot file, and let it run on your Deriv account. Binary Bot is the older one. DBot came later and sits inside the Deriv platform. Bot Forge is the third thing in that family, and it reads bot files from both of the older builders, so a strategy you already have does not have to be rebuilt from scratch.

Trading loses money for many people, and a bot does not change that. It only changes who presses the button.

Binary Bot and DBot are the same idea at different ages

Both builders work the same way on screen. You pick a market, pick a contract type, set a stake and a duration, and then describe what happens after a win and after a loss. The blocks snap together like a flowchart. Nothing is typed in code, and nothing runs until you press start.

Binary Bot is the earlier builder and carries the name from before the platform was called Deriv. DBot is the one you reach from inside the Deriv platform itself. The vocabulary is close enough that a trader who learned one can read the other without much trouble. The blocks have the same jobs: a trade definition block, a purchase block, a block that decides whether to trade again.

The practical difference most traders care about is the file. Both save your strategy as an XML file on your own machine. That file is the strategy. The builder is just the place you edited it.

The bot file is what actually moves between them

An XML bot file is a text file describing the blocks you arranged and the values you put in them. It holds the market, the contract type, the stake, the duration and the rules you wrote around them. It does not hold your account, your balance or your money. That is why a file can be passed from one builder to another at all.

So when people ask which builder their bot belongs to, the honest answer is that it mostly belongs to the file. Load it somewhere that understands the format and the same strategy appears on screen. If you have never opened one, our guide on Binary Bot and DBot walks through where files live and how to bring them across.

Bot Forge reads files from the older builders

Bot Forge is BancaBot's block based builder, and it reads bot files from the older builders. You load an XML you already have, the blocks appear, and you can change them or run them. It also carries a library of free bots you can load without building anything first.

That matters if you have collected bot files over the years, or if someone sent you one. You do not need to work out which builder it came from before you can look inside it. Open it and read the blocks. The blocks tell you what the bot does, which market it is pointed at and what it does after a loss, which is the part worth reading twice.

What stays the same no matter which builder you use

The builder changes. The things that decide whether a bot is sane do not.

• The market. A bot written for a volatility index behaves differently when you point it at something else, and some bots are written for one index only.
• The stake rule. Read what the bot does to the stake after a losing trade. A bot that increases it can lose the balance faster than you expect.
• The stop loss and the target. Decide both before you start, not while the bot is running.
• The account. A demo account is the sensible place to run anything new.

If you want the longer version of that checklist, we wrote it out in what is a Deriv bot.

How the three builders line up

Signing in is the same account either way

Whichever builder you use, a bot cannot trade until it is attached to an account. With BancaBot you sign in with Deriv through Deriv's own OAuth screen. The permission asked for is trading only, which lets BancaBot read the account balance and place trades. It cannot withdraw, it cannot move money, and it never sees your password. Real and demo accounts both work.

The markets are Deriv's own: the synthetic indices, including Volatility 10, 25, 50, 75 and 100 and their one second versions, plus forex pairs and gold. Contract types are Deriv's too, such as rise and fall, higher and lower, and the digit contracts. A bot file written for one of those contract types only makes sense on that contract type.

Which one to open first

If you have no files yet, start with a library bot rather than a blank canvas, because reading a working bot teaches the blocks faster than arranging them does. If you do have files, the question of Binary Bot vs DBot stops being interesting the moment you can open either file in one place. The free bot library and the premium plans are set out on the site, and the free library costs nothing to load.

Open an old bot file or a free one in Bot Forge, run it on a demo account first, and read what the blocks do before you change anything.