Account and Plans

The account menu at the foot of the sidebar opens the account area. Profile is who you are and how you sign in, and Billing is what your account may do and what it costs.

Signing in

A code sent to your address, a password once you have chosen one, or Google, or GitHub, or on Enterprise your company's own single sign on (see Teams and single sign on below). After the address, the sign in screen sends a code. Once you have signed in on this computer with an account that has a password, it asks first: Send a code or Sign in with password. The first sign in on a computer is always a code. A password is chosen through a link we mail to your address, from Security in Settings, and Forgot password? on the sign in screen sends the same link. Ten wrong passwords in a row close the password way for fifteen minutes; the code keeps working. The provider round trip ends back on the page with the session in a cookie the page cannot read, which is why nothing sensitive appears in the address bar on the way. Two factor authentication is available and is the recommended setting for an account that has a broker connected.

A new account sets up its profile once, before the app opens: a username (optional, shown on the leaderboard), the language, the country or Global for no country, and whether to get updates and discounts by mail. All of it can be changed later under Profile and General.

Look around first on the sign in screen, or ?guest in the address, opens a preview with fixed synthetic runs. Every control is inert and it reaches no endpoint that needs a session. The account area, the admin terminal and Community are the pages it cannot open, because a preview of somebody else's account is not a preview of anything.

What each plan may do

Prices include VAT. Enterprise alone is priced plus VAT.

The founding price. Pro costs 26 EUR a month instead of 39, or 19 instead of 29 billed annually; Max costs 59 instead of 89, or 44 instead of 69 billed annually. It goes to new accounts while founding places are left, and to everybody who has a founding code from our launch mail. The code is asked for in the checkout dialog, before you reach the payment page, and it can also be typed in under Settings, Billing. A code belongs to the first account that redeems it.

The founding price stays yours for as long as the subscription runs, and it carries across a change of plan or billing cycle. Pausing or cancelling the subscription ends it: a cancellation at the end of the period you have paid for, a pause straight away, and after a pause the subscription goes on at the regular price. A founding code that has been used once does not bring it back.

Backtests run on your own machine on every plan. The daily count limits how many, and the plan decides what a run may use: a run on TICK, or of a Rust strategy, below Max is refused with the upgrade dialog rather than quietly run on something else. Python, C#, Pine and block strategies run on every plan. Running on our servers is what the minutes are: the container is capped at what is left of your allowance, and the time is charged when it exits whatever the run ended as. Minutes can be topped up, on Billing or on the Test page where they run out, and do not expire.

Tick data is the expensive half of everything: about 588 KB for one day against roughly 5 KB for the same day's M15 bars, and the vendor time to fetch it is the same ratio. That is why it sits on Max and not on Pro, and why every plan below Max fetches candles.

Billing

Billing shows the current plan, the cycle, the renewal date and the payment method. Invoices, card changes and cancellation happen in the billing portal, which opens in your browser. Every purchase opens an order step first: what you buy and its price incl. VAT. On an account that already has a subscription it also shows what the change does: moving up happens in place, keeps your billing cycle and charges the prorated difference for the rest of the period that day; moving down or changing the cycle is booked for the period end, charges nothing now and names the live deployments it ends. A subscription, an upgrade, a trial, a pack or the cloud add on asks you to tick that the service may begin before the 14 day withdrawal period ends; the perpetual licence asks two boxes. The button reads Order with obligation to pay, and on a new purchase the Stripe payment page follows. A plan can be changed or cancelled at any time.

Withdraw from contract, the small button beside the plan, withdraws from a contract within its 14 days: choose the contract (or describe another one), confirm, and keep the receipt with the time it arrived. A confirmation mail follows. We refund within 14 days of receipt, less a proportionate amount for the time the service ran if you asked for it to start early. Nothing is refunded automatically. Cancelling, which only ends the renewal, is something else and happens in the billing portal.

It also shows this month's server minutes against the plan's allowance, and any minutes bought as a pack, which do not expire. Runs on your own machine never count toward either. On a plan with a monthly allowance of minutes, the packs are bought there too, the same way as AI credits, and on the Test page: a Buy minutes button in the failure panel of a refused run, and a Top up button on the notice that appears once a month when 80 % of the minutes are used.

When you reach a limit

Trying something your plan does not include opens a dialog that shows what the higher plan would have done about it: selecting TICK or exporting CSV on Free, running a Rust strategy below Max, asking for more optimizer workers than the plan runs, or choosing walk forward on Pro. For TICK it draws the same four bars twice, once without ticks and once with them, and on an OHLC run it counts the trades on screen that closed on a bar reaching both their stop and their target. The dialog leads to the order step, or to Billing to compare plans.

