Skip to content
Jorli CLI

Dashboard

Terminal window
jorli dashboard

The command binds the .NET host to 127.0.0.1:7420, opens the browser, and serves the bundled Angular 21 production build. It shows:

  • health and worker heartbeat;
  • strategy versions;
  • a reactive strategy/broker/date backtest form with a running progress state;
  • complete backtest metrics, equity/drawdown and candlestick charts, P&L plus holding-period distributions, heatmaps, trade ledger, source, engine version, and data fingerprint;
  • a unified Kite/Dhan account view that remains visible when an adapter is missing or signed out, including account identity, install/auth/live readiness, capability matrices, holdings, positions, observed equity/day P&L/open-position/day-order risk usage, and read errors;
  • deployments, order intents, and audit events;
  • direct-stream credential presence, connection/stale state, resynchronization, sequence, reconnect attempts, and last-event time;
  • pause, stop, and global emergency-kill controls.

Control actions use PrimeNG confirmation dialogs. The local API requires a random in-memory session token in a custom header, rejects cross-origin mutation attempts, binds only to loopback, disables API caching, and serves a restrictive Content Security Policy.

The dashboard is a client, not the worker. Closing it does not manage positions or keep a strategy running. Start jorli worker run as an independent process and follow your OS service-manager practices for long-running shadow monitoring.