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

PyneSys exists because Pine Script™ deserves to run anywhere — not just inside one platform. It’s a remarkable language for traders and quants, but for years it has been locked to a single environment. That’s the gap we close.

Our compiler (PyneComp™) translates Pine Script™ into clean, readable Python. The output runs on PyneCore™, our open-source runtime that mirrors Pine’s behavior down to the bar-by-bar execution model. The two pieces meet in the middle: a deterministic conversion pipeline on one side, a faithful execution environment on the other.

We’re not trying to replace TradingView. TradingView is where Pine Script™ is best developed, tested, and refined — we respect that. PyneSys is the bridge that takes the work you’ve done there and makes it executable wherever Python runs.

How It Fits Together

• PyneComp — the compiler. Closed-source, accessible through the PyneSys SaaS, API, CLI, and Discord bot. Deterministic, no LLMs.
• PyneCore — the runtime. Open-source under Apache 2.0. Zero external dependencies. Runs on Python 3.11+.
• PyneSys — the platform. Subscriptions, API keys, billing, and the developer tooling around the whole stack.

You can use PyneCore on its own — write Pyne code directly in Python, no compiler needed. Or you can use the full pipeline: write in Pine, convert, run in Python. Both paths are first-class.

What We Promise — and What We Don’t

We try to be precise about what PyneSys is, and what it isn’t.

What we promise:

• Deterministic, classical-compiler conversion — no LLM-based generation
• Numerical parity with TradingView where possible, validated against real reference data
• Readable, hackable Python output you can adapt yourself
• Bugs fixed quickly when reported on Discord or GitHub

What we don’t promise:

• That every Pine Script™ will compile or run on day one — the compiler currently covers more than the runtime can execute
• That we’ll match every TradingView edge case immediately (some require runtime additions over time)
• 100% uptime on the SaaS

When something breaks or is missing, you can usually patch it yourself thanks to the open-source runtime — or wait while we close the gap. Either way, you’re not locked in.

Transparency & Community

• 🛠️ Open-source runtime (PyneCore, Apache 2.0)
• 🔐 Clear privacy policy — we don’t share your code with anyone
• 🧪 Test framework that compares results against TradingView reference data
• 🤝 Community feedback shapes our roadmap

Where to find us

• 💬 Discord — the main place for help, bug reports, and community
• 📝 GitHub Discussions — for longer technical threads
• 🌐 Open-source repositories

PyneSys is not affiliated with TradingView. Pine Script™ is a trademark of TradingView, Inc.
PyneCore™ and PyneComp™ are trademarks of PYNESYS LLC.