tradectl

Appearance

Going live ​

This guide moves your bot from paper trading to real money on Binance. You can run the bot on your own computer or on a small server that you rent. Read the whole guide once before you start.

Live trading can lose money

You choose the strategy and its settings, and the bot runs on your machine with your Binance account. We give you the software. We do not trade for you and we never hold your money.

Short on time? The go-live checklist lists every step on one page.

Before you start ​

You need:

  • The tradectl Lab on your computer, with a bot that already trades on paper. If you have no bot yet, see Getting started.
  • A Binance account with Futures opened.
  • Money in the right Binance Futures wallet. Look at the strategy's Market setting:
    • USDT perpetuals (for example ETHUSDT): USDT in your USDⓈ-M Futures wallet.
    • Coin-margined perpetuals (for example XRPUSD_PERP): the coin itself (XRP for XRPUSD_PERP) in your COIN-M Futures wallet.
  • A tradectl account at app.tradectl.com. You need it for a paid plan and for the server path. Live trading on the Free plan works without one.

What each plan lets you do ​

PlanPriceLive trading
Free$0BTC, ETH, XRP, SOL and BNB perpetuals only. Each order is cut to $20, or to the Binance minimum if that is larger.
Starter$20 a month1 live bot with no limits.
Pro$54 a month3 live bots with no limits. Each extra bot is $18 a month.

Paper trading has no limits on any plan. On Free you can already trade live with small orders, so you see real fills before you pay.

A bot that does not get a paid place (for example, a second live bot on Starter) still runs. It runs with the Free limits, and the Lab tells you why.

Which path to choose ​

On your PCOn a server
Costnothing extraabout $10 to $12 a month for the server
Setupa few clicks in the Labone line, pasted once into the server's console
When the PC sleeps, restarts or loses internetthe bot stops tradingnot affected
Good forthe Free plan, small live amounts, trying livereal money, a bot that runs day and night

A home PC sleeps, installs updates and restarts. Your internet can go down. Each time, the bot stops. Read If the computer or server goes down to see what that means for your open positions. If you trade real money, use a server, and add a watchdog on a second machine.

Two rules ​

  1. Do not trade by hand on the bot's coins with the same Binance account. Binance adds your hand trade and the bot's trade on the same coin into one position. The bot cannot tell them apart, so it can close or resize your trade, and your trade can break the bot's take-profit and stop-loss. For hand trading, use a Binance sub-account with its own key.
  2. Stop the bot before you move it to another computer or server. Stop closes its positions and cancels its orders. Then set up the new one. Never run the same bot in two places at once, and never just switch off the old machine: a bot that is not stopped leaves its orders and positions on Binance, and the new bot does not know them.

Path A: on your PC ​

A1. Make a Binance API key ​

Follow Your Binance API key. For the IP address, use your home IP (Which IP address to enter explains how to find it, and what to do when it changes).

A2. Open the bot's settings ​

In the left list of the Lab, right-click your bot and choose Settings. You can also press the Settings button at the top of the bot's chart. The Strategy editor window opens. It has three tabs at the top: Strategies, Exchange and Watchdog.

A3. Add your keys in the Exchange tab ​

  1. Click the Exchange tab.
  2. Paste the API key and the API secret from Binance.
  3. Press Save keys.

Saving keys does not restart the bot. After a moment the Lab tests the saved keys by itself with Binance and shows a checklist. Every line should be green before you go live:

LineIf it is not green
ConnectedNot connected, with the reason. Most often: "Binance refused these keys. Check the key and secret, the key's IP list, and that Futures is on for it."
Trading allowed"Trading not allowed. Turn on trading for this key."
Futures on"Futures off. Turn on Futures for this key."
Withdrawals off"Withdrawals on. Turn them off: a trading key does not need them."
Locked to IP"Not locked to an IP. Binance can make such a key read-only."
Balance: …"Balance: 0. Add funds before you go live." Move money to the Futures wallet (Before you start).

The checklist also has a Leverage line. It shows the leverage the bot will use on each symbol:

  • "Leverage: … (the account's setting)": the bot does not change leverage. It uses what is set for the symbol on your Binance account.
  • "Leverage: … (set by the bot)": the bot's settings ask for a leverage, and the bot sets it on Binance.
  • If Binance allows less on a symbol, the line says so, for example "…: 20x at most, so the bot will use 20x."
  • If a symbol has an open position, the line shows the leverage now and the leverage the bot sets when the position is closed.

