For MQL5 & EA Developers

Sell the EA, not the install.

Upload an existing EX5 or Author with AI, then use Senti to simplify customer activation, follow up with context, improve the service, and make the next relevant offer.

Non-custodial MetaTrader 5 API & Whitelabel
Senti · Create EA
$600M+Cumulative volume
63,000+Closed deals
$38MSingle-day peak
99.9%Live-beta uptime

These figures show infrastructure activity and availability. They do not describe the performance of your EA or promise customer returns.

[01]The problem / 01 : 10

The code scales. The manual work does not.

After the sale, too many developers become an installation desk. The strategy took real skill to build. Delivering it should not consume the time you need for the next one.

  • Sending EX5 files and repeating the same MT5 and VPS instructions to every customer.
  • Checking broker environments and reconstructing a different setup for each account.
  • Searching old chats to remember who activated, who is stuck, and what was promised.
  • Answering the same setup questions instead of improving the strategy.
  • No clear view of which customers are live, where they are stuck, or when another service would genuinely help.

A Senti-powered Whitelabel product adds a customer-operations layer around your EA without taking ownership of your strategy or your customer relationship.

[02]Create EA / 02 : 10

Two ways into Create EA

Create EA is the strategy creation and delivery capability inside your Whitelabel product. It is not a public marketplace where your EA competes beside other developers.

01 Upload EX5

Bring an existing compiled .ex5 file into Create EA. The standard path does not require source-code handoff, so your source stays in your own development environment. Best for a working EA you already sell or support.

02 Author with AI

Turn a strategy specification into an EA through an AI-assisted authoring and iteration workflow. You remain responsible for testing, validating, and approving the EA before any customer rollout. Best for a new EA or a faster iteration from a clear spec.

Neither path is a guarantee of trading performance. You decide what is ready to ship.

[03]The end-user journey / 03 : 10

What your customer gets

Once your EX5 or AI-authored EA has been tested, approved, and made available inside the Whitelabel product, the customer gets a simpler operating journey:

01
Connect a supported MT5 Trade Account

inside the branded product.

02
Select and activate the EA

you have made available, with the supported settings and guidance you define.

03
Let Senti run the automation 24/7

without renting a VPS or keeping a local terminal and laptop online.

04
Monitor through the confirmed customer-facing surface

using the positions, orders, account status, and per-strategy fields included at launch.

05
Use pause or stop when included in the confirmed launch scope

without returning to the local MT5 terminal. Stop prevents new orders; open positions continue according to the EA's rules.

This is the end-user value of the Whitelabel model: your EA is delivered as an operating product and ongoing service, not as a file plus installation manual.

[04]The Create EA flow / 04 : 10

From one-off delivery to a repeatable customer lifecycle

01
Bring your EA

Upload a compiled EX5, or author with AI from a specification. Your source and strategy logic stay in your environment.

02
Activate consistently

Customers follow one standard Create EA activation path instead of a file-and-instructions handoff reconstructed for each account.

03
Support with context

Start each request with customer, Trade Account, and activation context, and distinguish an infrastructure issue from strategy behavior.

04
Improve from real patterns

Use recurring activation friction and support questions as inputs for the next EA or service iteration. You still make the product decisions.

05
Offer the next step

Make a relevant next offer when it fits the customer: another EA, an additional Trade Account, configuration, education, or premium support. You own the offer, pricing, and consent.

Senti makes the customer lifecycle easier to observe. It does not take ownership of your strategy or your customer relationship.

[05]Before and after / 05 : 10

What the customer journey can become

Without an operating layer
With Senti
Deliver by sending files and instructions
Upload EX5 or author with AI
Repeat MT5 and VPS setup customer by customer
Use one consistent activation path
Search chats and reproduce the environment
Start with customer and account context
Prioritize the next build from anecdotes
Learn from recurring operating patterns
Broadcast the same offer to everyone
Make a relevant next offer in context
[06]Ownership / 06 : 10

You keep what makes your business valuable

Senti is not an EA marketplace. It does not catalog or sell your strategy, and it does not replace your responsibility for strategy quality, licensing, risk disclosure, or customer authorization. Strategy IP stays with the developer.

The developer owns
Senti provides
EA logic, source code, and IP
The Create EA workflow
Testing, validation, and approval
Trading automation infrastructure
Customer relationship and communications
Workspace and Trade Account context
Offer, pricing, licensing, and consent
A standard activation path
Strategy-specific support
Infrastructure monitoring and escalation
Non-custodial by design

