At barmenteros FX, our Pine Script developers build custom indicators, strategies and alert scripts for TradingView to your specification, in Pine Script v6. Fixed-price quotes within 48 hours. You own the source code outright.
What You Get
- Pine Script v6 source code delivered as a
.pinefile — paste directly into TradingView’s Pine Editor - Full ownership — no licensing restrictions, no recurring fees, no vendor lock-in
- Alert conditions included and compatible with TradingView webhooks for external execution pipelines
- 30-day bug-fix warranty after delivery — see our warranty terms
- Implementation notes explaining how the script works and how to configure it for your instruments
How It Works
- Specify your logic — describe the indicator rules, visual output, inputs, alert conditions, and any reference scripts you are working from
- Quote within 48 hours — we review the specification and deliver a fixed price. No hourly billing, no surprises
- Build in Pine Script v6 — development with testing across multiple instruments and timeframes before delivery
- Receive source code — you paste the
.pinefile into TradingView’s Pine Editor. It is ready to use on any chart
Who This Is For
Good fit:
- Traders who live on TradingView and need a custom indicator that does not exist in the public library
- Traders migrating from MetaTrader who want to recreate their indicator logic on TradingView for chart analysis
- Anyone who attempted to write Pine Script themselves and hit the limits of Pine Script’s series-based execution model — multi-timeframe lookups, confirmed-bar conditions, or complex alert logic
- Traders who need a strategy script for TradingView’s built-in backtester to validate entry and exit rules
Not the best fit:
- Projects where the primary goal is fully automated live execution — Pine Script cannot place orders directly. See FAQ below
- Projects under $100 — TradingView’s free public indicator library covers most simple single-calculation use cases
What Makes This Different
Repainting is the failure mode to rule out first in Pine Script work — an indicator that shows clean signals on historical bars but changes its output as new bars form in real time. It comes from a request.security() call that uses lookahead=barmerge.lookahead_on without a one-bar offset, or logic evaluated on the open realtime bar without barstate.isconfirmed as a gate. Both issues pass every visual check on a historical chart. They only reveal themselves in live use, when the signals you acted on yesterday no longer match what the chart shows today.
Every indicator and strategy delivered from this service uses confirmed-bar logic by default. When lookahead is intentionally required for a specific use case — for example, historical analysis tools where the bar is never re-evaluated — it is explicitly documented so you know exactly what you have.
Multi-timeframe (MTF) analysis is the other area where Pine Script work frequently breaks in production. A script can make at most 40 unique request.*() calls (64 on TradingView’s Ultimate plan), and the way each higher-timeframe value is requested decides whether it is confirmed or still developing at intraday resolution. The failures show up as stale MTF values, wrong bar counts, or results that change with the chart timeframe — problems that only surface under specific conditions that casual testing misses.
barmenteros FX has built algorithmic trading tools since 2011, primarily for MetaTrader — you can read what clients say on our customer reviews page and meet the team on about us. TradingView’s Pine Script uses a fundamentally different execution model: a script runs once on every bar of the series, left to right, and again on each update of the open realtime bar, with no event-driven callbacks. When MT4 indicators are converted to Pine Script, the calculation logic usually translates directly. Where it gets technical is matching the execution behavior across platforms, and that is the part we test before delivery.
Pricing
Simple indicators — single calculation, basic visual output, up to 3 configurable inputs — start at $150.
Standard indicators with multi-timeframe support, advanced visual formatting, conditional logic across multiple data sources, or alert conditions with webhook compatibility typically range from $200 to $600.
Full strategy development with backtesting configuration, commission and slippage settings, and alert integration for external execution pipelines typically ranges from $400 to $1,200 depending on scope and complexity.
Fixed-price quote within 48 hours. No hourly billing. Source code delivered — you own it outright.
Frequently Asked Questions
How much does a Pine Script developer charge?
Simple custom indicators start at $150. Standard indicators with multi-timeframe logic, alert conditions, or specific visual requirements typically fall between $200 and $600. Full strategies with backtesting configuration and webhook alert integration range from $400 to $1,200 depending on scope.
At barmenteros FX, every project starts with a fixed-price quote based on your specification — delivered within 48 hours. No hourly billing, no retainer, no ongoing fees. If the scope changes after the quote, we agree a new price before any additional work begins.
Can Pine Script strategies be used for live trading?
Not directly. A Pine Script strategy is a simulation: TradingView's broker emulator fills its orders on the chart, and the results appear in the Strategy Report. TradingView's Help Center states that automated strategy trading with a brokerage account is not available, so a strategy cannot send orders to a broker you have connected to TradingView.
To trade a strategy's signals live, the strategy raises an alert on each signal, through alert() calls or order-fill alerts, and a webhook forwards that alert to an external service or a custom handler that places the order through your broker's API. Webhook notifications and alerts on strategies require a paid TradingView plan; the free Basic plan includes neither.
If fully automated live execution is the primary goal, MetaTrader 4 or 5 with an MQL4/MQL5 Expert Advisor is a more direct architecture: the EA runs inside the trading terminal and places its own orders. Both approaches are available through barmenteros FX, depending on what your workflow requires.
What is the difference between a Pine Script indicator and a strategy?
A Pine Script indicator, declared with indicator(), plots information on a chart — lines, histogram bars, labels, background colors — and can raise alerts through alertcondition() or alert(). It has no position sizing, no P&L tracking and no backtesting output.
A strategy, declared with strategy(), adds strategy.entry() and strategy.exit() calls that simulate trades on the chart, and TradingView shows the results in the Strategy Report: an equity curve, drawdown figures, trade-by-trade logs and net profit statistics. Strategies raise alerts through alert() calls and order-fill events; an alertcondition() call compiles in a strategy, but TradingView cannot create an alert from it.
Strategy backtesting is available on every TradingView plan, including the free Basic plan, which shows the basic report metrics. Advanced report metrics, trade exports and Deep Backtesting need a paid plan — worth checking if you want those for the strategy you commission.
How do you prevent repainting in Pine Script?
Repainting happens when a script shows values on historical bars that it could not have shown in real time, or when a signal changes after the bar it appeared on.
The most common cause is a higher-timeframe request. request.security() called with lookahead = barmerge.lookahead_on and no offset returns future data on historical bars. Called with its default settings, it returns the developing higher-timeframe value on realtime bars, which keeps changing until that higher-timeframe bar closes. TradingView's documentation gives the non-repainting form: offset the expression by one bar and turn lookahead on — request.security(syminfo.tickerid, "D", close[1], lookahead = barmerge.lookahead_on).
The second cause is signal logic evaluated on the open realtime bar. Gating signals and alerts on barstate.isconfirmed makes them fire only after the chart bar closes, so what you see live matches what the historical chart shows. A third source is varip: variables declared with it keep their values across the ticks of an open bar, which historical bars cannot reproduce.
We test for all three before delivery. When a script uses realtime-only behavior on purpose, we document it so there is no ambiguity about how it executes.
Can you convert an MT4 or MT5 indicator to TradingView Pine Script?
Yes — for traders who have built or commissioned custom MetaTrader indicators and want to use the same logic on TradingView for chart analysis alongside their MT4/MT5 setup.
The core calculations usually translate directly: exponential moving averages, ATR, standard deviation bands, pivot calculations, custom oscillators. The main technical difference is execution model: MQL uses event-driven callbacks (OnCalculate() fires on each new tick or bar), while Pine Script evaluates top-down on every bar in the series from left to right. For most indicators, this difference is invisible in the output. Edge cases appear when the original MT4 indicator depends on tick-level data (which Pine Script cannot replicate at standard chart resolution) or uses iCustom() to call other indicators as inputs.
Any limitation that affects the conversion — precision loss, tick-data dependency, iCustom chains — is identified in the specification review and noted in the quote before work begins.