The execution layer
TradingView doesn't have.
PineX watches your Pine Strategy in real time and executes the trade in TradingView Desktop the moment a signal hits. Your connected broker places a real order. ~30 ms latency on Premium and above. No webhooks.
Welcome aboard.
PineX is in private beta, and your feedback shapes what ships next.
If you found your way here, it means you were invited to test, or someone sent it your way out of good faith. Either way, welcome aboard this journey. Your bug reports, feature requests, and "this feels weird" notes are what enable PineX to become a trading staple.
Why PineX exists.
PineX was born out of frustration with TradingView's lack of native automation. Every existing workaround, whether webhook relays, Zapier chains, or third-party broker bridges, is inconsistent, late, and costs a small fortune in monthly subscriptions. Most of them sit on a server somewhere in another country and add hundreds of milliseconds of round-trip latency before your order even hits the broker.
PineX runs locally on your machine. It watches your strategy's order book directly inside TradingView Desktop and routes new entries and exits to your connected broker within ~30 ms of the signal appearing (tested at 100 ms poll rate). No webhook services. No relays. No per-trade fees. Just a subscription at a fraction of the cost to fund development and maintenance.
This project will continue until either TradingView builds their own native automation, or the existing relay services lower their costs and raise their efficiency. Let's change the industry.
Cody and Mateo, out.
PineX vs webhook services.
Same signal. Different paths to your broker. The number of hops is the latency story.
- Pine Strategy prints signal
- PineX executes on TradingView
On Premium and above, expect execution within ~30 ms of the signal. Max ticks at a 1 ms poll rate for the lowest-latency configurations.
- Pine Strategy prints signal
- TradingView creates an alert (can be minutes late under traffic)
- Alert sent to webhook service
- Webhook places trade in broker
Three extra hops, each with its own queue. Best-case sub-second. Worst-case multiple minutes past the bar your strategy actually signaled on.
Sounds too good to be true.
Because it kind of is. Here's what webhook services can do today that PineX cannot — all on the active dev backlog, but worth knowing before you buy.
-
Only TradingView-partnered brokersPineX places orders through TradingView Desktop's native order flow, so it can only execute with the broker TradingView is already connected to. If your broker isn't on TradingView's partner list, webhooks remain the right tool for you.
-
One TradingView tab — multiple panes is OKPineX binds to a single TradingView Desktop tab at a time. Within that tab you can watch up to 4 panes simultaneously (Max tier). Multi-tab trading is in development.
-
Quantity stays where you set it on TradingViewPineX fires the order with whatever quantity is already entered in TradingView's order ticket. Adjust it manually for now — auto-quantity-per-signal is being built.
-
Your computer has to stay onPineX runs locally, which is why Premium and above can hit ~30 ms latency. If your machine sleeps or shuts down, PineX stops watching. VPS support is in development for unattended operation.
Download the beta
Windows 10/11 · macOS (Apple Silicon) · v1.9.0
PineX is in private beta. To download, you'll acknowledge the Terms, Privacy Policy, and Risk Disclosure, then verify your email with a 6-digit code. We use the verified email to reach you if there's a critical update or security advisory — not for marketing.
First-time setup takes about 2 minutes. You'll need TradingView Desktop launched with a debug-mode flag — the in-app Setup tab walks you through it. No additional dev tools required.
We want to hear from you
Bugs, feature requests, weird edge cases, things that just don't make sense in the UI. Send them all. The faster you tell us, the faster they're fixed.
Include: a short description of what you expected vs what happened, any error from the journal, and your PineX version (About tab). Screenshots help a lot.
FAQ
PineX isn't executing my strategy. What do I check?
- TradingView Desktop is running with the debug flag — visit
http://localhost:9222
from your browser. "Connection refused" means TV isn't running with
--remote-debugging-port=9222. Fully quit TV (right-click tray icon → Quit) and relaunch via the shortcut you set up. - Status pill says "Connected" — if it doesn't, click ↻ Reconnect.
- "Execute trades" is ON in Settings → Execution. By default it's OFF so first-time users can journal signals without placing real orders.
- Chart has a Pine Strategy applied, not just an indicator. Strategies expose the order stream PineX reads; indicators don't. Test it: Strategy Tester → List of Trades should be non-empty.
- You haven't switched TV chart tabs while trading. The binding goes stale on tab switch — click Reconnect if you did.
How does PineX work?
Does PineX work with my broker?
Is any of my data sent anywhere?
What's the difference between the tiers?
- Free — 1 chart, 30s poll rate, journal (last 50), desktop notifications.
- Basic ($10/mo) — 1s poll rate, unlimited journal, Discord forwarding, Stats tab.
- Premium ($25/mo) — 100ms poll rate, 2 simultaneous charts, priority support.
- Max ($40/mo) — 1ms poll rate, 4 simultaneous charts, advanced analytics, API access (coming soon).