Capital does not enter Senti's custody

Your customers' funds stay where they already are.

  • Customer funds remain in the customer's own broker account.
  • Senti executes the supported automation workflow through the agreed access model.
  • Senti cannot withdraw or transfer customer funds.
  • The developer and customer remain responsible for strategy, risk, authorization, and applicable obligations.

Senti is trading automation infrastructure. It is not a broker, fund manager, copy-trading marketplace, signal seller, or promise of returns.

Review Trust & Security →

[07]Commercial model / 07 : 10

A Whitelabel model for developers with their own audience

Under Senti's standard Whitelabel model, a qualifying Strategy Developer typically pays $0 in Senti infrastructure fees. End users subscribe to Senti directly through your Whitelabel product on these tiers.

Basic $29/month

Entry access for end users inside your branded product.

  • Standard Create EA activation path
  • Trade Account workspace
  • Automation runtime and monitoring
Pro $59/month

More capacity for active end users.

  • Everything in Basic
  • Higher account and activation capacity
  • Supported broker connectivity
Advanced $99/month

For end users running the most activity.

  • Everything in Pro
  • Highest capacity tier
  • Priority infrastructure escalation

You keep the EA license, configuration, education, support, or other service revenue you charge under your own customer agreement. You also keep any broker rebate you qualify for under a direct IB arrangement with your broker; Senti does not intermediate that relationship. This is the standard Whitelabel structure, not a universal price promise for every engagement. Eligibility, scope, billing, data access, and commercial terms are confirmed in the applicable agreement.

Proof snapshot: one account, two execution methods

In one anonymized live-beta account, over the same window and instruments, the Senti EA closed approximately 144 XAUUSD lots versus approximately 8 XAUUSD lots traded manually — about 18× the trading volume.

This is one account over a short window. It is directional activity evidence, not a guaranteed multiplier, a forecast for another account, or a return claim. Review the case-study method and caveats.

[08]Getting started / 08 : 10

Start with one EA, not a full migration

  • Choose the pilot: bring one working EX5 or one clear strategy specification.
  • Select the path: Upload EX5 or Author with AI.
  • Map the operation: define activation, follow-up, support ownership, and escalation.
  • Run a controlled cohort: observe recurring friction and customer questions.
  • Improve and expand: refine the service before adding more customers, EAs, or paid offers.
[09]Who this suits / 09 : 10

Best fit for

  • independent MQL5 developers with active customers;
  • EA studios managing more than one strategy;
  • developers with a technical community or published work;
  • strategy businesses that repeatedly support installation and activation;
  • developers preparing to add another EA or higher-touch customer service.

The strongest starting point is a working EA, a real customer workflow, and a recurring delivery or support problem worth fixing.

[10]Common questions / 10 : 10

Common questions

Do I need to share my source code? +
No. The standard Upload EX5 path uses the compiled file and does not require source-code transfer. Your source stays in your own development environment.
Will Author with AI make a profitable EA for me? +
No such outcome is promised. Author with AI assists creation and iteration. You remain responsible for testing, validation, risk decisions, and approval.
Does Senti own or sell my EA? +
No. Your EA and strategy logic remain your IP. You own the customer relationship and commercial offer. The agreement documents data access, communications, and non-solicitation obligations.
Is Create EA a marketplace or a Whitelabel product? +
For the deployment described here, it is a capability inside your Whitelabel product. Your customer sees your supported brand, accesses the EAs you choose to provide, and keeps the commercial relationship with you. Senti does not list or sell your EA in a public strategy marketplace.
Will my customers need a separate Senti journey? +
They use the standard Senti product flow through your branded Whitelabel surface, configured for your brand and offer, while Senti remains the platform and infrastructure provider underneath. Branding, disclosure, billing, and support boundaries are confirmed before launch.
Does Create EA remove every installation or support issue? +
No. It standardizes the activation path and removes many repeated handoff steps. Strategy-specific issues remain with the developer; infrastructure incidents follow Senti's escalation path.
What should I bring to the walkthrough? +
One working .ex5 file or one strategy specification, your current customer activation flow, and the support issue you encounter most often.

Bring one EA. We map the rest.

See both Create EA paths and leave with a plan for activation, support, and expansion.

Read the docs The first conversation is a delivery review.