chartping

Features

Everything Chartping watches — and how it tells you.

Chartping watches the risk rules that matter and warns you as you approach them — read-only, across every MT4/MT5 terminal and exchange account you run. It watches and warns; it never touches a trade.

Works withMetaTrader 4MetaTrader 5BinanceBybitDeribitOKXKrakenKuCoinBitgetCoinbase InternationalGate.ioOANDAAlpacaTradierHyperliquidcTrader · soon

At a glance

What it is
Read-only trading-account monitoring & early-warning alerts
Platforms
MetaTrader 4 & 5 (local agent) · 13 exchanges & brokers via read-only API key (Binance, Bybit, Deribit, OKX, Kraken, KuCoin, Bitget, Coinbase International, Gate.io, OANDA, Alpaca, Tradier, Hyperliquid) · cTrader (soon)
Access level
Read-only by design: Chartping has no order-placement and no withdrawal code path, and never asks for a broker password. Where an exchange lets us verify key permissions we reject write-capable keys; where it doesn't, we flag the connection and you supply a read-only key
Rules monitored
Daily loss %, drawdown-from-peak %, margin level % and an absolute equity floor — each with an early-warning threshold, on MetaTrader and exchange accounts alike. Exchange accounts add three further controls: leverage, margin usage and concentration (Pro)
Alert channels
Mobile push · desktop (tray, toast, sound) · SMS · voice call · signed webhooks (Discord, Telegram, Slack, custom) · in-app live feed
Apps
Web dashboard · iOS & Android app · Windows agent for MetaTrader
Delivery
Snapshot-based, best-effort — with a fail-loud “monitoring stopped” alert if your terminal, agent or connection stops. We can't alert you to an outage of Chartping itself
Price
Free plan available · Pro $29.99/mo · Elite $79.99/mo

Read-only MT4 & MT5 monitoring

A lightweight agent runs on your machine or VPS and reads your account state through your terminal — no DLLs, no sockets, nothing that places or modifies a trade. Because it never injects anything into the terminal, it stays clear of broker and prop-firm restrictions on automation.

Exchange & broker connections

Thirteen exchanges and brokers — Binance, Bybit, OKX, Kraken, KuCoin, Bitget, Deribit, Coinbase International, Gate.io, Hyperliquid, OANDA, Alpaca and Tradier — connect with a read-only API key (cTrader coming soon). On exchanges that let us prove key scope (Binance, Bybit, Deribit) a trade- or withdrawal-capable key is rejected at connect; where scope can't be proven (OKX, Kraken and the others) the key is accepted but hard-flagged. Either way Chartping exposes no order or withdrawal path — broker tokens (OANDA, Alpaca, Tradier) are used strictly read-only, never calling an order or withdrawal endpoint, and Hyperliquid is watched from a public wallet address with no key at all. Keys are encrypted at rest (AES-GCM), and on the exchanges we can verify, a key that later gains write rights stops the connection and alerts you.

A rule engine you control

Model the limits that matter: maximum daily loss, drawdown-from-peak, margin level and an absolute equity floor — each with an early-warning threshold and a per-account override, on MetaTrader and exchange accounts alike. Exchange accounts add three further controls — leverage, margin usage and concentration. Presets ship disabled: you review and confirm every value. Chartping never suggests a strategy or a number.

Early-warning thresholds, not just breach alerts

Set a heads-up level (say 80% of your daily loss) and get a calm, early warning while there's still time to act — then a critical alert if a limit is actually reached. You decide what to do; Chartping only tells you where you stand.

Alerts on every channel you use

Mobile push (iOS & Android), desktop notifications — tray status, Windows toast, sound — SMS, and a voice call for critical breaches, plus a live in-app feed. Route severities per channel and set quiet hours; critical alerts are never suppressed.

Critical alerts re-notify

A critical breach doesn't fire once and vanish: while the alert is still fresh, Chartping re-notifies a limited number of times if nobody has acknowledged it, then stops. An unacknowledged alert is treated as still-unhandled, never as done.

Signed webhooks to anywhere

POST any alarm to any URL — a Discord, Telegram or Slack incoming webhook, or your own backend — signed with HMAC-SHA256 (an X-Chartping-Signature header) and retried on failure. A URL-POST you control, so alerts route into whatever you already use.

Every account in one calm panel — web & mobile

Watch equity, drawdown-from-peak, today's P/L and open positions across all your accounts — MetaTrader terminals and exchange connections side by side, each with a nickname and its own rule set — in the web dashboard and the mobile app.

“Monitoring stopped” fail-loud alert

If your terminal closes, your machine sleeps or the connection drops, Chartping sends a critical alert — and a “monitoring resumed” notice when coverage returns. Being blind to your risk is as dangerous as a breach, so silence is never treated as “all clear.”

For EA developers: SDK and licensing

Any MQL EA or indicator emits a log or alarm in one line with the read-only Chartping SDK — “Powered by Chartping”. Selling an EA? License it through Chartping: issue, meter and revoke licenses, mint redeemable keys, and get HMAC-signed lifecycle webhooks to your own backend.

What Chartping does not do

It does not place, modify or close orders. It does not give advice or generate signals. It does not have withdrawal access or hold your funds. Chartping is a read-only monitoring and alerting tool — every decision and every trade stays yours.

Curious about the setup? See how it works in three steps or read the straight-answer FAQ.

Put your accounts under watch.

Join the waitlist — be among the first to know what's happening across every account you trade.

No spam. We'll email you when early access opens. Read-only · we can't touch your funds. By joining you agree to our Terms and Privacy Policy.