Pine Script backtest: 11,800 trades. Not one differs.
7,989 backtests graded, 100.00 % excellent or strong
Tap or drag the chart to read any point.
Source: probe composite-vcp-fvg-active-zones-01, pineforge-corpus d75b4fa, 2025-03-31 to 2026-05-01: CSV files, gallery page.
The chart as a table
| Trade | TradingView, USDT | PineForge, USDT |
|---|---|---|
| 0 | 0.00 | 0.00 |
| 1,470 | 1,080.01 | 1,080.01 |
| 2,953 | 702.71 | 702.71 |
| 4,435 | 2,009.59 | 2,009.59 |
| 5,910 | 1,726.02 | 1,726.02 |
| 7,375 | 1,349.79 | 1,349.79 |
| 8,858 | 883.15 | 883.15 |
| 10,341 | 458.12 | 458.12 |
| 11,800 | 262.81 | 262.81 |
The chart as a table
48 consecutive trades of the same strategy on the 178 Binance ETHUSDT perpetual 15-minute candles around them. TradingView’s export and PineForge’s trade book agree on side, entry and exit time, entry and exit price and net P&L, row for row.
| Trade | Side | Entry, TradingView | Entry, PineForge | Exit, TradingView | Exit, PineForge | Net P&L, TradingView | Net P&L, PineForge |
|---|---|---|---|---|---|---|---|
| 4,100 | long | 4,306.95 | 4,306.95 | 4,296.64 | 4,296.64 | −10.31 | −10.31 |
| 4,106 | long | 4,279.17 | 4,279.17 | 4,276.80 | 4,276.80 | −2.37 | −2.37 |
| 4,112 | long | 4,327.73 | 4,327.73 | 4,315.74 | 4,315.74 | −11.99 | −11.99 |
| 4,118 | long | 4,272.71 | 4,272.71 | 4,242.19 | 4,242.19 | −30.52 | −30.52 |
| 4,124 | long | 4,779.50 | 4,779.50 | 4,760.73 | 4,760.73 | −18.77 | −18.77 |
| 4,129 | long | 4,749.87 | 4,749.87 | 4,738.93 | 4,738.93 | −10.94 | −10.94 |
| 4,135 | long | 4,718.89 | 4,718.89 | 4,731.00 | 4,731.00 | 12.11 | 12.11 |
| 4,141 | long | 4,723.34 | 4,723.34 | 4,718.71 | 4,718.71 | −4.63 | −4.63 |
| 4,147 | long | 4,752.76 | 4,752.76 | 4,745.12 | 4,745.12 | −7.64 | −7.64 |
The chart as a table
Each mark is one strategy script on one market and timeframe; the 84 amber ones graded strong, the other 7,905 excellent.
| Market | Timeframe | Graded | Excellent | Strong |
|---|---|---|---|---|
| ETHUSDT.P | 15-minute | 1,009 | 995 | 14 |
| ETHUSDT.P | Daily | 540 | 538 | 2 |
| BTCUSDT | 15-minute | 668 | 660 | 8 |
| BTCUSDT | Daily | 516 | 515 | 1 |
| ES1! | 15-minute | 76 | 73 | 3 |
| ES1! | Daily | 35 | 34 | 1 |
| NQ1! | 15-minute | 74 | 71 | 3 |
| NQ1! | Daily | 37 | 37 | 0 |
| AAPL | 15-minute | 632 | 625 | 7 |
| AAPL | Daily | 464 | 463 | 1 |
| F | 15-minute | 637 | 622 | 15 |
| F | Daily | 505 | 501 | 4 |
| NIFTY | 15-minute | 314 | 308 | 6 |
| NIFTY | Daily | 225 | 224 | 1 |
| EURUSD | 15-minute | 653 | 645 | 8 |
| EURUSD | Daily | 453 | 452 | 1 |
| XAUUSD | 15-minute | 695 | 688 | 7 |
| XAUUSD | Daily | 456 | 454 | 2 |
The chart as a table
Each mark is one of the 200 strategies timed on both engines, at its exact speed-up on a log scale.
| Rank | Speed-up |
|---|---|
| 1 | 2.5× |
| 26 | 21× |
| 51 | 26.2× |
| 76 | 31.2× |
| 101 | 36× |
| 125 | 47.4× |
| 150 | 55.3× |
| 175 | 71.5× |
| 200 | 1,307× |
How this is measured
100.00 % of 7,989 graded backtests are excellent or strong against TradingView’s own trade lists, and the median run is 36× faster than PyneCore (how we timed it).
Parity baseline 2026-09-29 on engine 35db01c8. Engine v1.0.1, released 2026-10-02, includes it, and the releases changed no grade. Methodology
Probe composite-vcp-fvg-active-zones-01 in pineforge-corpus at commit d75b4fa: Binance ETHUSDT perpetual, 15-minute bars, 2025-03-31 to 2026-05-01. PineForge’s trade list there was written on 2026-10-02 by engine v1.0.1. See the CSV files or open it in the gallery.
How we timed it: PineForge in-process with Google Benchmark, bar magnifier on; PyneCore 6.10.3 as a subprocess, so its wall time includes interpreter start-up. An AWS c7a.8xlarge (AMD EPYC 9R14, 32 cores, SMT off) running Ubuntu 24.04, each timing process pinned to fixed cores; engine 35db01c8, 2026-09-29, one 53,929-bar ETHUSDT 15-minute feed. Engine v1.0.1 was released after it, and the timings were not re-measured on the release. Read the full benchmark.
Run it where your strategy lives
PineForge runs PineScript v6 as native C++: offline, in CI or from your AI agent.
Hosted MCP
claude mcp add --transport http pineforge https://mcp.pineforge.dev/mcpAnother MCP client? See its setup.
Docker
Runs the released engine on your OHLCV file; your data stays local. Offline guide.
docker run --rm --network=none \ -v "$PWD/strategy.pine:/in/strategy.pine:ro" \ -v "$PWD/ohlcv.csv:/in/ohlcv.csv:ro" \ ghcr.io/pineforge-4pass/pineforge-release:1.0.1 > report.jsonSource
Strategy-pool optimization and a hosted Studio are planned. We’ll email you when each one opens.
You get one welcome email now. Reply STOP to any email to unsubscribe.