Plans
What each plan allows, and what happens when a limit is reached.
Every plan can do everything the bot does: as many bots as you like, every setting, every risk control, and unlimited adds to an open position. What differs is below.
| Free | Pro | Max | |
|---|---|---|---|
| Live exchange keys | 1 | 3 | one per bot |
| Trades per day | 1 | 5 | unlimited |
| Logs overview | no | yes | yes |
| Trade notes & templates | no | yes | yes |
Logs overview adds up every patch of a bot across a date range you pick.
Trade notes & templates let you write your own thoughts on a trade, and keep a few starting points to write them from.
Your account page carries both your plan and how much of it you have used: a Plan tile at the top with your plan's name and when it ends, and a Plan usage section in the summary column down the right of every account page, showing how much of today's trade limit is gone, how many days your plan has left and how many of your key slots are in use. The bot's main menu shows your plan, when it ends and today's usage too, once your Telegram account is linked.
A refusal gives you the name of the plan above yours, what it would allow, and a link to Pricing so you can see what it costs.
Bots
Your bots, their exchange keys and today’s trading.
Buying, renewing and changing plans
Plans are bought on the website, under Billing in the sidebar of your account, and paid in USDT or USDC - Billing walks through it. Prices are listed in USD on Pricing. In short:
- Pro or Max is bought by the month or by the year, for 1 to 12 months or 1 to 3 years.
- Renewing the plan you are on adds the new period after the current one ends.
- Moving up starts at once, and the unused days of your current plan count toward it.
- Moving down waits and starts when your current plan ends.
- Free is never bought. It is where you are when no paid plan is running.
A paid plan ends at the end of the period you paid for, and nothing renews on its own. You get an email and a message on every bot you use 5 days before it ends, and again when it has. From that moment you are on Free - or on the lower plan you queued - and bots beyond Free's key allowance are paused automatically until you renew. A payment can be refunded within 7 days if no trade has been placed since and its plan has not been renewed or upgraded; see Refunds.
A plan an operator assigned to you by hand has no end date, and says so.
An invoice can be cheaper than the list price a few ways. A campaign Risbot happens to be running applies to any invoice, not only a first one. A referral discount applies only to your first Pro or Max invoice, and only if you have not already taken part as an invited friend - and it never stacks with a campaign: if both would apply, you get whichever of the two is larger, never both added together. A coupon, if you type one in at checkout, comes off on top of whichever of those two applied - see Coupons and gift cards.
Your plan and your credit belong to your website account, not to a Telegram account. Unlinking Telegram, linking the same one again, or linking a different Telegram account does not end your plan or touch your credit - whichever Telegram account is linked trades on the plan you already have. What unlinking does cost is covered in Linking Telegram.
The Plan usage dial counts from 00:00 UTC, for your whole account. That is deliberately not the same boundary as your bot's daily loss guard, which starts its day wherever that bot's own UTC offset says - one plan cannot have two reset times.
Trading needs a linked account
Link your Telegram account before you trade. Until you do, the bot still provisions you, still opens every panel and still saves every setting - it just will not place an order.
The message carries the two ways in, because nothing the bot can see says whether you have never registered or have an account you have not linked to this chat yet.
Armed bots
Your plan says how many of your bots can be armed at once - connected to an exchange and able to place orders. It counts connected exchange accounts across every bot you hold, not keys that were typed in and never proven; see Connect proves the key before the account counts as connected for what "connected" means.
Connect more than your plan runs and the extra bots are paused automatically. The oldest connection keeps the slot until you say otherwise, and the newer one waits. Nothing is taken from a paused bot: its key stays stored, its settings and risk rules stay exactly as you left them, its history stays, and every panel keeps working. The only thing it will not do is place an order.
A paused bot arms itself again the moment a slot frees up: disconnect the bot holding the slot, or move to a plan that runs more of them together.
Choosing which bot holds the slot
You do not have to disconnect anything to change your mind. On your account page, a bot reading Paused - over allowance carries Resume here. Press it, confirm, and that bot takes the slot from whichever bot has it now - which then reads Paused - over allowance in its place.
Nothing is disconnected either way, and there is no limit on swapping back. What it is not is a way to run more bots than your plan allows: the number armed at once never changes, only which ones they are.
This is why the message above says a bot has the slot for now rather than because it connected first. Connection order decides it until somebody chooses; after that, the choice does.
Seeing your bots
Your account page lists every bot your linked Telegram account owns, with what each one is doing. Five answers, and they are not the same:
| It says | It means |
|---|---|
| Armed | Placing orders |
| Paused by you | You pressed Pause on this bot. Nothing else changed |
| Paused - kill switch | Every bot you own is paused, from the button at the top of the page |
| Paused - over allowance | It has a key, and another of your bots is holding your plan's slot. Resume here moves the slot to this one |
| Rules only - no key | Configured, with no exchange key, so it places nothing |
A paused bot with no key says both - Paused by you · rules only - rather than picking one: fixing the pause would otherwise leave the second surprise waiting behind it.
Each row also carries the bot's Telegram handle and when a signal last reached it - "last signal 2h ago", or "no signals yet" for one that has never been asked to trade. That counts every signal, including the ones your guardrails refused: a bot refusing everything is exactly the one where knowing signals still arrive matters.
Every row opens showing its guardrails and its exchange key, and the chevron on its right collapses it. Beside the chevron, Trade logs opens Logs on that bot - every position it has closed, with its stats.
Above the list, a row of counts: how many bots you have, how many are armed, how many you paused, and how many of your plan's key slots are in use. A plan with no key cap says how many are connected instead of counting against a limit.
A closed row says its name, its state, its Telegram handle and when a signal last reached it. The figures are inside the card, not summarised on the header - the row is a bot with a name and a state, and open is its default.
Your bots
One bot, one exchange key, one set of guardrails. Everything a bot does is in its own card.
Exchange keys are connected, replaced and removed right here - see Connecting Your Exchange.
Adding another bot
Under the list, Add another bot shows every bot we run that you do not already have an account on. No plan caps how many bots you own - what your plan caps is how many of them can hold an exchange key and place orders, which is the armed bots limit above.
The panel is a shortcut, not a button that creates anything. Each handle opens that bot in Telegram; sending it the start command is what makes the account, exactly as it did for your first one. The new bot arrives with its own settings and its own guardrails, and with no key - so it stays rules only until you give it one.
If every bot we run is already yours, the panel is not there. Neither is it there while your account page cannot reach the list of our bots, rather than showing you a guess - Verify a bot reads the same list.
The key it holds
Under the guardrails, each bot shows its exchange key: which exchange, what the exchange calls that key, when it was connected, and the permissions the exchange granted it - in the exchange's own words rather than ours. The menu beside it replaces or removes the key.
A bot with no key says so and offers Connect Exchange, unless your plan's key slots are all in use. Then it reads Live trading needs a key slot and offers the plan that would give it one - Pro from Free, Max from Pro - because connecting a key your plan cannot run would leave that bot refusing every signal it receives. On a plan with no wider one above it, the block says the slots are in use and offers nothing, rather than pointing at a plan that does not exist.
What a bot is armed with
Every row opens. Inside is what that bot's guards are set to - read-only, because these are live risk settings and two places to change one is two places for it to be wrong. The panel links straight through to the bot that owns them.
Four rails, always these four, whatever is configured:
| Rail | What it says |
|---|---|
| risk / trade | The percentage of your total balance - the exchange wallet plus any collateral - that each trade may lose. Your stop is what turns that into a position size |
| max daily loss | Your daily loss guard's percentage cap, drawn as a bar with today's losses in it - 1.2% used · 1.8% left, or nothing lost today. A position still open shows as a grey stretch of the bar and is already taken out of what is left. The bar needs a live balance from the exchange to price the percentage; without one the rail shows the cap alone |
| max loss trades | Your daily loss guard's trade cap: how many trades have lost today, with any still open shown beside them - 1 / 8 today · 1 open |
| open positions | What this bot is holding on the exchange right now, read live each time the page loads |
Either loss cap that is not set says none · not set rather than being left out - a guard that is off and a guard that does not exist are different things. Under each is what it does when it is reached, which is not always the same for the two: on Cap Risk the percentage cap sizes your next trade down, while the trade cap has no dial to turn down and simply refuses. On Notify only neither stops anything - you get one warning and trading continues, and the rails say so.
The bar on max daily loss counts down what the guard has left, and it is the guard's own arithmetic rather than a second copy of it - the same function the bot's Daily Loss Limit panel reads, to the same two decimal places.
An open position is not a loss, and neither rail draws it as one. The guard does count it against both caps, at the full amount its stop could still lose, so it takes room on the bar and a mark on the trade count - but in grey, beside the losses rather than among them, and called open. Once it closes, it either becomes a loss or frees that room.
On a day when nothing has been lost and nothing is open it needs no exchange at all - zero lost is zero percent of any cap, so the rail reads nothing lost today whether or not your balance could be fetched. Once something has been lost, turning those dollars into a percentage needs the balance, and without one the rail shows the cap alone rather than a figure that quietly ignores the day.
Beyond that, it appears only where the day can actually be priced: a guard set to Notify only is not counting down to anything, a switched-off one is spending nothing, and a balance the exchange would not give up leaves the cap showing as a plain figure. None of those draw a bar, because a bar filling towards an end that does not stop you is worse than no bar.
Open positions is the one rail that is not a setting, and the one that can fail to load. It is a live call to the exchange, so a revoked key, an IP allowlist or a slow moment leaves it reading 0 · the exchange did not answer - and that foot is the part to read. A count of 0 under nothing in the market is a confirmed flat account; the same 0 under the exchange did not answer is a question nobody got an answer to. A bot with no exchange key reads 0 and nothing in the market, which is true: it reaches no exchange, so it holds nothing.
Your bot's day start and its trading days are not here. Both are set in the bot's own Daily Loss Limit and Trading Days panels, and read there too. The day start in particular is worth knowing about: it is the bot's own UTC offset, which is the same value as your time zone on this website - change either one and the other moves with it.
Refresh, above them, reads every figure again, and beside it is when they were last read - synced 2m ago, or reading exchange… while it works. They are worked out each time the page loads - trades that closed since the last check are settled with the exchange first - so a new day shows as reset without waiting for your next signal.
If the settings cannot be read at the moment you open the panel, it says so. Your guardrails are unchanged either way - the page failed to fetch them, it did not find them missing.
Under the rails is what they actually stopped:
Refused 9 signals this month for breaking these limits - 5 over your risk per trade,
4 past the daily loss cap.The count is every signal this bot refused since the 1st, and the month runs on UTC - not your display zone, and not the bot's own day offset, because one figure cannot use a boundary that differs per bot. At most two reasons are named, commonest first; the total covers the rest. A month with nothing refused says so rather than printing a zero, and a bot with no exchange key adds that nothing reached an exchange either way.
Where the settings are changed
Nowhere on this page. The rails are read-only, and the Configure in @yourbot link at the top of the panel opens that bot's own Risk Management panel, where they are - see Risk Management for what each setting does and how to change it.
Naming a bot
Every row starts as Bot 1, Bot 2 and so on - the Telegram bot it is reached through, which tells you nothing once you run three of them on three strategies. Click the pencil beside the name, type your own, and press Save. Enter saves it too; Escape leaves it as it was; clicking away saves.
Clear the field and save to take the name off again, and the row goes back to its slot wording. Forty characters is the limit; a longer one is refused rather than quietly shortened, so nothing is stored that you did not read back. A long name is still shortened with an ellipsis on a narrow screen - that is the row running out of width, not the name being cut.
The name is yours and nobody else's - it is not shown to anyone, and it is not what anything else calls that bot. Your trade history and your settings all still use the bot's own id, so renaming can never lose you anything.
With Telegram unlinked there is nothing to list - a bot takes its orders from the Telegram account that owns it, so linking comes first, and the panel on that page is where you do it.
Pausing your bots yourself
This is a different pause from the one above - nothing to do with your plan, and nothing the server decides for you.
One bot at a time: each row carries a small Pause switch beside its name. Press it and that bot stops placing orders; it then reads Resume, and pressing it starts that bot again. Nothing else on the page changes. While every bot is paused from the top of the page, each row still reads Resume - pressing it starts that one bot and leaves the rest paused.
All of them at once: a button at the top of the Bots page, beside its title, reads Pause all bots. Press it and every bot you own stops; the button then reads Resume trading. There is no confirmation dialog either way - one click, and a toast tells you it worked.
Both write the same thing, so they can never disagree: the kill switch is the per-bot switch applied to every row at once.
While it is on, every row reads Paused - kill switch rather than Paused by you. That is the same state worded differently on purpose: one button stopped all of them, and one button starts them again. Resume a single bot from its row instead and the kill switch is off - that bot trades, and the others read Paused by you until you resume them too.
Paused reaches every order the same way, including one that would only add to a position you already hold, and including a dry run. Nothing else about a paused bot changes: an open position stays open, its exchange key stays connected, and every setting and risk rule stays exactly as you left it. Pausing does not give up the bot's slot in your plan's armed-bot allowance either, so resuming can never fail for want of one.
A bot stopped by your plan - Paused - over allowance - carries Resume here instead of a pause switch. Nothing stopped that bot but the plan, so the control it needs is the one that moves a key slot, not one that stops it again.
It is yours alone - nobody else can pause your bots. There is no operator control for it, on the account page or anywhere else.
Trades per day
A trade counts when the exchange accepts the order. A signal the risk engine refuses costs you nothing, an exchange error costs you nothing, and adding to an open position is never counted at all. The count covers every bot on your account together.
The day belongs to your Risbot account, not to your Telegram account. A trade is recorded against the plan that paid for it at the moment it was placed, so unlinking Telegram and linking it again does not give you the day back, and neither does linking a different Telegram account. Linking your Telegram to a different Risbot account is judged by that account's plan and that account's day - what you have already placed today stays with the account that placed it.
If two signals arrive at the same moment and only one slot is left, they are settled one at a time: the first takes the slot, and the second is refused with the message above rather than both going through. This matters most on Free, where the whole day is one trade and two bots can fire together.
This day is not the Daily Loss Limit's day
Your plan's day resets at 00:00 UTC, the same moment for everyone - the Plan usage card and the refusal above both count down to it rather than printing the time, so there is no zone to mistake for your own. The Daily Loss Limit uses the UTC offset you set on that panel instead, so the two can reset at different times, and that is deliberate: a plan is one entitlement across all your bots, and your bots may not agree on what day it is.
If your plan cannot be determined
This is not a limit you reach by trading more. It means the server could not find a plan for your account at all, which is a configuration problem rather than something about your usage.
Every message above arrives as a Trade Rejected
notification, on the Reason: line, and is written to your trade history.