How our licensing works, and why it is bound to your account

What a licence covers

Each licence is bound to a specific MT5 account number and validated against our servers at startup and periodically thereafter. Binding to the account rather than the machine means you can move between a laptop and a VPS freely without needing a new key — the licence follows the account, not the hardware.

Activations, transfers and demo accounts

• —Demo accounts do not consume an activation. Test as much as you want before binding to live.
• —Each licence tier includes a defined number of live account slots, shown in your account area.
• —Changing broker requires a transfer, which you can request yourself from the account area.
• —Transfers are rate-limited to prevent key sharing. If you need an exception, ask and explain.

What happens if validation fails

If the terminal cannot reach our validation service, the system continues managing existing positions and stops opening new ones until connectivity returns. We designed it this way deliberately: a network fault should never orphan an open trade, and it should never silently keep adding risk while unsupervised.

What binding protects, and what it deliberately does not

Account binding exists so that a licence corresponds to a known deployment rather than to an unlimited number of anonymous copies. It is not designed to make your life difficult: transfers between your own accounts are a normal, supported operation, and the process exists precisely because brokers change, accounts get upgraded and prop evaluations end.

Normal operations that are fully supported

• —Moving from a demo account to a live account.
• —Migrating to a different broker or a new account number.
• —Reinstalling after a VPS rebuild or hardware change.
• —Running a permitted demo alongside your live deployment for testing.

Security model and what we can see

Validation checks that a licence is active and bound to the account requesting it. It does not transmit your trading history, your balance or your positions, and it is not a channel through which anything can be executed on your account. The design principle is that a licence server should be able to answer exactly one question and nothing else.

Fail-safe rather than fail-open

If our validation endpoint were ever unreachable, the correct behaviour is not to disable a paying customer's system mid-trade, nor to grant indefinite unverified access. A short grace window keeps existing deployments trading through a transient outage while ensuring a genuinely revoked licence does not run forever.