Leverage does not change the size of an order. It changes how much margin Binance locks for it (margin = order value / leverage).

To fix a line, change the key on Binance (Your Binance API key), then press Test connection.

Saved keys are shown as dots. The Lab never shows them again. To test them later, press Test connection. To use a different key, press Replace keys.

There is a link on this tab, How to create a Binance API key. It opens Binance's own guide.

Changing the keys of a live bot

A bot that already trades live uses new keys only after it restarts. Change them only when the bot has no open position: a restarted bot does not take back the positions it held before (see If the computer or server goes down). Save the new keys, then restart the bot: in the Strategy editor, press the ≡ button at the top (bot actions), choose Restart bot and confirm.

For a paper bot that goes live for the first time, you do not need this: step A4 restarts the strategy with the keys.

A4. Switch the strategy from paper to live ​

  1. Click the Strategies tab.
  2. Pick the strategy in the list on the left.
  3. Untick Emulator (paper).
  4. Press Save at the bottom. This saves the change but does not apply it yet.
  5. Press Restart 1 strategy at the bottom of the strategy list on the left. The strategy restarts, and now it places real orders on Binance.

If something stops it from trading live, one line under the switch says what, for example "Needs Binance API keys" or "ADA is not in the Free plan".

If you untick Emulator (paper) before you have added keys, the strategy stays on paper and a window API keys needed opens. Press Go to Exchange and do step A3 first.

WARNING

Switch a live strategy back to paper only when it has no open position. The switch restarts the strategy, and an open position is left on Binance without the bot.

A5. Keep the PC awake ​

  • Turn off sleep while the bot trades. On Windows 11: Settings → System → Power (on a laptop: Power & battery), and set sleep to Never when plugged in. On Windows 10: Settings → System → Power & sleep.
  • Stop the bot before you restart or shut down the PC. Right-click the bot in the left list and choose Stop. The Lab asks "Stop <name>? It cancels its orders and closes every open position." Confirm, and wait until it shows stopped.
  • After the PC starts again, start the bot again yourself: right-click it and choose Start. For a live bot the Lab asks again and shows Start live.

Path B: on a server ​

A server is a small computer in a data centre that you rent by the month. It does not sleep and it does not restart for updates on its own. You never need to work on it after the first setup. You manage the bot from the Lab on your own computer, as before.

One shot bot per server. Do not run a second bot on the same server. Rent a second server for a second bot.

B1. Rent a server in Tokyo ​

Binance's trading servers are in Tokyo. Pick the Tokyo region, so your orders reach Binance fast.

1 vCPU and 2 GB of memory is enough for one shot bot. Pick Ubuntu 24.04 LTS as the system. Any of these is fine:

ProviderWhat to pickPrice
Akamai (Linode)Shared CPU → Linode 2 GB (1 vCPU, 2 GB), region Tokyo, JPabout $12 a month
VultrCloud Compute, Shared CPU → Regular Performance, 1 vCPU, 2 GB, location Tokyoabout $10 a month
AWS LightsailLinux/Unix → OS only → Ubuntu 24.04 LTS, the $12 plan (2 GB, 2 vCPU), region Tokyo$12 a month (with a public IPv4 address)

Prices change. Check the price on the provider's page before you pay.

When you create the server:

  • Set a root password (Linode and Vultr ask for it). Write it down. You need it to log in to the server's console.
  • Turn on automatic payment. Add a card and let the provider charge it each month. If a payment fails, providers stop and then delete servers, and your bot goes with it.
  • AWS Lightsail only: open the server's Networking tab and press Create static IP, then attach it to the server. Without it, the server's address can change when the server is stopped and started, and your Binance key stops working.

B2. Find the server's IP address ​

Open the server's page at your provider. The public IPv4 address is shown at the top (four numbers with dots, for example 203.0.113.41). Write it down. You need it for your Binance key in the next step. The install command in step B5 prints it too: "This server's IP is 203.0.113.41. Lock your Binance API key to it".

B3. Make a Binance API key ​

Follow Your Binance API key. Lock the key to the server's IP address from step B2.

B4. Get the install command ​

  1. Open the Lab and sign in. Open Profile.
  2. Under pair key, press Make a pair key if this Lab has none. (On a second computer, enter the key from your first Lab instead: see Your pair key.)
  3. Under add a server, press Bot server, then Copy command.

The command looks like this (your code, key and hash are different):

