MQL5 or MQL4 — which one should your bot be built in?
The two languages look similar and are not. Choosing wrong means paying twice, because almost nothing carries across.
Read the guideTechnical notes on building, testing and deploying trading software. Written for people commissioning a build, not for people choosing a strategy.
The two languages look similar and are not. Choosing wrong means paying twice, because almost nothing carries across.
Read the guideA good quotation takes twenty minutes if the brief is complete, and three days of back-and-forth if it is not. Here is what makes the difference.
Read the guideMost of a conversion is straightforward. The 10% that is not is where every disagreement about the finished build comes from — so it is worth understanding first.
Read the guideThis is a software acceptance checklist, not a strategy evaluation. It tells you whether the build does what the specification says — nothing about whether the rules are good.
Read the guideAn EA that worked perfectly on one broker places nothing on another, and the log says retcode 10030. This is almost always one line of missing code.
Read the guideTime filters look like the easy part of a build. They are where a large share of real bugs live, because server time is not your time and midnight is a special case.
Read the guideFour moving parts, and each one fails in its own way. Understanding the shape of it makes the difference between a bridge you trust and one you watch nervously.
Read the guideA VPS is only worth paying for if it is configured so that nobody has to think about it again. Most are not.
Read the guideDevelopers who have only built for MetaTrader are repeatedly caught out by Indian segments. The differences are not subtle, and they are all schedule-shaped.
Read the guideBuffers are the one concept that separates an indicator that works from one that redraws itself, eats CPU, or quietly returns zeros.
Read the guideTwo EAs on one account without a magic-number scheme is not a configuration. It is two programs quietly closing each other's trades.
Read the guideMost disputes in custom software are not about code quality. They are about what was agreed, what was delivered and which build is running.
Read the guideThese are not strategy rules. They are the layer that sits outside the strategy and limits what a bug, a gap or a bad day can cost.
Read the guideEngineering notes from the work we do — platform differences, implementation detail, test procedure and delivery practice. They exist so that someone commissioning a build can ask better questions and recognise a good answer.
None of these guides contains trading advice, a strategy recommendation, a market view or any claim about results. We build software to your specification; what the software should do is always your decision.
Send your rules on WhatsApp and we will reply with a written scope, price and timeline.