Local API console

Fresh Binance Automation Dashboard

Checking server
Live trading is locked. Demo/Testnet order execution is controlled by the dashboard switch. Live is used only for public chart, price, and volume data.

Operating manual

Dashboard Instructions

Use this page as the main checklist before you scan alerts or prepare demo trade automation.

Start here

Visual workflow

From Connection To Demo Trade Gate

Follow left to right
Phase 1 Foundation
01

Connect APIs

Demo/Testnet for safe account testing. Live for public market data only.

02

Load Market And Chart Data

Fetch symbols, load candles, and confirm Binance data is visible.

Phase 2 Signal Design
03

Upload Indicator

Add the dashboard indicator package and review its settings.

04

Create Alert Rules

Choose indicator alert names and define BUY/SELL alert intent.

Phase 3 Scanner Preparation
05

Build Daily Plan And Universe

Save time window, selected rules, volume filter, and scanner symbols.

06

Check Candle Readiness

Backfill missing candle history before scanning any selected symbols.

Phase 4 Execution Review
07

Run Scanner Once

Test background scanning manually before enabling scheduled runs.

08

Review Triggered Alerts

Filter today, current session, symbols, timeframes, and source.

Phase 5 Demo Trade Safety Gate
09

Prepare Trade Automation Rules

Only after alerts look correct, define demo-only limits, SL/TP policy, and duplicate controls. No live trading.

Icon-style workflow visuals are embedded SVGs based on free/open SVG icon patterns, so the dashboard works offline locally and on the VPS.

Required first

Before Any Scanner Test

  1. Open Binance API Connection and connect Demo/Testnet plus Live Market Data.
  2. Open Indicator Upload and confirm the indicator package is listed.
  3. Open Chart Data Storage, load the symbol/timeframe, and apply the indicator once.
  4. Open Alert Rules and create the alert rules that the scanner should watch.

Daily scanner

Before Daily Scanner

  1. Save Daily Scanner Plan with data source, time window, timeframes, and alert rules.
  2. Build Symbol Universe so the scanner knows which symbols are selected.
  3. Check Candle Readiness and backfill missing candles.
  4. Use Run Once Now first. Keep Start Daily Scanner disabled until you are ready for repeated scanning.

Alerts

After Scanner Runs

  1. Open Triggered Alerts and choose Today only or After daily scan start.
  2. Use Source = Background scanner to see only automatic scanner results.
  3. Use Alert Review only for marking or deleting local test alerts.

Trading safety

Before Demo Orders

  1. Create Trade Automation Rules only after alert results look correct.
  2. Set limits such as max trades/day, max open trades, and SL/TP policy.
  3. Live trading remains locked. Demo/Testnet orders can run only when the demo switch and safety gates allow them.

Page By Page Checklist

Binance API Connection
Connect Demo/Testnet for safe testing. Connect Live Market Data for public charts, price, and volume. Save credentials once, then use saved credentials later.
Live Futures Market Data
Fetch symbols, search a symbol, then refresh price, funding, volume, and change data.
Chart Data Storage
Fetch symbols, load chart, download historical candles, choose live/closed candle display, and apply indicators with settings.
Chart Live Data Verification
Compare live Binance REST Last Price candles against live WebSocket candles using separate symbol, timeframe, and candle-mode controls.
Indicator Upload
Upload dashboard indicator packages, inspect files, delete old packages, and confirm indicator settings are available.
Alert Rules
Select an indicator, choose an alert name, confirm BUY/SELL event, and save the rule that the scanner should watch.
Manual Scan
Test one symbol/timeframe against saved candles and alert rules before using the daily scanner.
Daily Scanner Plan
Save the daily time window, timezone, volume threshold, symbol limit, timeframes, and alert rules. Use Run Once Now for testing.
Symbol Universe
Build selected symbols from Binance 24h quote volume. Search selected/rejected symbols to confirm the list.
Candle Readiness
Check whether each selected symbol/timeframe has enough candles. Backfill missing history before scanning.
Triggered Alerts
View fired alerts. Filter by today, previous day, current scanner session, symbol, timeframe, source, and indicator.
Trade Automation Rules
Prepare demo-only trade permission rules, review decisions, and send Demo/Testnet orders when the safety gates allow them.
Safety
Set the global demo automation pause, maintenance mode, SL/TP requirement, same-symbol protection, and emergency action permissions.
Detailed Analysis
Review dashboard-native alert, decision, trade rule, lifecycle, and protection outcomes before changing automation rules.
Database Cleanup
Preview local test-data cleanup before deleting candles, old alerts, old decisions, audit logs, snapshots, or uploaded indicator packages.
Audit Logs
Review credential, rule, alert, decision, and demo order actions recorded by the dashboard.
Alert Review
Review, ignore, delete, or clear local test alerts.
VPS Readiness
Check app, PostgreSQL, and Redis readiness before migration to Hostinger VPS.

