Trading Technology

MetaTrader Automation

Expert advisors, custom indicators and bridges for MT4 and MT5, built with risk guards, restart recovery and demo testing, then monitored on a VPS so you know when something stops.

Discuss your projectDiscuss your MetaTrader EA

From the Strategy Tester to a live terminal

An EA that looks good in the Strategy Tester can still fail on a live account: requotes, broker-specific symbols and stop levels, a terminal restart that leaves the EA unaware of its open trades, or a lost connection nobody notices. We build expert advisors, custom indicators and bridges to external systems in MQL4 and MQL5 for traders, signal providers and brokerage teams, test them on demo accounts and set up monitoring that tells you when something stops. You define the strategy; we build the software and make its behavior visible.

AI-assisted, expert-led MetaTrader development

How AI assists

  • Drafts MQL4 and MQL5 code from your written strategy rules for engineers to review line by line
  • Translates logic between MQL4, MQL5 and Pine Script and flags calculation differences to verify
  • Generates test cases for trade-server errors such as requotes, invalid stops, closed markets and low margin
  • Reviews Experts and Journal logs to trace why an order was skipped, rejected or sent twice

What our experts own

  • Engineers own order handling, restart recovery by magic number, risk guards and the kill switch
  • Terminal logins, bridge keys and VPS access are set up by engineers and kept out of EA code
  • Backtests are reviewed by people, and every EA runs on a demo account before any live use
  • You own the strategy and every trading decision; we build, test and monitor the software

From signal to monitored order in MetaTrader

Illustrative EA on a VPS terminal; MT4 and MT5 differ in detail, and your written rules decide every entry.

  1. Signal check

    On each new bar the EA applies your rules, or polls your signal service via WebRequest, skipping repeats.

  2. Risk guards

    Daily loss, open exposure, trading hours and the kill-switch flag are checked before any order is built.

    Checkpoint: Kill switch or loss limit halts orders

  3. Broker-ready order

    Lot size, symbol suffix and stop distance follow your broker's settings; the order carries the EA's magic number.

    Checkpoint: Live lot sizes approved by you

  4. Trade-server reply

    Requotes, invalid stops or a closed market follow your spec's handling, with capped retries and a logged reason.

  5. Restart recovery

    After a terminal restart, the EA rebuilds its state from open trades by magic number before acting again.

  6. VPS heartbeat

    Heartbeats and terminal logs are shipped off the VPS, so a disconnect or stopped EA raises an alert.

When something fails: If the terminal crashes or loses its connection, auto-restart and recovery run before any new order, and you get a push, email or chat alert.

What you receive

MetaTrader EAs, indicators and bridges

  • Expert advisors in MQL4 and MQL5

    EAs that implement your entry, exit and sizing rules, with daily-loss and exposure limits, a kill switch and clear handling of trade-server errors.

  • Custom indicators

    Indicators and multi-timeframe signals built to your specification, checked for repainting, with matching MT4 and MT5 versions when you need both.

  • Bridges and API connections

    Links to webhooks, databases, signal sources and other platforms via WebRequest, sockets or the MetaTrader 5 Python package, with duplicate-signal checks.

  • Backtesting and forward testing

    Strategy Tester runs with realistic costs, out-of-sample and walk-forward checks to expose overfitting, then demo forward tests. Results are evidence, not forecasts.

  • VPS setup and monitoring

    Terminal hosting on a VPS with auto-restart, heartbeat checks and log collection, plus alerts when the terminal disconnects or the EA stops running.

  • Equity and risk dashboard

    A web dashboard of equity, drawdown, open exposure and trade history per account, with an error log that shows what the EA did and why.

Prepare an integration that your team can operate

  • Access and inputs

    Specify MetaTrader 4 or 5, the broker, demo account, symbols and exact strategy rules. Provide any existing MQL source and confirm the environment where the terminal or expert advisor will run.

  • A realistic first scope

    Start with a defined indicator, expert advisor or bridge. Agree restart behavior and loss limits; broker conditions and available interfaces may constrain the build. Backtests and demo results do not guarantee live trading results.

  • Handover and maintenance

    We deliver the agreed connection, test evidence, configuration notes and recovery instructions. Assign an owner for alerts and reconciliation. Provider changes, credentials and ongoing monitoring can be maintained under an agreed support plan; provider charges remain separate.

From written rules to a monitored EA

  1. 01

    Strategy specification

    Write your rules down precisely: entries, exits, sizing, trading hours, risk limits, and what the EA must do after an error or a restart.

  2. 02

    Prototype and backtest

    Build a first version and run it in the Strategy Tester with realistic spreads and costs, out-of-sample data and documented limits.

  3. 03

    Hardening and demo testing

    Add error handling, restart recovery, logging and the kill switch, then forward-test on a demo account with your broker's symbols and stop levels.

  4. 04

    Staged live rollout

    Go live on position sizes you approve, with VPS monitoring and alerts running; then hand over or continue under a support plan.

Two ways to work with AI tools

AI helps draft integration code and contract tests. Choose where it may process your code and API data.

Not sure? We'll recommend one during scoping. Compare AI delivery options

FAQ

Frequently Asked Questions

Can you convert a TradingView strategy to MetaTrader?

Yes. We translate Pine Script logic into MQL4 or MQL5, then compare indicator values and signals bar by bar on the same data, because calculation details, bar timing and fill assumptions differ between the platforms. Where results can't match exactly, we document the difference before the EA trades.

Where does the EA run, and who watches it?

Usually in a MetaTrader terminal on a VPS. We set up auto-restart, heartbeat checks and log collection, with alerts by push notification, email or chat when the terminal disconnects, the EA stops or orders are rejected. Monitoring is automated and continuous; who responds to alerts, and how quickly, is agreed in a support plan.

Will AI tools see my strategy code?

Only in the setup you choose. With Private / Local AI Engineering, models run inside a boundary you control, so your code and rules are processed there. With Claude Code / OpenAI Codex Engineering, we use commercial AI coding tools under provider terms, data handling and retention settings agreed with you before work starts. Either way, engineers review every change.

View all case studies
View all projects
View all articles

Related Services

All services

Ready to turn your rules into a MetaTrader EA?

Send your written rules, your broker and whether you use MT4 or MT5. We'll review them and outline the build, the demo testing plan and the monitoring.

Discuss your projectChat on WhatsApp