Turn confirmed sales into customer and license records
Automate the order workflow so a confirmed purchase creates the records and delivery steps your business expects.
For independently distributed MetaTrader products
Sell your EAs directly with licensing and customer management connected.
Integrate CML into your MT5 EA, apply supported account and broker-server rules, and connect licenses to your customer and order workflow. Add a storefront and activation portal using starter projects you can adapt to your business.
One product, end to end
Manage sales, licenses, releases, and customer delivery in one flow
Publish new EA versions from the same product record
Manage releases in CML and make approved versions available automatically to customers who are entitled to receive them.
Keep downloads, licenses, and activations together
Give verified customers access to eligible downloads and permitted activation actions without exposing the developer workspace.
Account rules and configuration
Define the checks your EA needs before you integrate them.
Trading account
Match the account identifier supplied by the integrated EA against a license rule.
Broker server
Evaluate the reported server value according to the documented host rule.
Remote configuration
Read defined values in product code. CML does not arbitrarily change every EA input or an existing EX5.
Network failure
Implement the documented cache, retry, and failure response intentionally. Do not place a network request on every tick.
1EA starts the checkThe SDK reads the license and current account context.
2Encrypted SDK requestLicense, trading account, and broker server are sent securely.
3CML evaluates accessLicense status, limits, and configured account rules are checked.
4Decision and configuration returnThe EA receives the access decision and approved runtime values.
5The EA applies the resultIt runs normally or follows your configured failure behavior.
Build and test the EA integration
Connect the SDK, verify one EA, then test every result.
- Integrate CML: Add the SDK inside your EA without uploading or exposing your source code to the platform. You decide where the compiled deliverable is stored and how eligible customers receive it.
- CML release delivery: Upload a compiled EA to a release record so eligible license holders can receive the version you publish.
- External delivery: Create a CML release that points to an EA stored in your own external drive or delivery service.
- Runtime configuration: Return the supported configuration values your integrated EA is designed to consume.
- Encrypted communication: SDK requests use HTTPS to protect data in transit.
Open installation requirements
Extend the workflow
Try the storefront and customer portal.
Marketplace SDK
Connect a merchant-owned storefront to CML catalog, customer, order, payment-record, and license operations. The merchant connects checkout and validates provider webhooks.
Activations starter
Adapt a verified customer portal for eligible license and activation actions. Server-side authorization—not a client filter—controls access.
Is this the right setup for your product?
Built for MT4 and MT5 EAs you sell and deliver directly.
The MT4 and MT5 SDKs provide the standard CML integration paths. Indicators require a different design because their WebRequest capabilities differ from EAs.
This page applies to EA editions distributed directly by you. An edition distributed through MQL5 Market must follow the Market rules and must not add external licensing controls or account- and server-dependent restrictions.
| Your product | Recommended path | Why |
|---|---|---|
| MT5 Expert Advisor | Use the MT5 SDK | Integrate the supported SDK into the EA and test the exact compiled build you plan to distribute. |
| MT4 Expert Advisor | Use the MT4 SDK | Integrate the supported SDK into the EA and test the exact compiled build you plan to distribute. |
| MT5 indicator | Use a different design | Indicators cannot call MQL5 WebRequest directly, so the EA integration path does not apply as-is. |
* Your EA can run in Strategy Tester, but CML license verification does not run there because MetaTrader disables WebRequest during testing.
Technical references: How MQL5 WebRequest works and MQL5 Market rules.
Assess one independently distributed EA.
Create a developer workspace and keep the MQL5 quickstart as your next destination after verification.