Connection setup

Binance API Connection

Simulated funds

Demo / Testnet

Not connected
Checking saved credentials...
Ready.

Public market data

Live Data

Not connected
Checking saved credentials...
Ready.

Current day connection health

API Connection Attempts And Sessions

Daily counts are calculated from local audit records for today in IST. Errors are shown here so repeated connection issues are easy to trace.

Not loaded
Manual refresh only
Demo attempts today--
Demo success / failed--
Demo sessions started--
Live attempts today--
Live success / failed--
Live sessions started--
Demo session active--
Demo session started--
Live session active--
Live session started--
Connection stats not loaded yet.
Connection Error History--

Help

What Each Field And Button Does

Demo / Testnet Card

API key and API secret are your Binance Futures Testnet credentials. Use this account for automation testing and demo trades only.

Test Demo Signed Key reads the Demo/Testnet Futures account once. Diagnose Demo Signed Key checks public Demo Futures plus signed Demo Futures account read.

Connect Demo Futures Testnet API verifies the signed demo account connection and shows demo account status. If saved credentials exist, you can leave the key fields blank.

Live Data Card

Live Futures Market Data URL reads public Binance Futures data for charts, price, and 24h volume. This does not need live Futures trading permission.

Test Live Data checks the public live Futures endpoint. Connect Live Futures Market Data API connects to Binance live public market data only. It does not place trades.

Common Buttons

Test Demo Public API and Test Live Data check whether Binance public data is reachable. Save stores credentials locally in this project. Use Saved uses saved credentials. Clear Saved removes them. Disconnect clears the current connection status.

Daily Stats

API Connection Attempts And Sessions shows today's attempt count, success/failure count, active session time, session start time, and recent errors from local audit logs.

Live futures market data

Market Watch

Auto refresh off
Click Fetch Symbols to load all active Binance Futures symbols into the dropdown.
Mark price --
Index price --
24h volume --
24h change --
Funding time --
24h trades --
Server time --
Last refresh --

Ranked by 24h quote volume

Top Live Futures Symbols

Top symbols are selected by highest Binance USD-M Futures 24h quote volume. Sorting changes the table view only; it does not change which symbols qualify for Top 10, 20, 50, or 100.

Not loaded
Manual refresh only

Click Refresh List to load ranked live futures symbols.

Stored candles

Chart Data Storage

No chart data loaded
Click Fetch Symbols to load active Binance Futures symbols for the chart dropdown.
Load Chart checks local storage first. If candles are missing, it downloads Binance REST history, stores it locally, then starts chart display.
Auto live socket is on. Load Chart starts Binance WebSocket updates for the current candle.
Move over a candle to see OHLC values.
Stored candles --
First candle --
Latest candle --
Last saved --

Uploaded indicator

Apply Indicator To Chart

No indicator applied
Select one uploaded dashboard indicator to view and edit settings.
Upload an indicator, load chart candles, then apply it here.
BTCUSDT PERP 1m Primary

Chart guide

How To Use This Chart Page

1. Pick Symbol