sh
 f=$(mktemp) && curl -fsSL https://github.com/tradectl/releases/releases/download/v0.2.6/install.sh -o "$f" && echo "<hash>  $f" | sha256sum -c --quiet - && TRADECTL_PAIR_KEY='tctl-key-1:ABCD-…' sh "$f" --setup ABCDE-FGHJK; rm -f "$f"

It downloads the installer from GitHub and stops if it is not the exact file this Lab expects. The code works once and only for 30 minutes. If it runs out, press Bot server again for a new one. TRADECTL_PAIR_KEY is your pair key: the bot locks its connection with it, so tradectl.com can list the bot but cannot read its access key. The command is a secret: do not share it. It starts with a space, so most shells do not keep it in their history.

B5. Paste the command into the server's console ​

Every provider has a console in the browser. You do not need any other program.

  • Linode: open the server, press Launch LISH Console. Log in as root with the root password.
  • Vultr: open the server, press View Console. Log in as root with the password shown on the server's page.
  • Lightsail: open the server, press Connect using SSH. Then type sudo -i and press Enter, so the next command runs as root.

Paste the command and press Enter. It takes about a minute. At the end you see lines like these:

✓ tradectl … installed
✓ Logged in as you@example.com (this server only)
✓ shot installed
✓ Bot "tokyo-1" runs as a service: it starts on boot and restarts after a crash
✓ Bot "tokyo-1" is on tradectl.com
✓ Port 9103 open for the Lab
✓ This server's IP is 203.0.113.41. Lock your Binance API key to it
Open the Lab signed in as you@example.com: the bot is under My bots → tokyo-1.

All bots on one server use one tradectl.com account. If the server is already signed in to another account, the command stops before it changes anything and names both accounts. To move the server to your account, run tradectl logout on it and paste the command again. The bots already on that server move with it.

The bot gets the server's name. To choose another name, add --name and a name at the end of the command, for example ... --setup ABCDE-FGHJK --name tokyo-1. Use only a-z, 0-9, - and _.

If a line starts with ! and says "If your provider has a firewall, allow TCP port 9103 there", see step B6.

If something fails, the command says what to do. It is safe to run the same command again with a new code: every step checks first and skips what is done.

B6. Open port 9103 (only if your provider has a firewall) ​

The Lab on your PC connects to the bot on TCP port 9103. This is the only way to change the bot from your PC: tradectl.com does not send settings to your bot. If the port is closed, the Lab says so, and you can only change the bot on the server itself.

  • Lightsail: in the server's Networking tab, under IPv4 Firewall, press Add rule, choose Custom, protocol TCP, port 9103, and save.
  • Linode and Vultr: there is no provider firewall unless you made one. If you did, add a rule that allows TCP 9103 in.

B7. Connect the Lab to the server bot ​

  1. In the Lab, click Profile at the bottom of the left list.
  2. If you are not signed in: press Get API key (it opens your account page in the browser), copy a key there, paste it into the Lab and press Sign in.
  3. The server bot now shows in the left list, under the server's name. Click it to connect.

B8. Set up the bot, on paper first ​

The new bot has no strategy yet. You have two ways to give it one:

  • Copy your PC bot's setup. In the Lab's left list, right-click the bot on your PC and choose Copy to…. Pick the server bot. The strategies are added there in paper mode. Exchange keys are never copied.
  • Set it up from scratch. The Lab shows Set up <name>: choose shot, check the settings and press Start on paper.

Let it trade on paper for a while, so you see that it works on the server.

B9. Add your keys and go live ​

This is the same as on your PC:

  1. Open the bot's settings (right-click → Settings).
  2. Exchange tab: paste the key and secret, press Save keys, wait for "Connected. Binance accepts these keys." (step A3).
  3. Strategies tab: untick Emulator (paper), press Save, then press Restart 1 strategy (step A4).

If the Lab says Binance refused the keys, the most common cause is the IP list: the key must be locked to the server's IP from step B2, not to your home IP.

Add a strategy to a server bot ​

The setup line in step B5 already put shot on the server, so for shot you can skip this. A strategy you got on the website must be put on the server first, and on your PC too, because the Lab lists only the strategies that are on your PC.

  1. On the server. Open the server's console (step B5) and paste this line. It puts every strategy you made or got on the website onto the server:

    sh
    tradectl install all

    It ends with a line like "Installed 2/2 strategies."

  2. On your PC. In the Lab, right-click a bot on this computer → Settings → + strategy. Under From your website account, press Install next to the strategy. You do not have to add it to this bot: you can close the window.

  3. Pick it for the server bot. Right-click the server bot → Settings → + strategy, pick the strategy, check its settings and add it. A server bot that waits for setup shows it in Set up <name> instead.

  4. If the Lab then shows Restart bot, press it. Do this only when the bot has no open position: a restart does not take back open positions.

