PineX PineX
PRIVATE BETA

The execution layer
TradingView doesn't have.

PineX watches your Pine Strategy in real time and fires the buy/sell hotkey into TradingView Desktop the moment a signal hits. Your connected broker places a real order. Sub-100 ms latency. No webhooks.

Download the beta Send feedback

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.

FROM THE DEVELOPER

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 talks to TradingView Desktop through the same protocol Chrome's DevTools uses, reads your strategy's order book directly, and fires the broker hotkey 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.

PineX
  1. Pine Strategy prints signal
  2. PineX executes on TradingView

With a paid plan, expect execution within 100 ms. Higher tiers poll faster and shave the delay further (Max ticks at 1 ms).

Other webhook services
  1. Pine Strategy prints signal
  2. TradingView creates an alert (can be minutes late under traffic)
  3. Alert sent to webhook service
  4. 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.

FAQ

PineX isn't executing my strategy. What do I check?
Walk through these in order:
  1. 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.
  2. Status pill says "Connected" — if it doesn't, click ↻ Reconnect.
  3. "Execute trades" is ON in Settings → Execution. By default it's OFF so first-time users can journal signals without firing real orders.
  4. 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.
  5. You haven't switched TV chart tabs while trading. The binding goes stale on tab switch — click Reconnect if you did.
Still stuck? The in-app Setup tab has a longer troubleshooting list. If that doesn't help, email pinex.support@c21eservices.com with a journal screenshot.
How does PineX work, technically?
PineX connects directly to TradingView Desktop using the Chrome DevTools Protocol — the same WebSocket interface a Chrome extension or developer would use to read and control any Chromium-based app. Once TradingView Desktop is launched with the debug port enabled, PineX opens a CDP WebSocket against it, injects a tiny JS snippet to read your strategy's ordersData() array every poll cycle, and detects new entries / exits as they appear. When a new order shows up, PineX dispatches a Shift+B or Shift+S keystroke into the TradingView window — TradingView's own market-order hotkeys — and your connected broker places the trade. No third-party servers, no relays, no per-trade fees.
Does PineX work with my broker?
PineX works with any broker TradingView Desktop is already connected to natively. If you can manually press Shift+B / Shift+S in TradingView Desktop and your broker receives the order, PineX can do the same automatically. Check TradingView's broker integrations page for the full list of supported brokers.
Is any of my data sent anywhere?
No trade data leaves your machine. PineX reads from TradingView Desktop on your computer, processes signals locally, and journals everything locally. The only outbound network traffic from PineX is: (1) subscription / authentication checks against our backend, (2) auto-update checks for new versions, and (3) optional Discord webhook forwarding if you opt in. See the Privacy Policy for the full breakdown.
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).
The poll rate is the upper bound on how fresh your signal can be — at 100ms, PineX checks for new orders ten times per second. Slower polling = higher latency. Pick a tier whose poll rate matches your strategy: HTF / swing strategies are fine on Free; intraday wants Basic+; scalping wants Premium or Max.
Why does TradingView Desktop have to stay open?
PineX reads your strategy state and dispatches keystrokes against the actual TradingView window. If TV isn't running with the debug port open, PineX has nothing to talk to. We considered building against TradingView Web instead — but the web app runs inside your browser's sandbox and doesn't expose the Chrome DevTools Protocol, so it's not a viable channel for the same approach.
How do I cancel my subscription?
In PineX: Account tab → Manage subscription. That opens your Stripe billing portal where you can cancel, change tier, update payment, or download invoices. Cancellation takes effect at the end of the current billing period — no proration.
I have a feature request / bug to report.
Two paths. (1) Inside PineX: when you stop trading you'll get a quick feedback prompt — that lands directly in our triage queue. (2) Email pinex.support@c21eservices.com with a description and a journal screenshot if it's a bug. Beta-tester feedback shapes the next release.

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.

Go to download

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.