Click Fetch Symbols, search the symbol, and select it from the dropdown.

2. Match Binance Chart

Price source must match the Binance chart setting. Use Last Price for normal trade candles, Mark Price for mark candles, or Index Price for index candles.

3. Download Candles

Historical candles to download controls how many REST candles are saved. Binance allows up to 1000 per request.

4. Show Candles

Candles to show on chart controls how many stored candles are drawn. Use fewer candles for a cleaner view.

5. Live Updates

Auto live socket starts Binance live updates after Load Chart. REST loads history first, then WebSocket keeps the current candle moving. A REST fallback runs only as backup.

6. Verify Live Data

Use the separate Chart Live Data Verification page when you want to compare Binance REST candles against live socket candles.

Chart live data verification

REST vs Live Socket Comparison

Use this page when Binance website candles and dashboard candles look different. Keep Binance website on the same symbol, timeframe, and Last Price mode.

Not running
Click Fetch Symbols to load active live Binance Futures symbols for verification.
REST Last Price
Waiting
Live Socket Last Price
Waiting
REST latest candle --
Socket latest candle --
Close difference --
Open time match --
This page compares Binance REST Last Price candles against Binance live kline WebSocket candles. Use Closed candles only when you want to ignore the current moving candle.

Dashboard indicator library

Indicator Upload

Upload only dashboard-native indicator packages that were already created and reviewed in the converter lab. This page does not convert Pine Script.

Visual review only
01 Package Files

Choose the indicator folder or select `indicator.json`, module file, and README together.

02 Stored Locally

Packages are saved under this dashboard storage folder and ignored by Git.

03 Inspect First

View manifest, README, and dashboard code before applying indicators to chart data.

04 Trading Locked

Uploaded indicators are not allowed to trade until later approval gates are added.

No dashboard indicator uploaded yet.

Delete Indicator

Inspect Indicator

Select an uploaded indicator and inspect its files before applying it on the chart.

Indicator Search Results--

Automation setup

Alert Rules

Create named alert definitions. These rules will later drive background scanning and demo trade decisions.

No rules loaded
This does not place an order. It only allows matching triggered alerts to be considered later by Trade Automation Rules and Safety settings.

Optional live-cross mode

Optional Live Candle Cross Settings

Saved with rule

Use Not applicable when this indicator does not need current live candle crossing. These fields are ignored unless live-cross timing is selected.

Create an alert rule before enabling background scanning.
Saved Alert Rules--

Indicator alert playbook

Hammer Maranatha153nz Alert Guide

Use this guide when Hammer Maranatha153nz alerts need both candle-close confirmation and live candle high/low crossing checks.

Guide only

Visual workflow

From Hammer Setup To Demo Trade Decision

Follow in order
Step 1 Upload
01

Upload Indicator

Upload Hammer Maranatha153nz, inspect the manifest, and confirm available alert names and settings.

Step 2 Rules
02

Create Alert Rules

Create separate rules for hammer pattern, hammer BUY entry, live cross above high, and live cross below low when needed.

Step 3 Scanner
03

Choose Timing

Use candle-close mode for confirmed hammer candles. Use live-cross mode when price must trigger before the candle closes.

Step 4 Trade Gate
04

Evaluate Safely

Triggered alerts go to Trade Automation Rules first. Demo orders are sent only when demo switch, safety, SL, TP, and duplicate checks pass.

Mode A

Candle-Close Hammer Alert

Use this when the hammer pattern must be confirmed only after the candle closes.

  1. Upload and inspect Hammer Maranatha153nz.
  2. Create an Alert Rule for the hammer pattern or confirmed BUY event.
  3. Use Manual Scan or Run Once with latest candle testing.
  4. Triggered Alerts should show candle time, symbol, timeframe, side, entry, SL, and TP if provided.
  5. Trade Automation Rules may evaluate it after the alert is created.

Mode B

Live Cross Before Candle Close

