Custom MetaTrader 5 trading robot development · Oxarus Quant Tell us how you enter, manage and exit a trade, and we'll write a robot, indicator or panel for MetaTrader 5 built for you alone. Breadcrumbs: Oxarus home › Oxarus Quant › Custom Robots NOTICES - Interface data marked as representative is illustrative; it is not a real client, result or measurement. - Not investment advice. Trading in financial markets carries a risk of losing capital. SECTIONS - your rules, run by a robot. - just describe it. - the robot's journey. - beyond the robot. - what we do and don't. - tell us about your method. YOUR RULES, RUN BY A ROBOT. QUANT · CUSTOM ROBOTS Have a method you've been running by hand for years? Walk us through your entry, stop, trade management and exit rules. We'll write a MetaTrader 5 robot built for you alone. https://oxarus.com/en/quant/robots - Describe your strategy → open_page(path="/quant/robots", anchor="cta-heading") - How to describe it → open_page(path="/quant/robots", anchor="brief") - Your strategy, coded for you alone - Specification first, code second - We work under an NDA 1. Your rules 2. Code 3. On the chart Representative interface data · Representative screen. Not investment advice. - window: MetaTrader 5 - symbol: EURUSD · H1 - briefTitle: Client notes - Entry - text: With price above the 50 EMA, buy when a green candle engulfs the red one. - Stop - text: Stop 5 pips below the last swing low. - Manage - text: Once 20 pips in favor, move the stop to break-even, then trail it 15 pips behind. - Risk - text: 1% of balance per trade. No new trades during news hours. - file: ClientTrendPullback.mq5 - running: Robot running - entry: Buy - sl: Stop - be: Break-even - trail: Trailing stop File · View · Insert · Charts · Tools · Window · Help M1 · M5 · M15 · M30 · H1 · H4 · D1 · W1 · MN - algo: Algo Trading - Trade - Exposure - History - Journal - Experts - waiting: Waiting for the approved specification… - compiling ClientTrendPullback.mq5 - including RiskSizing.mqh, NewsWindow.mqh - 0 errors, 0 warnings, 312 msec elapsed - ClientTrendPullback (EURUSD,H1) initialized - entry condition met: bullish engulfing above EMA(50) - order #1042 buy 0.42 EURUSD at 1.08736, sl 1.08512 - position #1042 stop moved to break-even 1.08736 - position #1042 trailing stop 1.08921 JUST DESCRIBE IT. SPECIFICATION No coding required. Pick your rules or add one in your own words; the robot's specification, its MetaTrader inputs and the test list update as you choose. https://oxarus.com/en/quant/robots#brief - How should it enter a trade? - Moving average crossover - Support / resistance breakout - At a set time, on a set condition - How should the trade be managed? - Fixed stop and target - Break-even, then trailing stop - Partial take-profits - Position size? - Fixed lot - Percent of balance - When should it stay out? - Around major news releases - During the Asian session - Friday evening Specification - A buy opens when the fast average crosses above the slow one; a sell opens when it crosses below. - A buy opens when price closes above the highest high of the last 20 candles; a sell opens when it closes below the lowest low. - At the set time, a single trade opens if the defined condition is met. - Every trade opens with a fixed stop and a fixed target. - Once price moves in favor, the stop moves to the entry level, then trails at a set distance. - Part of the position closes at the first target, and the rest at the second. - Every trade opens with the set fixed lot. - Lot size is calculated from the stop distance so each trade risks the set percentage of balance. - No new trades from 30 minutes before to 30 minutes after major news. - No new trades during the Asian session. - No new trades after 20:00 on Friday. MetaTrader inputs How the rules play out on the chart - The conditions under which the robot enters - How an open trade is protected and closed - How much is risked on each trade - Optional: times to stay out of the market - Your own rule · clarified on the call - placeholder: e.g. Close all trades at the Friday close - clear: Clear Behavior tests - state: ready to test Interface labels: Specification completeness · updated · Optional: a rule the options don't cover THE ROBOT'S JOURNEY. PROCESS We get your sign-off at the end of every step. No rule goes into the code unless we've agreed on it. https://oxarus.com/en/quant/robots#journey-heading 1. Discovery call · NOTES We walk through your method together, using example trades on the chart. - Representative interface data · Representative What this step produces - file: call-notes.md - Method - v: Buy pullbacks to the 50 EMA in the trend direction - Example trades - v: Entries and exits marked on the chart - Open question - v: Is the stop measured from the last swing low or the last two? - Open question - v: Which calendar defines news hours? 2. Specification · SIGN-OFF Every rule becomes a clear sentence, with nothing left ambiguous. You approve it. - Representative interface data · Representative What this step produces - file: SPEC-0142 · rev 04 - §1 Entry - v: Buy on a bullish engulfing candle above the 50 EMA - §2 Stop - v: 5 pips below the last swing low - §3 Manage - v: Break-even after 20 pips, then a 15-pip trailing stop - §4 Risk - v: 1% of balance per trade; no new trades during news hours - Sign-off - v: Approved by the client 3. Code · MQL5 The robot is written in MQL5. Inputs come with names that make sense to you. - Representative interface data · Representative What this step produces - file: ClientTrendPullback.mq5 - Compile - v: 0 errors, 0 warnings - Inputs - v: InpRiskPercent · InpEmaPeriod · InpStopBufferPips - Modules - v: RiskSizing.mqh · NewsWindow.mqh - Traceability - v: Every spec clause links to its place in the code 4. Behavior test · TEST In the Strategy Tester, we verify trade by trade that the robot follows your rules exactly. - Representative interface data · Representative What this step produces - file: Strategy Tester · EURUSD,H1 - §1 Entry - v: Entry condition verified on every trade - §2 Stop - v: Stop placed at the rule's level on every trade - §3 Manage - v: Break-even and trailing steps follow the rule - §4 News - v: No new trades opened inside the news window 5. Delivery and setup · DELIVERY We deliver the compiled, licensed .ex5 file with setup notes. The scope of post-delivery fixes is set in the contract; source code comes under a separate agreement. - Representative interface data · Representative What this step produces - file: Delivery package - ClientTrendPullback.ex5 - v: Compiled, licensed robot - Setup notes - v: What each input does and how to install - Test report - v: Rule checks from the Strategy Tester - Fix support - v: Scope agreed in the contract - ClientTrendPullback.mq5 - v: Source code, under a separate agreement The next step starts once you sign off. Interface labels: Previous step · Next step BEYOND THE ROBOT. WHAT WE BUILD Besides robots, we write indicators, scripts, panels and alert services, and port older robots to MT5. Pick a file. https://oxarus.com/en/quant/robots#catalog-heading - Trading robot A robot that opens, manages and closes trades according to your rules. - folder: Experts - file: Robot.ex5 - Example: A robot that scales in on trend reversals - Inputs: 14 - Platform: MT5 - Delivery: .ex5 - kind: Expert Advisor - Custom indicator An indicator that draws your own levels, zones or calculations on the chart. - folder: Indicators - file: Indicator.ex5 - Example: An indicator that plots the previous day's levels automatically - Inputs: 8 - Platform: MT5 - Delivery: .ex5 - kind: Custom Indicator - One-off script Short tools you run once to get a specific job done. - folder: Scripts - file: Script.ex5 - Example: A script that closes every open trade in one click - Inputs: 3 - Platform: MT5 - Delivery: .ex5 - kind: Script - Trading panel A panel that calculates lot size and sets stop and target by dragging them on the chart. - folder: Experts - file: Panel.ex5 - Example: A panel that sizes lots from a risk percentage - Inputs: 11 - Platform: MT5 - Delivery: .ex5 - kind: Expert · Panel - Alerts and notifications Notifies you by phone, email or Telegram when a condition is met. - folder: Services - file: Alert.ex5 - Example: A service that messages Telegram when a level breaks - Inputs: 6 - Platform: MT5 - Delivery: .ex5 - kind: Service - Migration and fixes We port your MetaTrader 4 robot to MT5, and fix robots that don't work. - folder: Experts - file: MT4_to_MT5 - Example: An MT5 version of a legacy MT4 robot - Inputs: — - Platform: MT4 → MT5 - Delivery: .ex5 + report - kind: Port & fix - Delivery - ex5: Compiled, licensed .ex5 - ex5 tag: Default - mq5: Source code (.mq5) - mq5 tag: Separate agreement WHAT WE DO AND DON'T. STRAIGHT TALK https://oxarus.com/en/quant/robots#honest-heading We do - Turn the strategy you describe into code, exactly - Test that the robot follows the rules - Keep your code and strategy confidential - Provide fix support after delivery We don't - Suggest strategies or call market direction - Promise profits - Manage your account or touch your trades - Sell the same robot to anyone else MQL5 seller profile We hold a verified seller account in the MQL5 community. A robot written for you is never listed on the Market; it is delivered to you alone. - Account: Verified seller - Platform: MetaTrader 5 - Delivery: Licensed .ex5 - Source code: By separate agreement Market · Seller profile - handle: MQL5 Market · Seller · Oxarus Oxarus - monogram: OX Verified seller - platform: MetaTrader 5 - Experts - code: EA - Indicators - code: IND - Utilities - code: UTIL - file meta: MT5 · .ex5 Licensed .ex5 · Source code by agreement · Custom work stays private Not investment advice. Trading in financial markets carries a risk of losing capital. We do - Each rule maps to code, point by point. Delivery is a compiled, licensed .ex5 file; source code comes under a separate agreement. - A Strategy Tester report shows that every rule triggers correctly. - An NDA is signed before any work begins. - Bugs found after delivery are logged and fixed; the scope of that support is set in the contract. We don't - The strategy is yours; we only code the rules you define. - No robot can know future outcomes, and we won't write anything that claims to. - We never ask for your account details; you run the robot in your own terminal. - A robot written for you is never sold to another client. TELL US ABOUT YOUR METHOD. ROBOT Write out your rules in a few sentences and, if you can, attach screenshots of example trades. We'll pin down scope and timeline, then get back to you. https://oxarus.com/en/quant/robots#cta - Describe your strategy → start_project_brief(topic="quant") - info@oxarus.com → contact(subject="Custom robot") ACTIONS - Describe your strategy → open_page(path="/quant/robots", anchor="cta-heading") - How to describe it → open_page(path="/quant/robots", anchor="brief") - Describe your strategy → start_project_brief(topic="quant") - info@oxarus.com → contact(subject="Custom robot") - Türkçe → switch_locale(locale="tr", path="/quant/robots") RELATED PAGES - Oxarus Quant