The indicator exists.
Just not on MetaTrader.

The portfolio is on the Products page

Most of what is sold here started as this exact job. AlphaTrend, MOST on RSI, Lorentzian Classification, Bheurekso Pattern — all Pine originals, all running native on MetaTrader now. You can download them on a trial and judge the work before commissioning any.

That matters more than a promise: a port either reproduces the original's signals or it does not, and you can check.

Port, or rewrite from the logic

Two different jobs, and which one you need depends on the script.

A port follows the Pine line by line and reproduces its output, including its quirks. This is what you want when the indicator is already trusted and traded — the goal is the same arrows in the same places.

A rewrite from the logic takes what the script is trying to do and builds it properly for MetaTrader. This is the right call when the Pine version leans on something MQL has no equivalent for, or when the original is slow, repainting, or written in a way that cannot survive tick-by-tick execution.

You are told which one the script needs after it is read, with the reason, before any price is agreed.

Where Pine and MQL genuinely differ

Most of a script ports without incident. These are the parts that do not, and how each is handled:

• Higher-timeframe data (request.security). MetaTrader can do this, but the bar alignment is not automatic and a naive port is off by one bar at every boundary. Handled explicitly, and the alignment choice is documented in the inputs.
• Repainting. Many popular Pine indicators repaint — the signal you see on history is not the signal you would have had live. A port can reproduce that faithfully or fix it, but not silently. You choose, and the choice goes in the documentation so nobody backtests something that cannot be traded.
• Drawing objects. Pine's label and box handling has no direct MQL equivalent; those become chart objects with their own lifecycle. Visually equivalent, structurally different — and it is the reason a port takes longer than reading the script suggests.
• Arrays and matrices. MQL5 handles these comfortably. MQL4 does not, so a script leaning on them gets a restructured MQL4 build rather than a direct translation.
• Built-ins with no counterpart. A handful of Pine functions have to be reimplemented from their definition. That is normal work, not a blocker — but it is where the hours go.

If something in your script cannot be reproduced at all, you hear it before the work starts, not in the delivery note.

What comes back

• An MQL4 build and an MQL5 build, source included — you own it outright.
• Inputs named and grouped the way the Pine original had them, so anyone who used that indicator recognises the settings panel.
• A side-by-side check: the same symbol and period on both platforms, showing the signals line up.
• Alerts wired up — MetaTrader popups, push notifications and email, since Pine's alert model has no direct equivalent.
• A note on anything that had to differ, and why.

What to send

1. The script, or the link to it

   Open-source Pine is ideal. A protected or invite-only script cannot be read, so it would have to be rebuilt from its described behaviour — possible, but a different job with a different price.

2. What you actually use it for

   Which pairs, which timeframe, and which of its signals you trade. A script often has five outputs and you care about one — knowing that keeps the port focused instead of gold-plating parts nobody looks at.

3. A screenshot of it working

   One chart with the indicator on it, on a period you know well. That becomes the reference the finished build is checked against.

A word on licensing

Porting someone else's open-source Pine script for your own use is ordinary. Taking a script written by someone else, porting it, and selling it as your own is not — and that job will not be taken on. If you want to sell the result, it needs to be your script, or one whose licence permits it. Ask if you are not sure; it takes one message to check.