NANOBOT FEATURES
Nanobot features: plan, test and monitor your trading in one place
Turn your strategy into a repeatable setup. Configure bot rules, define entry and exit conditions, try them out before going live, and follow every deal from a connected workspace so you can see both the plan and the result.
A bot acts on the conditions you set. It does not guarantee profit, and you still need to plan your capital and monitor your risk.
Be clear on when to enter, add and exit
Match your bot conditions to your capital plan, then study the outcome with the simulation and testing tools your account supports.
See the strategy toolsSTAY IN CONTROLTrack bot status, deals and account overview
Use Terminal Trading and your trade history to review how the bot is running, and understand the difference between stopping a bot and closing a deal.
See the workspace and monitoring10 features that help you manage trading systematically
#PLANCONTROLTESTMONITORCONNECT
- Strategy and DCA setupDefine the first order, follow-up orders and the rules of the plan.
- Take Profit and Stop LossSet your exit conditions for a deal in advance.
- Trailing TP / SLUse price-tracking conditions to manage the exit point.
- Demo accountLearn how the platform works using simulated funds.
- BacktestingStudy how a strategy behaves against historical data.
- Terminal TradingRun your bots and trade manually in the same workspace.
- Bot, Deal and HistoryCheck live status and review what has already happened.
- PortfolioSee an overview of your assets and connected accounts.
- Connect an exchange via APILet the bot work with a supported trading account.
- TradingView and Signal BotFeed external signals into your bot conditions.
Features, bot quota, API connections and testing access depend on your package, bot type and the services enabled on your account. Please check the current details before you start.
PLAN · BUILD THE SETUP
Bring your strategy and DCA settings into one plan
#Start by deciding the conditions under which your bot opens a deal, adds to it and closes it. Nanobot gives you a strategy screen where these pieces sit together, so you can review the plan before it runs instead of making a fresh decision every time the price moves.
Manage the first order and follow-up orders
Define the first order (Open Order) and the follow-up orders (Step Order) that make up your DCA plan, and check the number of orders and total capital required. The documentation may also use the term Base Order for the first order.
Percent
Set the price distance as a percentage of the reference point used in that setting.
Condition
Wait for the condition you defined before the next order is considered.
Filter
Add filters that define the context in which the bot is allowed to act.
Order of condition checks
Conditions within a group use OR, while filters use AND. Passing a condition still has to be combined with available capital and the bot's other limits. Averaging down can consume more capital and can still end in a loss.
CONTROL · DEFINE THE EXIT
Plan the exit with Take Profit, Stop Loss and Trailing
#Setting the entry is only part of a plan. Exit tools let you define how the system responds when price reaches your target or moves against you, and they should be considered together with deal size and total capital.
Take Profit and Stop Loss
Take Profit sets the condition for closing a deal once it reaches your target, while Stop Loss sets the condition for exiting once losses reach the level you planned for. For percentage-based Take Profit in DCA, check which reference the percentage uses — the deal's average price — and include costs when you assess the net result.
- Decide the rules for leaving a deal before you switch the bot on.
- Revisit the exit point whenever you change order size or the averaging conditions.
- Check the real order status after an exit condition is triggered.
Trailing Take Profit and Trailing Stop Loss
Trailing conditions follow price movement so the exit point can adjust within the values you set. Before using them, make sure you understand where trailing starts, how far it trails, and when orders are sent for the bot type you have chosen.
TP, SL and Trailing do not guarantee the execution price or a maximum loss. When price moves quickly, liquidity is thin, or the connection has problems, the real result can differ from the values you set.
TEST · LEARN BEFORE GOING LIVE
Practise on Demo and review your strategy with backtesting
#Learn the settings screen and study how a strategy behaves before committing real money. Each tool answers a different question, so choose the one that matches what you actually want to check.
Demo: practise with simulated funds
A Demo account lets you configure a bot, watch deals open, and get familiar with the tools your account supports — all using simulated funds. It suits practising the workflow and confirming that you understand how each setting behaves.
- Explore the workspace and practise reading bot and deal status.
- Change a setting and observe how the conditions respond.
- Check which bot types and Demo access are available on your current account.
Backtesting: study a strategy against historical data
Run backtests on supported strategies to study how your rules performed over the data range you selected. It helps you compare settings and see the limits before you commit. Backtesting access depends on your package and bot type.
- Compare settings using the same data range and the same cost assumptions.
- Look at drawdown along the way and the capital required, not just the total result.
- Test more than the one market period that happens to look good.
| Tool | Question it helps answer | What to keep in mind |
|---|---|---|
| Demo | How do I use and configure the platform? | It is a simulated-funds environment; results can differ from the live market. |
| Backtesting | How does the strategy behave on historical data? | It depends on the data, the assumptions and the supported functions. |
| Simulator in the settings screen | What does my order structure and plan look like overall? | Simulating settings should not be treated as a full backtest across every dimension. |
Demo, Simulator and Backtesting results do not guarantee future results, and they are not a substitute for checking real costs or execution limits.
MONITOR · SEE WHAT IS RUNNING
Control your bots and follow your trading from one workspace
#Connect the picture of your strategy to what is actually happening. Use the bot control screen, the deal list and your account data together to decide what to monitor, verify or adjust next.
Terminal Trading: run bots and trade manually in one place
Terminal Trading brings bot activity and manual trading into the same workspace, so you can move from following the plan to checking your trades without switching context. You still need to verify the account, the trading pair and the order before you act.
- Use the price chart, order book and trade list while you work.
- Use Scanner to filter pairs by market data such as volume and the supported Top / Favorite lists.
- Pick Manual Mode or Bot Mode to match what you intend to do, and review the order before confirming.
If you trade manually on the same account as your bot, account for the change in assets and balance, including the effect on deals that are still open.
Scanner
Running deal
Mock data used to illustrate the screen, not real trading results.
Bot, Deal and History: check status and review activity
A Bot is what runs your strategy; a Deal is one trading cycle. Use bot and deal status to see what is happening now, then review the history to understand which orders have already been executed.
| Command | What it does |
|---|---|
| Stop Bot | Stops new deals from opening. It does not sell the assets held in open deals. |
| Close Deal | Sends a sell order to close the selected deal. You still need to check the execution result. |
| Cancel Deal | Used when a deal is stuck or faulty. Understand the effect on your assets and outstanding orders before using it. |
Portfolio: an overview of your connected accounts
Portfolio shows totals and a per-account breakdown for your connected accounts, including available balance, assets, asset allocation and profit and loss within what the system supports. It helps you see which capital and assets relate to the plan currently running. The data depends on the exchange and on how frequently the system updates.
- Read the overview alongside open deals and your trade list.
- Reconcile balances with the exchange when figures look wrong or updates lag.
- Separate changes in asset value from the profit and loss actually realised by trading.
CONNECT · WIRE IT TOGETHER
Connect the exchange and the signals your plan relies on
#Account connections and external signals are part of the strategy. Before enabling them, check that the permissions, market type and services match what your account supports.
Connect an exchange via API
Nanobot connects to your trading account through an API to read data and act within the permissions you grant. Before you start, choose a supported exchange, check the trading pairs, and follow that service's connection steps. This page describes usage in the Spot market.
- Enable only the permissions the guide calls for, such as Read and Trade, and leave Withdraw off.
- Check the connection status and your balance before letting the bot start.
- Keep your API key and secret private — never share them in chat, screenshots or public URLs.
TradingView and Signal Bot
Connect TradingView alerts to your bot through the channels Nanobot supports, so external signals can feed the orders your strategy sends. This suits traders who already have their own signal conditions and want to wire them into automated execution.
- Check the message format, destination account and trading pair against the connection guide.
- Test how a signal reaches the system and how it is used before going live.
- Check the package limits of both Nanobot and your signal provider.
How a signal travels
Receiving a signal is not confirmation that an order succeeded. You still need to check bot status, the API, available capital and the result from the exchange. External connections and services can be delayed or fail.
START · MATCH THE TOOLS TO THE PLAN
Start with what you need, then add complexity
#You do not have to switch on every feature at once. Start from a plan you can explain, and use the tools to confirm that the system behaves the way your conditions describe.
- Learn on Demo
Explore the bot settings screen and see how deals open, adjust and close within the access your account supports.
- Plan capital and exits
Set the first order, the number of follow-up orders, the total capital and the TP/SL conditions so they work together.
- Test the plan
Use the simulation or backtesting tools available to you, then check the cost assumptions and the limits of those results.
- Connect and monitor
Verify the API and destination account before going live, then keep an eye on Bot, Deal and Portfolio regularly.
Frequently asked questions about Nanobot features
#Do I need to write code to configure a Nanobot bot?
You can configure a bot through the Nanobot settings screen using the options and conditions the system supports, though you still need to understand your plan and what each setting does. Signals or specialised connections may require you to prepare data as described in that service's documentation.
What is the difference between Percent and Condition DCA?
Percent uses a price distance expressed as a percentage of the reference point in that setting, while Condition waits for the condition you selected before the next order is considered. Either way, filters, available capital and the bot's limits still apply.
Can Demo replace backtesting, or the other way round?
They check different things. Demo lets you practise in a simulated-funds environment, while backtesting studies a strategy against historical data. Both can differ from live trading, and access depends on your bot type and package.
If I set a Stop Loss, is my loss capped at that value?
No, that cannot be guaranteed. Stop Loss is a condition that sends an exit order; the executed price can differ from your target when price moves quickly, liquidity is thin, or the connection has problems.
If I stop a bot, are open deals sold immediately?
No. Stop Bot stops new deals from opening; it is not an order to sell open deals. To close a deal, learn how Close Deal works and check the order result after you use it.
Does the API connection need withdrawal permission?
You should not enable Withdraw on an API key used with a bot. Enable only the permissions the guide calls for, such as Read and Trade, and keep the key and secret private. Limiting permissions does not remove trading risk.
Will every order succeed when I use a TradingView alert?
That is not guaranteed. The signal has to reach the system in the correct format, the bot and API have to be ready, capital has to be sufficient, and the order has to satisfy the exchange's requirements — so test it and check the real execution result.
Do all packages include the same features?
Some entitlements differ, such as bot quota, API connections, Signal Bot and backtesting. Check the package details and the access shown on your current account, along with any related service fees, before you start.
Start from a plan you understand, then pick the tools that genuinely help
Explore Nanobot on Demo, learn how to configure a bot and follow your deals, then apply the tools to your own plan, capital and risk.
Sign up and explore DemoRisk disclosure
Digital assets are volatile and you can lose your capital. Nanobot is a tool that acts on the conditions you set; it does not guarantee returns or execution prices. Simulated and backtested results are not a promise of future performance.
Sources
- Core features guide
- Creating a bot
- Risk management guide
- Supported markets and services
- Terminal Trading and Scanner
- Portfolio guide
- Connecting an exchange
Nanobot feature overview and getting-started guidance