trading-matrix-dashboard
A Streamlit dashboard for BTC, ETH, Gold, Silver and Crude Oil with live bid/ask, market direction, a volume-spike radar, support/resistance zones built from volume spikes, Telegram alerts and optional webhook / broker auto-trading.
Not financial advice. The dashboard shows reference levels and signals. It does not place stop-losses or take-profits for you. Always test in Paper mode first.
Install and run
pip install -U trading-matrix-dashboard
trading-matrix
Extra options are passed to Streamlit, for example trading-matrix --server.port 8502.
You can also run python -m trading_matrix.
Where to book a trade
Everything you need to decide when and where to trade is on the first tab, Live Market Matrix.
| What you need | Where to look | What it tells you |
|---|---|---|
| Direction (trade bias) | Market View at the very top | Overall direction plus the 15m and 1h direction. Trade with the bias, or be extra careful against it. |
| Entry trigger | Strategy Signal box, Telegram BUY / SELL alerts, webhook action |
Support bounce, trendline breakout or resistance rejection, confirmed by the 10-candle delta. |
| Price area to watch | Banner under Market View and the Spike Zone Tracker table (Range column) |
Where large volume traded before. Price near or inside a zone is where a reaction or a break is expected. |
| Where it may go next / profit area | 🎯 NEXT TARGET row and the If broken -> next zone column | If the zone in front of price breaks, this is the next volume zone, a common place to book profit or re-evaluate. |
| Confirmation that a zone broke | 💥 BROKEN status, red or green banner, Telegram ZONE BROKEN alert |
Price has moved through the zone. The next zone becomes the target. |
| Levels for the opposite scenario | Volume Spike Radar -> Next move with the Resistance and Support levels |
The nearest seller zone above and buyer zone below, useful for placing your own stop or exit. |
| Execution details | Execution (Webhook / Broker) tab, Trade log | Symbol, lot, price and signal reason for every order or paper order. |
How to read the zone table
- In a BEARISH market the dashboard tracks BUYER (support) zones below price.
- In a BULLISH market it tracks SELLER (resistance) zones above price.
- In a NEUTRAL market it shows the nearest zones on both sides and sends no zone alerts.
| Status | Meaning |
|---|---|
| ⏳ AHEAD | Zone is further away than the near-zone distance. |
| 🎯 NEXT TARGET | The nearest zone price has not reached yet. |
| 🟠 NEAR | Price is within the near-zone distance (sidebar slider, default 0.30%). |
| 🔶 INSIDE | Price is inside the zone range. |
| 💥 BROKEN | Price has gone through the zone (below a buyer zone, or above a seller zone). |
Example (bearish)
Buyer zones were logged at 99.00 - 99.80 and 97.00 - 97.60, and the market is bearish.
- Price at 100.00: status NEAR. Telegram: "PRICE NEAR ZONE ... If it breaks, next zone 97.00 - 97.60".
- Price at 99.40: status INSIDE. This is the area where buyers reacted before, so a bounce or a break can happen here.
- Price at 98.80: status BROKEN. The next zone 97.00 - 97.60 is now the NEXT TARGET, a level where a short trade may be booked or reviewed.
A bullish market works the same way, mirrored: seller zones above price, a break upward, and the next seller zone as the target.
Dashboard sections
- Market View: overall, last 15m and last 1h direction, with the reasons behind each score.
- Live Bid / Ask: bid, ask, mid, spread, order-book share and market direction.
- Volume Spike Radar: spikes above 2X, 3X, 4X or 5X the average of the last 200 candles (dropdown in the sidebar). Red candle =
seller, green candle =buyer. Shows the top 10 and the "Next move" view. - Spike Zone Tracker: support and resistance zones, status and next zone (see above).
- KPIs and chart: support, resistance, trendline, 20 and 50 EMA, spike markers, zone bands, bid/ask lines.
Telegram alerts
Open the Telegram Alerts Config tab, enter the bot token and chat ID, and press the test button. Alerts are sent for: new volume spikes, market direction changes, zone near / inside / broken, volume crash, strategy BUY / SELL signals, and every trade or paper trade. Each alert fires once per change, not on every refresh.
Webhook and broker trading
Open the Execution (Webhook / Broker) tab.
- Choose Webhook, Direct broker API (ccxt) or Both.
- Set the lot size (saved separately for each asset) and the symbol.
- For webhooks, paste the URL and, if needed, a secret (sent as
{secret}and as theX-Webhook-Secretheader). - Keep Paper mode on until you have tested. Paper mode logs what would be sent and sends nothing.
- Press Send test webhook to check your receiver, then switch on Enable Auto-Trade.
Default payload (editable):
{"action": "{action}", "symbol": "{symbol}", "lot": {lot}, "price": {price}, "timeframe": "{timeframe}", "signal": "{signal}", "time": "{time}"}
Placeholders: {action} {symbol} {asset} {lot} {price} {bid} {ask} {timeframe} {signal} {time} {secret}.
Valid JSON is sent as JSON, anything else as plain text. MT5 and Shark Exchange can be reached through a webhook bridge.
Each signal fires once per candle, per side, per mode, and is remembered across restarts.
Files and settings
- Volume-spike log:
~/.trading_matrix/volume_spikes.json - Fired-signal memory:
~/.trading_matrix/executed_signals.json - Change the folder with the environment variable
TRADING_MATRIX_DATA. - Pre-fill the webhook fields with
TRADING_MATRIX_WEBHOOK_URLandTRADING_MATRIX_WEBHOOK_SECRET. - Telegram token, webhook secret and broker keys are kept in the browser session only and are not saved to disk.
Good to know
- Spike scans, zones and alerts only run while the dashboard is open in a browser tab.
- Auto-trade only watches the asset selected in the sidebar.
- Yahoo Finance data (fallback for commodities) can be delayed and may have no bid/ask.
- "Broken" is judged on the live mid price at each refresh, not on a confirmed candle close.
- If the
trading-matrixcommand is not found, runpython3 -m trading_matrixor install withpipx.
Metadata
Release files for trading-matrix-dashboard 2.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| trading_matrix_dashboard-2.0.1.tar.gz | 26.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| trading_matrix_dashboard-2.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 51.9 kB
Release files / trading_matrix_dashboard-2.0.1.tar.gz
| Download URL | trading_matrix_dashboard-2.0.1.tar.gz |
|---|---|
| Size | 26.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4efb204309f37098d67b2f8e462c3f22a405b03886e35c31283a15c1949d2075
|
|
BLAKE2b-256 checksum How to use checksums |
5f38843db01ba86b2ea254424bc07839377907651a2a54c4b4b353d2430e5771
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.14
|
Release files / trading_matrix_dashboard-2.0.1-py3-none-any.whl
| Download URL | trading_matrix_dashboard-2.0.1-py3-none-any.whl |
|---|---|
| Size | 25.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2d0b00463c545f38279ae02675b20d6a6587890cb079abc442e6914e4d7dfed9
|
|
BLAKE2b-256 checksum How to use checksums |
6badadc07705013cec9a6e234fad9a0df60529e692936a07ab610af0ef5d9a3a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.14
|
Security for trading-matrix-dashboard 2.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.