Free has one optimizer run a month, on the grid with two workers, counted on the server whether it ran here or there. A sweep that fails before its first pass gives the run back, and so does a sweep on the server that you stop, since it keeps no passes. Once it is used, the Optimize view shows an upgrade line, and the next run comes on the first of the month.

Three more come from the server. When a server run is refused because the minutes are spent, and last month's ran out as well, the dialog names the plan with more. On Max, Invite a teammate on Billing explains Enterprise and ends in a mail to us, since Enterprise is not bought in the app. And an annual subscription that has renewed twice is offered the perpetual desktop licence, once, the next time Billing opens; after that it is a row on Billing. Buying the licence ends the subscription when the year already paid for does, so nothing is charged twice.

The free trial is on Max. Before it starts, the order step shows its days, the end date, the plan and price incl. VAT it turns into, and the date to cancel by. A card is collected to start it and nothing is charged until the trial is up. From the waitlist it runs ten days, and the Max checkout from our launch mail starts with it. One trial per person.

Enterprise is a contract rather than a checkout. The floor of 490 EUR a month plus VAT includes five seats, each seat beyond them is 79 EUR a month plus VAT, and the year is invoiced. Write to us and we set it up.

Teams and single sign on

Settings, Team is where an Enterprise team lives. On the other plans the entry is greyed out.

• Seats. The owner invites colleagues by address. The invite is mailed, and signing in with exactly that address takes the seat, with everything the team's plan includes. An invite holds its seat until it is taken up or removed, and one account holds one seat.
• Roles. The owner and admins invite and remove members. Only the owner makes somebody an admin or takes it back.
• More seats. We add them on request, and they are invoiced for what is left of the contract year. A seat taken away is not refunded, and the count never goes below the seats in use: nobody is removed by a smaller number.

Single sign on works with any OpenID Connect provider: Entra ID, Google Workspace, Okta and the like.

1. Tell us the email domains your team signs in with. We verify them, and your provider is believed only for addresses on those domains.
2. In your provider, register an application and give it the Redirect address shown on the Team page.
3. Enter the Issuer, the Client ID and the Client secret, switch Sign in with single sign on on and save. The issuer is checked when you save, so a typo shows up there and not at somebody's first sign in.

The issuer is https://login.microsoftonline.com/<tenant id>/v2.0 for Entra ID, https://accounts.google.com for Google Workspace and https://<your org>.okta.com for Okta.

From then on Continue with SSO on the sign in screen starts from the address in the field. Colleagues from your domains who sign in that way get a seat while seats are free. Require single sign on closes the other ways in for addresses on your domains: codes by email, passwords, Google and GitHub. The client secret is stored encrypted and never shown again.

AI credits

The monthly AI allowance comes with the plan and expires with the month. Credit packs are bought once and do not expire. The allowance is always spent first. See AI Assistant for what a request costs.

Connecting a broker

The broker connection is Max and Enterprise, and it is demo accounts only. This is a research and testing product, not a trading terminal. The restriction is enforced in the main process and on the server, not by a checkbox in the interface: the server talks to cTrader's demo host only and keeps no live account.

The credential is written encrypted on your own machine. The switch Keep this connection on our server, in the Broker panel, hands it to our server, which keeps the demo accounts it opens, encrypted, so a deployment there can send orders while this app is closed. The panel then lists them under On our server. Switching it off, or disconnecting the last account, deletes the copy on the server and disarms every deployment that used it.

Orders from a deployment on our server. Start it under Live, On our server, open it, and on its Orders tab choose the account and press Arm. From its next signal on, each trade opens, reverses and closes a position on that account, every order with its stop and target; what it signalled before is not sent, and a trade it already holds is not copied. The tab lists every order and how it ended, and every signal skipped or refused with the reason (an instrument the account has no symbol for, a size below the broker's smallest, the market shut). Disarm stops the next order. Stopping the deployment or disarming leaves an open position at the broker with its stop and target, and nothing of ours closes it. A part close in the strategy is not sent: the account keeps the whole position until the rest closes. This machine sends no orders itself; its Live Deploy says where they are sent from.

A cBot or an MQ5 export is a different program on a different engine, with its own fills, spread and data. It will not reproduce the backtest. Test it on a demo account before it sees money.