MNQ +0.42% MES +0.21% CL -0.88% GC +0.15% NQ +0.44% ES +0.19% RTY -0.12% PIPRAID EXECUTION ENGINE // SIGNAL → FIRE → FILLED
TRADINGVIEW → TRADOVATE // MULTI-ACCOUNT EXECUTION

One signal.
Every account.
Zero hesitation.

PipRaid takes your TradingView alerts and fires them across all of your prop accounts simultaneously — with a hard-coded risk engine standing between your strategy and a blown evaluation.

DEMO DATA
—
Accounts wired
—
Orders today
<1s
Signal → order
—
Engine uptime
TRADINGVIEW→WEBHOOK API→AUTH + DEDUPE→ RISK ENGINE→EXECUTION FAN-OUT→TRADOVATE API→N ACCOUNTS

Webhook ingestion

A single authenticated endpoint receives your TradingView alerts. Bad secret, malformed payload, or duplicate fire — rejected before it touches an account.

Multi-account fan-out

One signal executes across every enabled account in parallel. One account erroring never blocks the rest of the raid.

Risk engine

Daily loss limit, max position size, max trades per day, trading-hours window. Breach the loss limit and PipRaid flattens everything and halts — automatically.

Watchdog

A 30-second heartbeat re-authenticates dropped sessions, polls PnL on every account, and keeps the kill-switch armed while you sleep.

Encrypted credentials

Account passwords are AES-256-GCM encrypted at rest with a key that only lives on your server. Nothing leaves your box.

Self-hosted

Runs on your own VPS. No middleman servers, no shared infrastructure, no one else's downtime.

Manual execution

  • Open every account, every session
  • Copy each order by hand, one at a time
  • Miss a fill when you step away
  • Risk limits enforced by willpower
  • One bad night undoes an evaluation

PipRaid execution

  • One TradingView alert drives everything
  • Parallel fills across every account
  • Server-side risk checks on each signal
  • Automatic flatten + halt at your loss limit
  • Watchdog re-connects while you sleep
SELF-HOSTEDAES-256 ENCRYPTIONSERVER-SIDE RISK LIMITS ZERO CLOUD CREDENTIAL STORAGETRADOVATE COMPATIBLETRADINGVIEW COMPATIBLE

Dashboard access

Enter the DASHBOARD_TOKEN from your server's .env file. The preview below shows sample data until you connect.

HALTED
Realized today (all accounts)
—
Open PnL
—
Trades today
—
Loss limit headroom
—

System status

SAMPLE DATA

Accounts

SAMPLE DATA
NameLoginStatusBalanceRealizedOpen PnL

Signal tape

SAMPLE DATA watchdog: —
APEX COMMAND CENTER

Portfolio Overview

Every account. Every metric. One screen.

—
Total Accounts
—
Active
—
Total Balance
—
Today's P&L
—
Trades Today

Event Timeline

Connect and configure accounts to see your trading timeline.

Daily P&L by Account

AccountTypeBalanceToday P&LDrawdownWin DaysPayoutsHealth
SYSTEM SETUP

From zero to live execution

Five steps. Run everything in demo first — always.

STEP 01 — INSTALL

Install & start the engine

On your VPS, from the pipraid folder:

npm install cp .env.example .env nano .env # fill in every value — see steps 2–3 npm run start
STEP 02 — SECRETS

Generate your keys

Three values in .env must be generated, never invented:

openssl rand -hex 24 # → WEBHOOK_SECRET openssl rand -hex 12 # → DASHBOARD_TOKEN openssl rand -hex 32 # → MASTER_KEY (encrypts account passwords)
STEP 03 — TRADOVATE API

Add your API credentials

In Tradovate: Application Settings → API Access. Create an API key and copy the CID + secret into TRADOVATE_CID and TRADOVATE_SECRET. Keep TRADOVATE_ENV=demo until every test below passes.

STEP 04 — ACCOUNTS

Wire your prop accounts

Open the Dashboard tab, connect with your DASHBOARD_TOKEN, and add each account's Tradovate login. Passwords are encrypted with your MASTER_KEY before they touch disk.

STEP 05 — TRADINGVIEW

Point your alerts at the engine

In your TradingView alert, set the webhook URL to your server and paste this as the message:

{ "secret": "YOUR_WEBHOOK_SECRET", "symbol": "{{ticker}}", "action": "{{strategy.order.action}}", "quantity": {{strategy.order.contracts}} }

Webhook URL: http://YOUR_SERVER_IP:8722/webhook/fire

Test it by hand before letting TradingView drive:

curl -X POST http://localhost:8722/webhook/fire \ -H "Content-Type: application/json" \ -d '{"secret":"YOUR_WEBHOOK_SECRET","symbol":"MNQZ6","action":"BUY","quantity":1}'
RISK ENGINE

The part that keeps your evals alive

Limits are enforced server-side from .env — the dashboard shows the live values; changing them means editing .env and restarting, so nobody fat-fingers a limit at 2am.

Daily loss limit
—
Max position size
—
Max trades / day
—
Trading hours (UTC)
—
Before going live: confirm your prop firm's policy on automated execution and copy-trading across accounts — some firms restrict or ban it, and violations can forfeit funded accounts. PipRaid is a tool, not financial advice; you are responsible for compliance and for all trading outcomes. Run in demo until the loss-limit trip has been tested.
PRICING

Own your execution stack

One-time license. Self-hosted. Your keys, your box, your edge.

Solo

For individual traders running one evaluation.
$297
one-time
  • 1 prop account
  • Webhook engine + risk engine
  • Watchdog auto-recovery
  • Setup guide + updates
MOST RAIDED

Raider

For prop traders juggling multiple evaluations.
$497
one-time
  • Up to 10 prop accounts
  • Everything in Solo
  • Multi-account fan-out
  • Priority support

Syndicate

For trading groups and resellers.
$997
one-time
  • Unlimited accounts
  • Everything in Raider
  • White-label rights
  • Resell under your brand
QUESTIONS, ANSWERED
Does one alert really fire on every account?
Yes. A single TradingView webhook is validated once, passed through the risk engine once, then executed in parallel on every enabled account. An error on one account never blocks the others.
Is this cloud hosted? Who holds my credentials?
You do. PipRaid runs on your own VPS. Account passwords are AES-256-GCM encrypted with a master key that exists only on your server. Nothing is stored on anyone else's infrastructure.
What happens if my VPS or a session drops mid-day?
The watchdog heartbeat re-authenticates dropped sessions automatically, and the engine runs as a system service that restarts itself and survives reboots.
Can I set hard daily loss limits?
Yes — a daily loss limit, max position size, max trades per day, and a trading-hours window are enforced server-side. Hitting the loss limit flattens every open position and halts the engine until you resume it.
Do prop firms allow this?
Policies differ by firm — many allow your own automation, and most restrict copy-trading across accounts or cap total allocation per strategy. Confirm your firm's written policy before running one strategy on multiple accounts. PipRaid gives you the controls; compliance is on you.
Which platforms does it work with?
Signals come from TradingView alerts (paid plan required for webhooks). Execution targets the Tradovate API used by major futures prop firms. Additional execution adapters are on the roadmap.