Configuring Deriv Autopilot Settings for Binary Bots

Configuring your autopilot settings correctly requires defining eight core fields on the configuration panel to control trade entry, contract duration, and martingale progression. Because AutoPilot executes directly through Deriv's server-side automation system, your choices stay active on Deriv's servers even after you close your browser tab or disconnect your network. Getting these settings right is the difference between a controlled trading session and a rapid account wipeout.

Unlike standard client-side scripts, this bot places CALL and PUT contracts using server-side execution. Once you press start, the server handles trade placement, contract expiration, and stake multiplier calculations automatically. Understanding how each parameter changes the bot's behavior keeps you in control of your exposure.

How AutoPilot Settings Control Server-Side Execution

When you adjust your configuration parameters, you write rules directly into the server's execution queue. You don't need to keep a laptop lid open or worry about losing your internet connection mid-trade. The automation processes each contract tick by tick, applies your chosen martingale multiplier on losses, and resets to your base trade size after a win.

Because execution happens remotely, your pre-set limits carry total authority over your account. If you launch a session with poor parameters and walk away, the system will keep placing contracts until it hits your boundaries. That is why tweaking your autopilot settings thoughtfully on a virtual account must always come before trading live funds.

Locating the On-Screen Parameters Panel

When you launch the platform at AutoPilot, the configuration card sits right at the center of the workspace. You don't need to write code or drag visual blocks. Everything happens inside eight standard input fields.

Here are the exact control fields on your screen:

• Market: Selects which volatility index to trade.
• Direction: Sets the contract type to CALL (Rise) or PUT (Fall).
• Base Stake: Defines the initial dollar amount placed on the first trade.
• Duration (sec / min): Sets the contract lifetime in seconds or minutes.
• Growth Rate — 1% to 5%: Adjusts the dynamic target calculation per successful trade sequence.
• Risk Level — Safe / Medium / Aggressive: Controls how aggressively the martingale multiplier scales up your stake after a loss.
• Take Profit: Sets the maximum target profit in dollars where the bot automatically stops trading.
• Stop Loss: Sets the absolute dollar cap on total losses before the server terminates the automation.

Comparing Safety and Progression Profiles

Choosing between Safe, Medium, and Aggressive changes the underlying stake multiplier when recovering from a losing trade. Higher risk settings attempt to recover accumulated losses faster, but they force your required stake up exponentially on consecutive drawdowns.

Here is how the three risk options handle trade runs:

Selecting your Risk Level along with your Duration (sec / min) changes how fast trades trigger and how quickly loss runs stack up. If you set a short 5-second duration on an Aggressive profile, three bad ticks can happen in fifteen seconds flat. That's why choosing the right combination of parameter values on binary bots matters so much.

Step-by-Step Configuration Guide

Follow these steps to configure your session cleanly before pushing real capital to the server.

Step 1: Select your target index under Market and set Direction

Pick a volatility index from the Market dropdown menu, such as Volatility 75 Index. Choose your trade bias under Direction by picking either CALL or PUT depending on whether you want to trade a rise or fall contract.

Step 2: Input your Base Stake and select Duration (sec / min)

Enter your initial trade size in the Base Stake box. If you have a $100 balance, start with a small base stake like $0.35 or $1. Choose your contract timeframe under Duration (sec / min) by entering the number and selecting either seconds or minutes from the unit selector.

Step 3: Dial in your Growth Rate — 1% to 5% and select Risk Level — Safe / Medium / Aggressive

Set your Growth Rate — 1% to 5% selector to adjust trade progression pacing. Next, select your Risk Level — Safe / Medium / Aggressive setting to control multiplier scaling. If you're testing new strategies for deriv bots, select Safe first.

Step 4: Define strict Stop Loss and Take Profit limits

Input your maximum total session loss into the Stop Loss field and your target profit into the Take Profit field. The server checks these numbers after every single settled contract. Set your Stop Loss at an amount you can afford to lose entirely on a bad run.

The Cold Math of Martingale Stake Progression

Let me show you what happens when a losing streak hits during execution.

Assume you open a session with a $100 starting balance on Volatility 75 Index using a $2 Base Stake with Medium risk settings. The bot trades CALL contracts.

Here is how the math plays out across a four-trade losing run:

1. Trade 1: Stake $2. Trade loses. Running loss: $2. Account balance remaining: $98.
2. Trade 2: Stake scales to $4. Trade loses. Running loss: $6. Account balance remaining: $94.
3. Trade 3: Stake scales to $8. Trade loses. Running loss: $14. Account balance remaining: $86.
4. Trade 4: Stake scales to $16. Trade loses. Running loss: $30. Account balance remaining: $70.
5. Trade 5: Next required stake jumps to $32.

After four fast losing ticks, you've lost $30 out of your $100 balance. To place the fifth trade, the bot needs to stake $32. If that trade loses as well, your cumulative loss reaches $62—over 60% of your initial account wiped out in five consecutive trades. A sixth loss requires a $64 stake, but with only $38 left in your balance, the account can no longer place the next trade and hits total drawdown failure.

This math proves why setting a strict Stop Loss is vital. Synthetic indices generate independent random draws on every tick. Past trade results don't change future probability, and losing runs happen regularly. Because server-side execution continues when your browser is closed, your pre-set Stop Loss is your only defense against an empty balance.

Always test your autopilot settings on a virtual demo balance first before deploying real funds on live deriv bots. You can explore other automated tools across our full free bot library once you've mastered server-side risk controls on binary bots.

Try configuring your strategy parameters directly on AutoPilot using a demo balance first. If you don't have an active trading account yet, create a free Deriv account to begin testing. Trading involves risk. Past performance does not guarantee future results.

Related: Autopilot for Beginners: Deriv Rise/Fall Bot Setup

Related: How to Use Autopilot for Server-Side Deriv Automation

Related: Autopilot Demo Account Setup: Test Deriv Bots Risk-Free

Related: Autopilot vs Manual Trading: Deriv Bots Compared