For a server bot, the Lab shows "Install on the server first" next to a strategy that is not on your PC yet. Do step 1 and step 2, then open the window again: the strategy is now in the list.

Stopping and starting a server bot ​

The Lab cannot stop or start a bot on a server. You do it in the server's console (step B5), with one line each. Replace tokyo-1 with your bot's name.

To stop the bot. It cancels its orders and closes every open position before it exits. This can take up to 3 minutes; wait for it. A bot you stopped stays stopped, even if the server restarts.

sh
tradectl stop tokyo-1

To start it again:

sh
tradectl service start tokyo-1

To see if it runs:

sh
tradectl service status tokyo-1

If the bot crashes, the server starts it again after 10 seconds. If it crashes 3 times in 10 minutes, the server gives up and the bot stays down until you start it again with the start line above. A bot that keeps crashing should not keep trading.

Your Binance API key ​

The bot uses an API key to place orders on your Binance account. Make a key that can trade Futures and cannot withdraw. Lock it to one IP address.

Binance's own guide: How to create API keys on Binance.

Create the key ​

  1. Log in to binance.com. Click your profile icon, then Account → API Management.
  2. Press Create API. Choose System-generated.
  3. Give it a name, for example tradectl. Confirm with your 2FA.
  4. Binance shows the API Key and the Secret Key. Copy both now. Binance shows the secret only once. Keep them private: anyone who has them can trade on your account.

Set the permissions ​

Press Edit restrictions on the new key.

  1. Under IP access, choose Restrict access to trusted IPs only and enter the IP address (see below). Binance gives trading permission only to a key that is locked to an IP, so do this first.
  2. Tick Enable Futures.
  3. Leave Enable Withdrawals off. The bot never needs it. Leave every other trading or transfer permission off too.
  4. Press Save and confirm with your 2FA.

If Enable Futures cannot be ticked: open your Futures account first, then make a new key. A key made before the Futures account was opened may not get Futures permission.

Which IP address to enter ​

Server path: the server's public IPv4 address from step B2.

PC path: your home internet's address, as the internet sees it. In your browser, search for what is my IP and use the IPv4 address it shows (four numbers with dots).

Most home internet addresses change from time to time (after a router restart, or every few days). When yours changes, Binance refuses the key, and the bot can no longer place or cancel orders. The Lab shows "Binance refused these keys". Then:

  1. Find your new IP (search what is my IP again).
  2. On Binance, open API Management, press Edit restrictions on the key, replace the old IP with the new one, and save.
  3. In the Lab, open the Exchange tab and press Test connection.

To avoid this, ask your internet provider for a fixed (static) IP address, or use a server. Binance also lets you turn off its Default Security Controls so a key works from any IP. We do not recommend it: a key that works from anywhere is worth more to a thief.

If the computer or server goes down ​

This section explains what happens to your open positions when the bot is not running.

Stop is safe ​