Use this when current live price must cross the previous candle high/low or an identified candle level before the candle closes.

  1. First identify and store the reference candle high or low.
  2. Start live monitoring for selected symbols and timeframes.
  3. Trigger BUY when live price crosses above the selected high.
  4. Trigger SELL when live price crosses below the selected low.
  5. Use one duplicate key per symbol, timeframe, alert rule, reference candle, and direction.

Mode C

Live Trigger With Close Confirmation

Use this when you want fast notification, but still want to know whether the candle finally confirmed.

  1. Live cross creates an intrabar alert immediately.
  2. Dashboard marks it as live cross triggered.
  3. When the candle closes, scanner checks whether the hammer rule is still valid.
  4. Status becomes confirmed at close or failed after close.
  5. Trade automation can be configured later to trade immediately or wait for confirmation.

Page By Page Checklist

Indicator Upload
Upload Hammer Maranatha153nz and inspect alert names, inputs, and required candle count.
Chart Data Storage
Load symbol/timeframe, apply Hammer Maranatha153nz, and visually confirm markers before creating automation rules.
Alert Rules
Create separate alert rules for pattern confirmed, BUY entry, SELL entry, previous high cross, and previous low cross when the indicator supports them.
Manual Scan
Use this for historical/candle-close testing only. It should not be used as proof that intrabar live-cross timing works.
Daily Scanner Plan
Use Run Once with Next live candle after click for less noise. Start Daily Scanner handles normal candle-close rules and WebSocket/live-cross rules automatically.
Triggered Alerts
Check alert source, timing, candle time, reference candle, duplicate key, and whether the alert was close-confirmed or intrabar.
Trade Automation Rules
Attach only trusted Hammer alert rules to demo trading. Set SL/TP policy, position size, flat-position rule, and same-symbol duplicate behavior.
Demo Orders Monitor
Confirm every demo entry has the expected SL and TP orders. Missing protection must be handled before continuing automation.

Important distinction

Close Alerts vs Live Cross Alerts

Candle Close

Stable and safer. Alert is created after candle close, so the pattern is already confirmed.

Live Cross

Faster and noisier. Alert can trigger before close when price crosses a selected high or low.

Reference Level

Every live-cross alert needs a stored reference candle or level, such as previous high, previous low, support, or resistance.

Duplicate Safety

One reference candle and direction should create one alert only, even if live price crosses the level many times.

Scanner test

Manual Scan Now

Run saved Alert Rules against locally stored candles before enabling daily background automation.

Not scanned
Candles--
Rules--
Matches--
Created--
Create Alert Rules and download chart candles, then run a manual scan.
Manual Scan Results--

Manual scan guide

What This Does

Uses Stored Candles

Manual Scan does not download candles by itself. Download historical data in Chart Data Storage first.

Uses Alert Rules

Only saved and enabled Alert Rules are scanned. Rules decide which indicator events become triggered alerts.

Blocks Duplicates

If the same alert already exists for the same candle, it is counted as a duplicate instead of being saved again.

No Trading Yet

This local scan creates signal history only. Demo trade execution will be added after scanner validation.

Daily automation setup

Daily Scanner Plan

Save the daily scan window, symbol-volume filter, timeframes, and Alert Rules before building the live scheduler.

No plan loaded

Optional speed controls

Scanner Optimization

Default original process

When optimization is off, the scanner uses the original full process: full stored history, candle readiness check, one safe worker, then alert scan and trade evaluation. It is slower, but easier to understand and gentler for first testing.

Keep optimization off until the scanner result is correct. Turn it on later to make repeated automatic cycles faster.

Timeframes

Alert Rules

No Alert Rules selected yet.

Start--
End--
Timeframes--
Rules--
Save Daily Plan

Save only when you change times, symbols, timeframes, rules, or checkboxes. You do not need to save it every day.

Enable daily plan

When checked, Start Daily Scanner can run this plan during the saved time window. When unchecked, the scanner skips safely.

Reset selected symbols every day

When checked, each new session can rebuild the symbol universe from fresh 24h volume data.

