Eight questions a serious reader asks.

PineForge is independent. PineScript is a trademark of TradingView. We re-implement Pine v6’s documented semantics in C++ and validate outputs against TradingView’s “List of Trades” CSV exports — the same way other third-party engines (PyneCore, PineTS, Quantower) do. We don’t reverse-engineer TradingView’s runtime; we re-implement against the public language spec and reference traces from the chart.

PyneCore translates Pine to Python and runs interpreted. PineForge transpiles to C++ and runs natively. Both validate against TradingView. On the 50-strategy three-engine benchmark checked into the open-source engine repo, PineForge hits the canonical excellent tier on 48/50 strategies vs PyneCore’s 45/50 (see benchmarks/results/summary.md). The three PyneCore-only outliers are concentrated in bracket exits, trailing stops, and partial closes — categories where PyneCore’s broker emulator differs from TV. Full breakdown →

If it’s pure PineScript v6, almost certainly. The codegen covers ~98% of what real strategies use: full strategy.* orders, risk + accessors; full ta.* with 66 stateful indicators; matrix, array, map, UDT; request.security ratio + calendar + lower-TF. Drawing primitives (plot, label.new, bgcolor) compile cleanly but emit no visual output — PineForge is a backtester, not a renderer. See the function-by-function coverage doc.

There isn’t one. pineforge-engine is Apache-2.0, CI runs on Ubuntu + macOS, and every compiled strategy .so exports exactly the 10 C symbols in pineforge/pineforge.h — the stability-pinned surface (append-only within the same PINEFORGE_VERSION_MAJOR, per the README). Public checkouts run 16 ctest binaries on every commit (~81% line coverage of src/ via scripts/coverage.sh). The 158/162 headline is produced on a private maintainer corpus/ submodule (162 TV-linked strategies); anonymous public clones don’t ship those fixtures, so that sweep isn’t what GitHub Actions runs. The closed-source piece is the PineScript-to-C++ transpiler (hosted API at launch). Writing your own transpiler against the runtime is explicitly supported.

For batch backtests, yes — that’s the entire current release. For forward-testing with a streaming feed, not yet (Q3 2026). For live broker execution, not yet (2027). The roadmap is honest; we don’t soft-launch features. If you need live execution today, PyneCore or a TV alert + broker bridge will serve you better. Come back when forward-test ships.

libpineforge.a, the public headers, and the benchmark harness code in pineforge-engine stay Apache-2.0 — you can fork and keep building offline backtests. TradingView-linked fixtures live in private git submodules (corpus/, benchmarks/assets); public clones don’t automatically get them, which is why CI runs ctests, not the full 162-strategy corpus on every PR. Trade output remains plain CSV; your Pine source and your data are yours. Worst case if hosted Studio or the transpiler API goes away: you lose those services, but you can retain a local copy of the runtime plus any transpiler-emitted C++ you already have and relink.

TradingView is excellent at chart-driven discovery and one-click execution. PineForge replaces nothing on the chart side. It runs the strategy you already wrote on TV, on your own data, with the same semantics — just compiled, deterministic, and free of the chart-rendering tax that makes 1,000-bar parameter sweeps painful in the browser. Use TV for prototyping; use PineForge when you need the answer to be reproducible.

2027. The encrypted-distribution + license-server architecture is documented at pineforge-utils/plans/distribution-build-plan.md — threat model, AES-256-GCM payload encryption, Ed25519-signed licenses, machine fingerprint binding, time-bounded subscriptions, 7-phase rollout. Pre-launch waitlist for sellers opens Q4 2026 alongside hosted Studio. Join the waitlist →