When you stop the bot (the Lab's Stop on your PC, or tradectl stop on a server), the bot cancels its orders and closes all its open positions at market price before it exits. Positions of other bots are not touched. So a stopped bot leaves nothing of its own open on Binance.

A crash, a power cut, sleep or lost internet ​

If the bot stops without a clean stop, nothing is closed. Your orders and positions stay on Binance exactly as they were.

  • Take-profit and stop-loss orders that are already on Binance keep working. Binance fills them even while the bot is off. The default shot settings place real stop-loss orders on Binance, so a normal position stays protected.
  • A position on a virtual stop-loss has no stop at all until the bot is back. A virtual stop-loss is kept inside the bot, not on Binance. It is off in the default shot settings. If you turned on virtual SL, your positions are not protected while the bot is down. See Virtual stop-loss.
  • A stop-loss that was not placed yet is missing. With the Stop-loss delay setting, the bot waits a few seconds after an entry fills before it places the stop. If the bot goes down in those seconds, that position has no stop.
  • Waiting entry orders stay on Binance and can still fill. A position opened this way while the bot is down has no take-profit and no stop-loss.

When the bot comes back ​

  • On a server, the bot starts again by itself: 10 seconds after a crash, and when the server restarts (unless you stopped it on purpose). After 3 crashes in 10 minutes it stays down (Stopping and starting a server bot).
  • On your PC, you start it again yourself in the Lab.
  • A bot that starts again starts blank. It does not take back the orders and positions it left behind. Positions with a take-profit and a stop-loss on Binance stay protected by those orders until one of them fills. Anything else is not protected.

With a watchdog ​

A watchdog (below) runs on a second machine and reads your Binance account every few seconds. When it is set to Auto-protect, it closes what the bot left broken:

  • A position with no take-profit order is closed after 12 to 20 seconds.
  • A position with no stop-loss order is closed after 12 to 20 seconds while the bot runs, and after 8 to 16 seconds when the bot is down.
  • A virtual stop-loss counts as a stop only while the bot runs. If the price passes the virtual stop and the position is still open, the watchdog closes it after 8 to 16 seconds. When the bot is down, a virtual stop-loss does not count, so the position is closed as one with no stop-loss.
  • The bot counts as down when the watchdog has heard nothing from it for 30 seconds. Then the watchdog cancels the bot's waiting entry orders, so a down bot cannot open new positions.
  • A stop or take-profit order left on a coin with no position is cancelled after 30 seconds, so it cannot hit your next position.

It closes only the part of a position that is not protected, and only with reduce-only market orders, so it can never open or flip a position.

Without a watchdog ​

Only the take-profit and stop-loss orders already resting on Binance protect you. A position on a virtual stop-loss has no stop until the bot is back, and a position opened by a waiting entry while the bot was down has no take-profit and no stop-loss. After any crash or power cut, open Binance and look at Positions and Open Orders on the Futures page. Close any position that has no stop-loss.

What you should do now ​

  • Use a server for real money, and add a watchdog on a second machine.
  • On the server: turn on automatic payment with the provider (step B1), so the server is never deleted for a failed payment. Do the same for the watchdog's server.
  • For your tradectl plan: set a reminder in your phone's calendar a few days before your plan ends. Payment does not renew by itself (Paying for your plan).
  • Keep the default stop-loss on Binance (leave virtual SL off) unless you know why you need it.

A watchdog on a second machine ​

The watchdog is a small program that guards your bot from another machine. It uses its own Binance key to read your account, and it closes positions the bot left without a take-profit or a stop-loss (With a watchdog says when). It is your safety net when the bot's computer or server dies.

It must run on a different machine from the bot: if they share a machine, they die together. A small, cheap server is best. Pick a different provider and a different region from the bot's server (for example Frankfurt), so one outage cannot take both. Another Linux computer that is always on also works (the install command needs Linux with systemd, like Ubuntu).

ProviderWhat to pickPrice
Akamai (Linode)Shared CPU → Nanode 1 GB, region Frankfurt, DE, Ubuntu 24.04 LTSabout $5 a month

Use the same steps as for the bot's server (step B1): Ubuntu 24.04 LTS, a root password, automatic payment. Then:

W1. Get the install command ​

In the Lab, open Profile. Under add a server, press Watchdog server, then Copy command. It has --watchdog in it:

sh
 f=$(mktemp) && curl -fsSL https://github.com/tradectl/releases/releases/download/v0.2.6/install.sh -o "$f" && echo "<hash>  $f" | sha256sum -c --quiet - && TRADECTL_PAIR_KEY='tctl-key-1:ABCD-…' sh "$f" --setup ABCDE-FGHJK --watchdog; rm -f "$f"

The code works once, for 30 minutes, like the bot's code.

W2. Paste it into the watchdog server's console ​

Log in to the console as root (step B5) and paste the command. At the end you see:

✓ tradectl … installed
✓ Logged in as you@example.com (this server only)
✓ The watchdog runs as a service: it starts on boot and restarts after a crash
✓ Port 9110 open for the Lab and your bots
✓ This server's IP is 198.51.100.7. Lock the watchdog's own Binance API key to it
Open the Lab: the watchdog is under My bots. Use "+ guard a bot" there to guard your bots.

Write down the IP. The watchdog keeps running after a crash or a server restart by itself. It never gives up: unlike a bot, it starts again after every crash, because a watchdog that is down guards nothing. If it crashes, you get a Telegram line (W6).

W3. Open port 9110 (only if your provider has a firewall) ​

Your bots and the Lab connect to the watchdog on TCP port 9110. If the result has a line starting with ! about a firewall, allow TCP 9110 in at your provider, as in step B6.

W4. Make a second Binance key for the watchdog ​

Follow Your Binance API key, but lock this key to the watchdog server's IP from W2. Futures on, withdrawals off. Do not reuse the bot's key: each key is locked to its own machine.

W5. Guard your bot from the Lab ​

  1. In the Lab, the watchdog shows in the left list, like a server bot (sign in under Profile if you do not see it). Click it. The watchdog view has two tabs, Monitoring and Settings.
  2. Press + guard a bot.
  3. Step 1 of 2, which bot: pick your trading bot. Press Next →.
  4. Step 2 of 2, market & credentials: choose the market the bot trades, and paste the watchdog's Binance key and secret from W4. Press Create and guard.
  5. Press Connection string next to the bot. It copies a line.
  6. Open the trading bot's settings (right-click → Settings), go to the Watchdog tab, paste the line under Connection string and press Save. The Lab says if it applies now or at the bot's next restart.

W6. Telegram alerts ​

The watchdog tells you on Telegram every time it acts. In the Lab, open Profile and press Connect Telegram (it opens @tradectlbot; tap Start). Then in the watchdog's Settings, under Telegram alerts, choose use the shared bot.

W7. Alert only first, then Auto-protect ​

A new watchdog is Alert only: it watches and sends alerts, but never closes anything. Leave it like this for a day and read its alerts. When they make sense, open the watchdog's Settings, under Authority & policy choose Auto-protect, and press Apply settings. The banner at the top of the watchdog view should now say Protecting. You cannot switch to Auto-protect until Telegram alerts are set (W6), because nobody would learn what it closed. If alerts stop working later, the watchdog keeps guarding and warns you in the Lab.

On the Monitoring tab you see every position the watchdog sees, marked protected or NOT PROTECTED.

WARNING

With Auto-protect on, the watchdog closes any position on that Binance account that has no take-profit and stop-loss, also one you opened by hand. This is one more reason for the two rules: no hand trading on the bot's account.

W8. Optional, advanced: a free alarm if the watchdog's server dies ​

If the whole watchdog server dies, it cannot tell you. An outside check can. The watchdog sends a short "I am alive" signal once a minute to a web address you give it, and a free service such as healthchecks.io warns you (by email, or Telegram) when the signals stop.

  1. Make a free account at healthchecks.io and add a check. Set its Period to 1 minute and its Grace to 5 minutes. Copy its ping URL (it looks like https://hc-ping.com/…).

  2. In the Lab, open the watchdog and press Export config. It copies the watchdog's settings, without keys.

  3. Paste them into Notepad. Find your account (the block with "label") and add one line inside it:

    json
    "deadman_url": "https://hc-ping.com/your-check-id",

  4. Copy the whole text. In the Lab press Import config, paste it, and press apply. Your keys and Telegram settings are kept.

The watchdog sends the signal only after a good check of your Binance account, so the alarm also fires when the watchdog runs but cannot read Binance.

Stopping and starting the watchdog ​

In the watchdog server's console. To stop it. Stopping closes nothing, but your accounts are not guarded until you start it again. It stays stopped after a server restart.

sh
tradectl stop watchdog

To start it again:

sh
tradectl service start watchdog

To see if it runs:

sh
tradectl service status watchdog

More about what the watchdog checks: Watchdog.

Paying for your plan ​

  1. Go to app.tradectl.com/account/billing.
  2. Under Starter or Pro, press Pay for 1 month or Pay for 3 months.
  3. Pay with Binance Pay on the page that opens. Send the exact amount shown. The amount has extra digits (for example 20.0137 USDT); they tell us the payment is yours.

When the payment arrives, your plan shows Starter until <date> (or Pro). Running bots pick it up by themselves within about 10 minutes. To make the Lab check now, open Profile, find the Plan card and press Refresh.

Paying again for the same plan before the end adds the days to the current period. If you change plan, a new period starts and the days you had left are converted into it.

The plan does not renew by itself. We send a reminder by email (and on Telegram, if you connected it) 7 days and 1 day before it ends. If you signed up with GitHub and see "Add your email" on the website, add it, or the emails cannot reach you. Set your own reminder too.

When the plan ends, nothing is closed. Your bots keep running and keep their take-profit and stop-loss orders. They move to the Free limits: no new entries on symbols outside BTC, ETH, XRP, SOL and BNB, and new orders are cut to $20. Pay again and they go back to full size without a restart.