Run Once Now

Runs one immediate test cycle and stops. By default it scans and evaluates only. It can place Demo/Testnet orders only when the Run Once demo order checkbox and max order count allow it.

Start Daily Scanner

Starts the real automatic loop during the saved window. It scans normal candle-close rules, starts live-cross monitoring when needed, evaluates alerts, and lets Trade Automation Rules plus Safety decide whether Demo/Testnet orders can be placed.

Speed controls

Workers are parallel scanner jobs. 1 worker is slowest but safest. More workers can finish faster, but can add API and computer load.

Stop Daily Scanner

Stops the loop only. It does not delete the saved plan, symbol universe, candles, or triggered alerts.

Save the plan locally before we build the VPS scheduler.

Background execution

Daily Scanner Runtime

Stopped
Daily Scanner Controls

One start button runs the saved daily plan. Normal candle-close rules and live-cross rules are handled automatically.

Automatic
Run Once Test Steps

Choose which real steps Run Once should perform. Keep all steps selected for normal testing.

Test only
Run Once is a test by default. It can place Demo/Testnet orders only if you tick the Run Once demo order checkbox, set a max order count above 0, and the Safety page allows demo orders.
Run Once Now remembers the last candle it tested, so the next Run Once creates alerts only from newer candles. Use Clear Run Once Test Alerts only when you intentionally want to delete run-once test alerts and reset that Run Once checkpoint for retesting the same candles.
Live Cross Engine Status

Started automatically by Start Daily Scanner only when selected Alert Rules use live-cross settings.

Stopped
Streams--
Rules--
Created--
Duplicates--
Live-cross engine is automatic. Set optional live-cross settings in Alert Rules when an indicator needs intrabar crossing checks.
Live Cross Scanner Results--
Next run--
Symbols--
Created--
Duplicates--
Start only after Symbol Universe and Candle Readiness are complete.
Background Scanner Results--

Daily plan guide

What This Saves

Session Window

The selected timezone, start time, and end time define when each daily scanner session should run.

Daily Reset

When reset is enabled, the next day can build a fresh symbol list from the latest 24h volume data.

Symbol Filter

Minimum 24h quote volume decides which symbols qualify. Symbol limit is All by default, or a Top N cap when selected.

Trade Automation

Start Daily Scanner follows Trade Automation Rules and Safety. Run Once has its own demo-order test option so you can test order placement manually before relying on the automatic loop.

Daily Scanner Runtime

Run Once Now uses the selected test steps beside its button. Start Daily Scanner uses the saved Daily Scanner Plan and optional optimization settings at the top of this page.

Daily symbol builder

High-Volume Symbol Universe

Build today's scanner symbol list from Binance USD-M Futures 24h quote volume.

No universe built
Session date--
Active symbols--
Selected--
Built at--
Use Daily Scanner Plan values or override them here, then build today's symbol list.

Selected Symbols

--

No selected symbols yet.

Rejected Symbols

--

No rejected symbols yet.

Universe guide

How Symbols Are Chosen

Active Perpetuals

The builder keeps only active USD-M Futures perpetual contracts from Binance exchange info.

Quote Volume

Symbols are ranked by 24h quote volume from Binance ticker data, then filtered by your threshold.

Symbol Limit

All matching symbols are selected by default. Choose Top 10, 20, 50, 100, or more only when you want a cap.

Next Step

After this list is built, candle readiness will check whether each selected symbol has enough history.

History gate

Candle History Readiness

Check whether selected symbols and timeframes have enough stored candles before background scanning starts.

No check yet
Total checks--
Ready--
Missing--
Required--
Build Symbol Universe first, then check candle readiness.
Candle Readiness Rows--

No readiness rows yet.

Readiness guide

What This Checks

Selected Universe

Readiness uses the symbols from the saved Symbol Universe and timeframes from Daily Scanner Plan.

Indicator Need

The required candle count comes from selected indicators, with a local minimum of 100 candles.

Backfill

