If you have source code with a license that allows redistribution, you can rebrand an Expert Advisor, give it your own name and identity, and sell it. Done right, it is a legitimate way to build a product line. Done wrong, it is piracy. Here is how to stay on the right side of that line.
First, check the license
This is the step people skip, and it is the most important one. You can only resell or rebrand code when the license permits it. Permissive open source licenses like MIT, Apache 2.0, and BSD generally allow commercial use and redistribution, often with a requirement to keep the original attribution. GPL allows resale too, but requires you to keep the derived work open source under the same license.
What you cannot do is take a commercial EA you bought, or an unlicensed file, and sell it as your own. That is copyright infringement.
Rebranding the EA
Once you have the legal right, rebranding is mostly editing:
- Rename the file to your product name, for example
MyBrandScalper.mq5. - Update the property block at the top of the code:
#property description,#property copyright, and the EA name shown on the chart. - Rebrand visible text: any Print, Comment, or Alert message the trader sees. Keep it in English and consistent with your brand.
- Keep required attribution: if the license requires crediting the original author, keep that line in the license file. You can still sell the product.
Compile a clean product
Compile the rebranded source to a fresh .ex5 or .ex4. Test it on demo to confirm nothing broke during editing. Our compile guide covers this end to end.
Decide what you sell
- Compiled only: you sell just the
.ex5. Buyers can run it but not read or copy the logic. Best for protecting your edge. - Full source: you sell the
.mq5too. Buyers can study and modify it. You can charge more, but your logic is exposed.
Package it professionally
A clean product package includes the compiled file, a short user manual explaining the inputs, and a license note describing what the buyer is allowed to do. Presentation matters as much as the code.
Add licensing if you want control
If you sell compiled EAs and want to limit them to specific accounts, you can add account based licensing to the source before you compile. This lets you sell per account or offer reseller packs. It is more advanced, but it is how most commercial EA vendors protect their products.
Source to build on
Our premium source code catalog and free library both ship editable source with clear licensing, so you know exactly what you are allowed to do before you build a product on top of it.