Once Upon a Pine

Once upon a time, in the depths of the Forest of Bits, during the Age of Code, there lived a language. A secret, yet magical tongue, which could only be summoned from a single tower. There, the arcane coders forged their patterns, conjuring the spirits of price and time — and every spark born of this language was bound to that place. But one day…

A wandering coder spoke: “Why should this language remain in chains?” He spoke not out of mercy, nor out of rage. But because he knew — the time had come. Thus began the change. At the dawn of a new cycle, the thought took form: a system that would set the power of Pine free. No longer merely visible. No longer just interpretable. But executable. Anywhere. In any way. And even beyond.

This is Pyne. This is PyneSys. And the story… has only just begun.

About PyneSys

(We work in Pine Script, not just on it. Even our logo was plotted in Pine, not drawn in a design tool or by an AI.)

Pine Script is a good language for writing indicators and strategies. For years you could only write and run it on TradingView. We built PyneSys so you can also develop and run your Pine scripts on your own computer, in Python, and take them anywhere Python runs.

It started with a compiler that turns Pine Script into readable Python and a runtime that runs that Python the way Pine runs. Then we built PyneIDE, so you can write, run and debug Pine Script and Pyne code in VS Code.

We aren’t trying to replace TradingView. It’s still where most people chart, write and share Pine Script. PyneSys gives your scripts a second home that you control.

The three parts

PyneIDE

The development environment: a free extension for VS Code, open source under GPL-3.0. It checks Pine Script and Pyne code as you type, runs your scripts on a live chart, and lets you step through them bar by bar in a debugger. Your scripts run on your own machine. See PyneIDE.

PyneComp™

The compiler. It translates Pine Script v4, v5 and v6 into Python. It is a classical compiler with no LLM in it, so the same script always gives the same output. It’s closed source. You can use it from PyneIDE, the command line or the API with a subscription, and you can try it on 3 scripts for free with our Discord bot. More about the compiler.

PyneCore™

The runtime. It is open source under Apache 2.0, needs Python 3.11 or newer, and has no required dependencies. It runs Pyne code bar by bar, the same way TradingView runs Pine.

Pyne code is the Python that PyneCore runs. You can write it by hand without the compiler, and running it is free. You only need a subscription to compile Pine Script.

How we check our results

A compiled script is only useful if it gives the same results as on TradingView. We check that in two places.

Our test suite runs scripts through PyneCore and compares every output with reference data from TradingView.

Pyne in the Wild does the same in public, at a larger scale. We take a thousand popular open-source scripts from TradingView, compile them, run them, and compare every plot and every trade with TradingView. The report shows how many compiled, how many matched, and which ones didn’t.

What we promise, and what we don’t

We promise:

• The compiler is deterministic. It never uses an LLM to write your code.
• We test our results against TradingView and publish the comparison.
• The Python output is readable, so you can change it yourself.
• We fix bugs quickly when you report them on Discord or GitHub.

We don’t promise:

• That every Pine script compiles and matches on the first try. Pyne in the Wild covers popular public scripts, and yours may use something we haven’t handled yet.
• That we match every TradingView edge case right away. Some of them need changes in the runtime first.
• That the compiler API is up 100% of the time. Pyne code doesn’t need it, because it runs on your machine.

If something is missing or broken, you can patch PyneCore yourself, since it’s open source, or tell us and we’ll fix it. The compiled Python stays yours either way, so you aren’t locked in.

The privacy policy describes what happens to the code you send to the compiler.

Where to find us

• Discord : help, bug reports and the community
• GitHub Discussions : longer technical threads
• Open-source repositories
• YouTube : our videos, including Trading Myth Busting, where we test trading claims with code and data
• X : news and releases
• Contact us for anything else

PyneCore™ and PyneComp™ are trademarks of PYNESYS LLC.