Backfill downloads missing historical candles using Binance REST and stores them in the local chart candle store.

Gate Before Scanner

Background scanning should only start for symbol/timeframe rows marked ready.

Background signal inbox

Triggered Alerts

Search alerts that were triggered by indicators. The status shown on each card comes from optional manual review or later trade automation decisions.

No alerts loaded
Total--
New--
Reviewed--
Ignored--
No triggered alerts loaded yet.
Use the Status filter to see New, Reviewed, Ignored, Trade blocked, or Trade opened alerts. Alert Review is optional and is only for manual notes, status cleanup, and deleting local test alerts.
Triggered Alerts List--

Alert guide

How This Page Will Be Used

Signal Inbox

Every scanner match is saved here with symbol, timeframe, indicator, event, side, candle time, and optional entry/SL/TP.

Duplicate Safety

The duplicate key is stored internally so the same symbol, timeframe, indicator, event, and candle cannot create repeated local alerts.

Daily Views

Use Alert period to see today's alerts, previous-day alerts, or only alerts triggered after the saved daily scan start time.

Trading Locked

This page stores signals only. Demo and live orders remain disabled until the later Trade Automation Rules step.

Demo trade gate

Trade Automation Rules

Choose which triggered alerts may open demo/testnet trades, review ready or blocked decisions, and send Demo/Testnet orders only when safety gates allow them.

No trade rules loaded
Create Alert Rules first, then define demo trade permissions here.
Saved Trade Automation Rules--

Dry-run execution gate

Demo Trade Decisions

Evaluate triggered alerts against saved Trade Automation Rules before any Binance testnet order endpoint is connected.

No decisions loaded
Demo ordersLocked
Demo credentials--
Live tradingLocked

Filtered decision list

Ready Demo Order List

Shows the saved decisions matching the selected status, symbol, and limit filters.

--
Use Test Demo Trade Decision from Triggered Alerts for sample manual checks only. Later automation will evaluate new triggered alerts in the background.

Trade safety guide

What This Controls

Demo Only

Rules are stored for Binance Demo/Testnet only. Live trading stays locked.

Duplicate Control

Use same-symbol and flat-position controls to prevent repeated or conflicting demo trades.

Risk Limits

Max trades per day, open trades, trades per symbol, position size, SL/TP policy, default SL %, and TP/RR are saved before order execution exists.

Order Kill Switch

Demo/Testnet orders require the local execution switch and saved demo credentials. Live orders remain locked.

Decision Gate

Triggered Alerts can be evaluated as dry-run demo trade decisions. Ready means the rule allowed it; blocked means no order should be sent.

Global safety gate

Safety

Set the dashboard-wide demo/testnet automation limits before any order reaches Binance Demo/Testnet. Live trading stays locked.

Not loaded
Effective demo orders--
Live tradingLocked
Active demo decisions--
Today demo decisions--
Safety settings not loaded yet.

Safety guide

How This Gate Works

One Effective Gate

Demo orders require both the Demo/Testnet order switch and Safety settings to allow the action.

Pause And Maintenance

Pause blocks new demo orders. Maintenance also blocks cancel/close controls while you are changing settings.

Global Limits

These limits sit above individual Trade Automation Rules and apply to every demo order attempt.

Audit Trail

Every Safety settings save is recorded in Audit Logs so VPS migration can keep the same control history.

Demo/testnet only

Demo Orders Monitor

Monitor Binance Demo/Testnet wallet, positions, open SL/TP orders, and local execution decisions. Live trading remains locked.

Not loaded
Demo orders--
Available USDT--
Unrealized PnL--
Live tradingLocked
Refresh monitor after connecting Demo/Testnet API credentials.
Demo reconciler status not loaded yet.

Local vs Binance check

Reconciliation

Not checked --

Open exposure

Open Demo Positions

--

Protective and pending orders

Open Demo Orders

--

Local execution log

Recent Demo Decisions

--

Monitor guide

What This Page Does

Demo Only

This page reads and controls Binance Demo/Testnet orders only. Live trading is still locked.

