What I can build
- TradingView Pine Script (v6): indicators, strategies you can run in the Strategy Tester, and alerts, including webhook messages if you send alerts to another tool (webhook alerts need a paid TradingView plan and two-factor authentication).
- MetaTrader 5: Expert Advisors (EAs) and indicators in MQL5, tested in MT5's Strategy Tester before you get them.
- cTrader: cBots and indicators in C# for cTrader Algo (formerly cTrader Automate).
- Conversions: a TradingView indicator turned into an MT5 EA or a cTrader cBot, or the other way round, as long as its logic can be written as exact rules. I only convert scripts you wrote or have the author's permission to use.
- Changes to a script you already have: alerts, session times, a lot size worked out from your risk, a daily loss limit, a break-even stop, or a fix for something that doesn't behave as it should.
To see the kind of code you'd get, open any of the 35 free Pine Scripts on our trading strategy pages. Each one is written from its page's rules.
How to describe your strategy
The clearer the rules, the more accurate the price and the fewer surprises later. A script can only do what's written down, so cover these:
- Entry: what has to happen, on which candle, for a buy or a sell.
- Exit: where the stop loss and take profit go, and whether the stop moves.
- Size: a fixed lot size, or a % of the account risked per trade.
- Instrument and timeframe: for example XAUUSD on the 5-minute chart.
- Filters: sessions, days or news times to skip, and a maximum number of trades a day.
- Open trades: one at a time or several, and what happens at the end of the day.
A good example of rules written this way: "Buy when a 15-minute candle closes with the 9 EMA above the 21 EMA after being below it on the previous candle, and the close is above the 200 EMA. Stop below the lowest low of the last 5 candles, target twice the stop distance, risk 1% of the account per trade, one trade at a time." Our 9 and 21 EMA crossover and opening range breakout pages show full rule sets.
What I don't build
- "Guaranteed profit" bots. No script can promise profits, and a good backtest isn't a promise either.
- Tools that get around a broker's or prop firm's rules, such as latency arbitrage, or copying or hedging trades across accounts where the firm bans it.
- Bots that place orders for you through an Indian broker's API (Zerodha, Dhan and others). Under SEBI's retail algo rules, an algo supplied by someone else has to come through an exchange-empanelled algo provider working with your broker.
- Signals or tips. I code the rules you give me; I don't tell you what to trade. PipLedger doesn't give investment advice.
Before you run an EA or bot
- Test it on a demo account first. A backtest uses past prices, and live trading adds spreads, slippage and gaps the test may not show.
- Prop firm accounts: many firms limit EAs, for example by banning high-frequency or arbitrage trading, restricting third-party EAs that many traders run, or allowing no EAs on some platforms or account sizes. Check your firm's rules before you order, and name the firm in the form. Our prop firm comparison summarises each firm's main rules; always check the firm's own help centre before you buy.
- Trading from India: Indian residents may trade currency derivatives only on NSE, BSE or MSE through a SEBI-registered broker. Trading forex, or CFDs on gold, indices and other markets, with overseas brokers isn't allowed under FEMA, and using an EA doesn't change that. See forex trading in India.
- Auto-trading through an Indian broker's API (Zerodha, Dhan and others) falls under SEBI's retail algo rules, which apply at every broker from 1 April 2026: orders must come from a static IP registered with your broker, an algo sending more than 10 orders a second per exchange segment has to be registered with the exchange through the broker, and an algo supplied by someone else has to come through an exchange-empanelled algo provider. That's why I don't build those bots. See algo trading in India.