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
$1B+Cumulative volume
70,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 algorithmic developers turn into a 24/7 technical support desk. Your strategy required deep quant skill to engineer, delivering it should not consume the time you need to build the next one.

  • Manual File Distribution: Sending .ex5 files and re-explaining VPS and MT5 setup steps to every single buyer.
  • Environment Drift: Debugging unique broker setups, terminal builds, and local OS issues for each client.
  • Fragmented Client Context: Searching endless chat threads to figure out who is live, who is stuck, and what was configured.
  • Support Cannibalization: Burning high-value quant research hours answering low-level software installation questions.
  • Blind Client Health: Zero centralized visibility into real-time bot performance, runtime errors, or expansion opportunities.

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 streamlined paths to deployable trading logic

Create EA is the native delivery engine inside your branded product. You build and deploy independently, never competing against other developers in a public marketplace.

01 Upload EX5 Deploy pre-compiled binaries instantly.

Ingest your existing compiled .ex5 files directly into Senti's managed execution pipeline. Your intellectual property stays 100% private, zero source code handoff required.

02 Author with AI Iterate from structured specifications.

Convert strategy parameters and logic descriptions into deployable automation workflows using AI assistance. You retain full authority to test, backtest, and approve code before rollout.

Neither path guarantees trading performance. You maintain full discretion over code release and testing.

[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 your delivery workflow becomes

Senti replaces chaotic manual file delivery with an automated, institutional software distribution pipeline.

Without an operating layer
With Senti
Emailing .ex5 binaries and lengthy PDF installation guides
Upload once via .ex5 binary or author from logic specs
Hand-holding each client through VPS setups and terminal logins
One standardized activation flow completed independently by users
Digging through chat histories to diagnose client account errors
Dedicated workspace with unified account health and telemetry
Prioritizing strategy updates from vague chat anecdotes
Data-driven updates based on aggregate runtime logs
Blasting generic upsells to unsegmented email lists
Contextual add-ons triggered by actual active trading volume
[06]Ownership / 06 : 10

You keep what makes your business valuable

Senti is pure execution middleware. We never catalog, marketplace, or claim ownership of your proprietary trading strategies.

The developer owns
Senti provides
Proprietary strategy IP, source code, and parameters
The Create EA workflow and continuous runtime pipelines
Backtesting, model validation, and deployment approvals
Institutional trading automation infrastructure
Customer commercial relationships and communications
Centralized workspace and multi-account context
Software licensing terms, pricing, and client consent
Frictionless self-serve activation flows for end users
Strategy-specific logic support and custom iterations
Platform-level health monitoring and engineering escalations
Non-custodial by design

Zero Client Capital Custody

Client funds never touch Senti. Capital remains deposited directly inside the client's own broker account, running on trade-only execution permissions.

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

$0 infrastructure fees for developers. Monetize your own audience.

Strategy developers pay $0 in platform fees. End users subscribe directly to Senti's underlying automation runtime through your branded portal, while you keep 100% of your strategy licensing revenue and broker rebates.

Basic $39.99/month

Entry access for end users inside your branded product.

  • Standard Create EA self-activation flow
  • Dedicated single Trade Account workspace
  • Always-on automation runtime & web monitoring
Pro $99.99/month

Expanded capacity for active traders.

  • Everything in Basic
  • Multi-account orchestration capacity
  • Verified MT5 broker connectivity
Advanced $199.99/month

Maximum scale for heavy execution.

  • Everything in Pro
  • Highest account capacity tier
  • Priority infrastructure health & escalation support

You retain 100% of your software licensing, education fees, and direct broker IB volume rebates. Senti bills end users strictly for underlying cloud infrastructure.

Performance snapshot

18× Execution Volume: Manual vs. Automated Deployment

Across identical test windows and market conditions, an account operating Senti's automated runtime executed 144 XAUUSD lots versus just 8 XAUUSD lots traded manually.

  • Zero Missed Entries: Automation executes disciplined setups 24/7 without emotional hesitation or execution latency.
  • Accelerated IB Rebates: Higher continuous execution volume unlocks maximum qualifying volume tiers under your broker's IB partnership agreements.

Data reflects live beta telemetry; individual volume depends on market conditions and specific strategy configurations. Review the case-study method and caveats.

[08]Getting started / 08 : 10

Start with one EA, not a full migration

Pilot path

Prove the service on one EA before you scale it.

Five steps from a single working EA to a service ready for more customers:

  • 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.