Cancel Orders

Cancel open demo SL/TP or pending orders for one symbol when you need to clean up a test.

Close Position

Close an open demo position with a reduce-only market order after confirming the action. The dashboard also tries to clean normal and algo SL/TP orders for that symbol.

Audit Trail

Recent decisions show what the dashboard attempted and whether Binance accepted or rejected it.

Orders vs Positions

In Futures, an accepted market order opens or changes a position. So a test may show a position even when the later SL/TP protection step failed.

Clear Failed Errors

Use this only to clean failed messages from this monitor view. It does not close positions, cancel Binance orders, or delete audit history.

Global report library

Reports & Analytics

Explore every report type planned for this dashboard. Use this page to understand what each report shows, which data it needs, and whether it can be built now or after VPS/PostgreSQL migration.

32 reports
Market Data
Indicators
Alerts
Decisions
Demo Orders
PnL / Risk
Total reports--
Can start now--
Needs more demo data--
Needs VPS/PostgreSQL--
Select a report card to see what it will show and why it matters.

Live local report

Daily Control Room

One place to confirm today's API connection, scanner plan, symbol universe, candle readiness, alert activity, and demo/testnet safety state before automation runs.

Not loaded
Report date --
Checks passed --
Last refresh --
API Connections -- Demo/Testnet and Live Market Data
Daily Plan -- Window, timezone, and selected rules
Symbol Universe -- Selected symbols for today
Candle Readiness -- Historical data coverage
Scanner -- Automatic runtime state
Demo Safety -- Demo/testnet order gate
Current Alerts -- After daily scan start
Trade Decisions -- Ready, blocked, opened, attention
Daily Session Timeline--
Readiness Checklist--
Refresh to load today's control-room status.

Live local report

Alert Funnel

Follow dashboard indicator alerts from trigger to trade decision, blocked state, ready-for-demo order, demo order attempt, opened position, protection, and attention items.

Not loaded
Funnel Stages--
Drop-off Checks--
Scanner Inputs--
Top Symbols--
Top Indicators--
Top Timeframes--
Trade Rules--
Refresh to load the alert funnel.

Live local report

Live Cross Verification

Confirm whether selected Alert Rules require intrabar live-candle cross monitoring, whether the live-cross scanner is running, and which rule settings are still missing.

Not loaded
Configured Rules -- Selected rules with complete live-cross settings
Selected Symbols -- From Symbol Universe
Estimated Streams -- Symbols x timeframes x price source
Scanner State -- Current WebSocket engine state
Live-Cross Checks--
Rule Readiness--
Recent Live-Cross Alerts--
Refresh to load live-cross verification.

Live local report

Demo Order Lifecycle

Review demo/testnet order decisions from ready state through order attempt, opened position, SL/TP protection, close, failed/unknown state, and attention items.

Not loaded
Lifecycle Stages--
Symbol Lifecycle Summary--
Recent Order Attempts--
Needs Attention--
Refresh to load demo order lifecycle.

Live local reports

Additional Reports Available Now

These reports use local dashboard records that already exist, so they can be used before VPS/PostgreSQL migration.

Not loaded
Market Universe Report--
Selected--
Rejected--
Active symbols--
Min quote volume--
Candle Data Quality Report--
Total checks--
Ready--
Missing--
Required--
Indicator Quality Report--
Packages--
Import ready--
Alert options--
Needs attention--
API / Rate Limit Report--
API logs--
Failures--
Demo attempts--
Live attempts--
Audit / Compliance Report--
All logs--
Tracked logs--
Credential actions--
Order actions--
Data Retention / Cleanup Report--
Sections--
Current rows--
Removable--
Local size--
Triggered Alerts Report--
Alerts--
Symbols--
Indicators--
Duplicate keys--
Trade Decision Report--
Decisions--
Ready--
Blocked--
Order sent--
Reconciliation Report--
Monitored--
OK--
Need attention--
Protected--
Demo Performance Report--
Attempts--
Opened--
Closed--
Avg RR--
Risk Exposure Report--
Open--
Ready--
Notional--
Planned risk--
Scanner Performance Report--
Checkpoints--
Stale--
Last created--
Skipped--
Refresh to load the additional local reports.

