Your trades.
Your machine.
Take an AI-assisted Pine Script from a tested alert to MetaTrader 5 on your PC.
Hookmode is the execution layer after your review. It receives the TradingView signal, checks your rules, then asks your paired Windows device to place the MetaTrader 5 trade. No chart EA. No VPS to rent. Your broker password stays on your PC.
- Signal received and 3 rules matched
- Drawdown limit checks pass
- 3 trades dispatched to “Office PC”
- Broker accountFilled+0.2 s$120 / $500
- Funded accountFilled+0.3 s$260 / $500
- Challenge accountFilled+0.2 s$330 / $500
Hookmode is a Windows desktop application that receives TradingView webhook alerts and places the trades in MetaTrader 5 on the trader’s own computer. It is not an Expert Advisor and does not need a VPS.
- TradingView alerts
- any HTTP webhook
- MetaTrader 5
- Windows
Built for
AI-assisted Pine Script users
You used AI to draft a script. Now you need a clear path to review the alert, test it, set limits, and decide when to execute it.
Pine Script and webhook builders
You already have a signal source. Route it to account rules without attaching an Expert Advisor to a chart or renting a VPS.
MetaTrader 5 prop-firm traders
Set a drawdown budget per rule and a daily loss limit per account. Then compare those controls with your firm’s own published rules.
AI writes the Pine. You test the alert.
Treat AI-generated code as a draft, not a trading decision. Hookmode does not build, validate, or improve a strategy. It executes the signal path you configure after your own review.
- 01
Review the script
Understand what the Pine Script can open, close, and override.
- 02
Test the alert
Check the payload and the result in a demo setup where appropriate.
- 03
Set conservative controls
Configure the alert’s stop loss, then choose a risk factor, a position cap, and limits you understand.
- 04
Read the trace
Confirm a fill, block, or failure before you rely on the execution path.
What must be true before a trade can open
- A Windows 10 or 11 PC that stays on and online while you expect trades.
- MetaTrader 5 installed on that PC and logged in to your broker at least once.
- A trading account on MetaTrader 5.
- A signal source: a TradingView plan that supports webhook alerts, or anything that can POST JSON.
- A beta invitation. Join the waitlist if you do not have one yet.
No VPS to rent. The PC is the part that must stay on.
From a tested alert to a traced result on your PC.
Three setup steps. Hookmode receives and checks the signal; your paired Windows device places the MetaTrader 5 trade.
A webhook is a message your alert source sends to a URL when a condition fires. TradingView sends one when an alert triggers.
- 1Once
Install and pair a device
Install the Hookmode desktop app, then pair the Windows device from the web app with a 6-digit code. The code is valid for 10 minutes and can be used once.
4 8 2 9 1 7
Code valid 10 minutes, single use
- 2Per account
Add a trading account
Add the nickname, broker server, and login in the web app. Type the password on the paired device. The desktop app verifies it against MetaTrader 5 and stores it there, encrypted.
You point the app at your MetaTrader 5 install folder once.
Active · verified against MetaTrader 5 · terminal running
- 3Per webhook
Add the alert and rules
Create a webhook, copy its message into TradingView, then add a portfolio rule for each account. Rules set the symbol, the risk factor and the guardrails before a signal reaches the device.
POST api.hookmode.com/api/webhook
Follow the full setup path
Follow the five-step getting-started guide, with separate TradingView and guardrail guides when you need more detail.
Do not guess what happened. Read the trace.
Every signal leaves an ordered record. See whether it was rejected, which rules matched, whether a guardrail blocked a new trade, and what the broker returned.
Illustrative examples. Not trading results.
Opened
- webhook received
- 1 rule matched
- trade dispatched to “Office PC”
- trade opened · EURUSD 0.50 @ 1.08742 · +0.6 s
Daily-loss block
- webhook received
- 2 rules matched
- trade dispatch failed · Challenge account · the account reached its daily loss limit
- trade dispatched to “Office PC”
- trade opened · EURUSD 0.25 @ 1.08744 · +0.5 s
Bad key
- webhook rejected · invalid signature
- A rejected signal names the reason before a trade is sent.
- A blocked trade names the account or rule and the limit it reached.
- A failed trade records the device or broker reason. It is not queued or replayed.
- Broker-side closes are written back with their source.
Limits that block new Hookmode trades before dispatch. Closes still pass.
Set a drawdown budget per rule and a daily loss limit per account. Hookmode checks them before it asks your device to place a new trade.
These limits count only trades placed through Hookmode. Your broker or prop firm may calculate risk differently, so set Hookmode below the limit that matters to you.
Illustrative rule example · hard stop on
$0budget left
- EURUSD Sell 0.50closed−$120
- XAUUSD Buy 0.20closed−$140
- EURUSD Sell 0.50closed−$150
- GBPUSD Buy 0.30closed−$90
- Next signal blocked: rule drawdown
No new trades until you reset it. Closes still pass.
Illustrative account · resets 00:00 server time
$0left today
- EURUSD Buy 0.50opened · stop-loss riskreserves $300
- EURUSD Buy 0.50closed at stop−$300
- XAUUSD Sell 0.20opened · stop-loss riskreserves $700
- Next signal blocked: the account reached its daily loss limit
Blocked while XAUUSD is still open. The limit counts the stop-loss risk of open trades, not only closed losses. No new trades on this account until midnight. Closes still pass. A Telegram alert went out.
- Drawdown limit per rule. The rule’s realized P&L, measured from its best point. You set the drawdown budget on the webhook; each rule scales it by its risk factor. With the hard stop on, a breach blocks new trades until you reset it. Closes still pass.
- Daily loss limit per account. Today’s closed losses plus the stop-loss risk of every open trade, minus today’s profits. When it is reached, no new trade opens on that account until the day resets. It resets at midnight in your broker’s server time, read from your terminal. Closes still pass.
- Every trade is placed with a stop loss. Stop loss and take profit are set per webhook side and placed at the broker. Per-signal overrides only if you allow them.
- Max open positions per rule. Default one. Raise it only on hedging accounts.
- Pause anything. Pause a webhook and its signals are rejected and logged. Pause a rule, a portfolio or an account and signals skip it.
- Trigger or close by hand. From the webhook page, with the same rules applied.
The server handles the signal. Your PC handles the broker login.
Hookmode servers receive, validate, and route the webhook. Your paired Windows device stores the broker password and uses its local MetaTrader 5 terminal to place the trade.
Password on your PC only
You type it on your machine. Windows encrypts it (DPAPI), and the desktop app uses it locally to connect the MetaTrader 5 terminal. Our servers keep the nickname, server and login. Never the password. Protect your Windows sign-in and lock the PC when you leave it.
Outbound only
The desktop app opens a TLS connection to Hookmode. It communicates with the MetaTrader 5 terminal over localhost on the same PC. No port forwarding is needed.
Pair with a code, revoke in a click
A 6-digit code is valid for 10 minutes and can be used once. Every device gets its own token. Unpair it from the web app to revoke its access.
A key per webhook
Every webhook has its own 32-character key, sent in the signature field of the message. A request without a valid key is rejected before an order is sent. Rotate the key at any time. TradingView cannot add custom headers to its requests, so the key sits in the message body, protected in transit by TLS.
Terminal stays local
Hookmode manages one MetaTrader 5 terminal per account. Each terminal uses a per-session token and is reached only by the desktop app on your PC.
Your machine, your IP
Orders are submitted by your own PC and your own MetaTrader 5 terminal. Broker and prop-firm rules differ, so check yours before automating.
Stays on your PC
- broker password (DPAPI)
- device token
- MetaTrader 5 session
- local trade mirror (SQLite)
Shared with the web app
- account nickname, server, login
- balance / equity snapshots
- open positions and floating P&L (every 60 s)
- trades and realized P&L
- signal payloads and trace events
Your PC executes. Your phone tells you when it does not.
Watch signals, trades, blocks, and device status from any browser. If the device is offline when a signal fires, the trade fails and is not queued.
Illustrative notification data. Not trading results.
- 09:31Received EURUSD open signal
- 09:31Opened EURUSD buy trade for 0.50 lots
- 11:04Broker closed EURUSD buy trade
- 13:15Opened XAUUSD sell trade for 0.20 lots
- 14:02Device “Desk PC” went offline
- 14:06Device “Desk PC” is online again
- 15:40Broker closed XAUUSD sell trade
- MonWeekly summary of signals and trades
Problems first
The Home page shows an attention card when a device is offline or an account is blocked. When nothing is wrong, it stays out of the way.
Review each account
Review balance and equity snapshots, open positions, trade history, and the rules that produced each result.
Alerts you choose
Receive Telegram and in-app alerts for signals, trades, failures, device changes, and risk blocks. Choose the Telegram events per chat.
Features
Webhook control
One URL and one rotatable key per webhook. TradingView, a bot, or anything that can POST JSON can send a signal.
One signal, many account rules
Add a rule per account with its own symbol and risk factor. One close signal closes the matching stack.
Guardrail visibility
A drawdown or daily-loss block is visible in the trace and can send a Telegram alert.
Broker closes written back
A stop loss, take profit, manual terminal close, or stop-out is detected and recorded with the broker result.
Runs in the background
The desktop app manages a MetaTrader 5 terminal per account while the device is powered, online, and connected.
Manual actions
Trigger a buy or sell, or close a side, from the webhook page. The trace marks it as manual.
What Hookmode does not pretend to be
- Not a strategy builder or signal provider. You bring the alert and decide whether it is ready.
- Not an Expert Advisor attached to a chart. The desktop app works with the MetaTrader 5 terminal on your device.
- Not a copy-trading service. Hookmode never holds your broker password and nobody else’s trades run on your account.
- Not an always-on cloud bot. If your device is offline, the trade fails. Nothing is queued or replayed.
- Not a prop-firm approval or a replacement for the firm’s own rules.
- Not multi-platform yet. MetaTrader 5 on Windows today.
FAQ
Bring a tested alert to a PC you control.
Hookmode is for traders with Windows, MetaTrader 5, and a webhook source who want a clear, traceable execution path. Join the waitlist and we will email when an invitation is available.
Private beta. We will email you when an invitation is available.