Report catalog

All Reports

--

Build sequence

Recommended Implementation Order

Local first

Dashboard-native reports

Detailed Analysis

Review indicator alerts, trade decisions, lifecycle status, and demo/testnet outcomes from local dashboard records.

Not loaded
Alerts--
Symbols--
Decisions--
Need attention--
Ready decisions--
Blocked decisions--
Opened demo orders--
Protected orders--
Analysis not loaded yet.

Symbol performance

Alerts And Decisions By Symbol

--

Indicator performance

Alerts And Decisions By Indicator

--

Timeframe performance

Alerts By Timeframe

--

Trade rule performance

Trade Automation Rule Results

--

Needs review

Lifecycle Or Protection Attention

--

Latest alerts

Recent Triggered Alerts

--

Latest decisions

Recent Trade Decisions

--

Analysis guide

How To Use This Page

Read Only

This page does not scan, create alerts, or send orders. It only reads local dashboard records.

Start With Attention

Check Need attention first. These are failed, unknown, or unprotected demo lifecycle records.

Compare Rules

Use symbol, indicator, timeframe, and trade rule tables to see which rules create useful or blocked outcomes.

VPS Target

This local report will later become PostgreSQL report queries with exports and scheduled summaries.

Preview before delete

Database Cleanup

Clean local JSON test data only after reviewing the preview. Active demo order decisions are protected from decision cleanup.

Not previewed
Selected sections--
Current records--
Removable records--
Approx local size--
Choose cleanup areas, then preview before applying.
Cleanup Preview Rows--

Apply cleanup

Confirm Local Test Data Deletion

Type DELETE LOCAL TEST DATA exactly. Cleanup applies only the selected preview options.

Cleanup guide

How This Page Works

Preview First

Preview shows current records, removable records, remaining records, and sample rows before deletion.

Candle Cleanup

Candles are cleaned by age and by keeping the latest candles per dataset. Symbol filter limits candle cleanup to matching symbols.

Protected Decisions

Pending, opened, and unknown demo order decisions are kept so the monitor can still reconcile them.

VPS Target

On VPS this will become PostgreSQL dry-run counts, export-before-delete, and admin-only cleanup permissions.

Operational history

Audit Logs

Review important dashboard actions before we move the same flow to VPS PostgreSQL.

Not loaded
Total logs--
Credential/API--
Trade events--
Safety changes--
No audit logs loaded yet.
Audit Log Rows--

Audit guide

What This Page Records

Credential Actions

Save, connect, use saved, diagnose, and disconnect actions are recorded without exposing API secrets.

Alert And Rule Changes

Alert rule, trade rule, triggered alert review, delete, and clear actions are tracked.

Demo Order Actions

Ready/blocked decisions, demo order sends, unknown timeouts, failures, cancel orders, and close position actions are visible here.

VPS Migration

This local JSON log will later become a PostgreSQL audit_logs table with user, IP address, and role details.

Alert maintenance

Alert Review / Cleanup

This page is optional. It is only for manual notes, changing review status, ignoring test alerts, or deleting local test alerts.

Review controls
What happens when status is changed?

The status is saved on that individual triggered alert and appears again in Triggered Alerts. It does not change the Alert Rule, and it does not automatically affect future alerts for the same symbol.

Do I need to review every alert?

No. Normal automation should use Alert Rules and Trade Automation Rules. Manual review is only for testing, notes, cleanup, or intentionally marking alerts as ignored.

Where do I see the result?

Open Triggered Alerts and use the Status filter. Counts for New, Reviewed, and Ignored are shown above the alert list.

Review list not loaded yet.
Alert Review Rows--

VPS readiness

Deployment Health

App uptime --
PostgreSQL --
Redis --