Use Cases

One charting terminal, three very different ways to use it

The value of charting software depends on your trading rhythm. The three user types below differ greatly in latency, timeframe and instrument needs — and that is how our plans and default layouts are designed.

Scenario 1

Day trading

Focus on 1-minute to 1-hour timeframes, needs low-latency quotes and live alerts, sensitive to interface response speed.

  • Four panes showing 5m, 15m, 1h and daily charts together
  • Volatility alerts set around the London–New York session overlap
  • ATR-based stop distances instead of fixed point values

Suggested plan: Professional (low-latency feed)

Scenario 2

Swing and allocation

Works mainly on daily and weekly charts, cares about cross-market spreads, the gold/silver ratio and the dollar's relative direction.

  • XAU/USD vs SGE Au(T+D) premium comparison
  • Long-term charts of the gold/silver ratio and gold vs real rates
  • Signals confirmed at weekly closes to filter intraday noise

Suggested plan: Professional (with cross-market comparison)

Scenario 3

Institutions and brokers

Needs to feed market data into existing research, risk or client-facing systems, and cares about field definitions and compliant licensing.

  • REST and WebSocket APIs with field and timezone documentation
  • Multi-seat management with permission tiers
  • Redistribution of data requires separate licensing

Suggested plan: Institutional (API and technical onboarding)

A typical working day

A Hong Kong day trader's monitoring rhythm

The flow below follows Hong Kong time and shows where the terminal is actually used during a trading day.

Time (HK)ActionFeatures used
08:30Review overnight closes and gapsDaily chart, event markers
09:00Compare SGE opening premiumCross-market spreads, FX conversion
14:00Define ranges before the European sessionDrawing tools, ATR
20:30Volatility around US data releasesVolatility alerts, 1m chart
23:00Review and journalingChart screenshots, trading log

Before you choose

Confirm three things before talking feature lists

We usually ask these three questions before a demo, because they decide which latency tier and which layout you need:

  1. How long do you hold positions? Minute-level holding needs low latency and live alerts; if you work on a daily horizon, delayed quotes are enough.
  2. How many instruments do you watch? Two or fewer: single-chart switching is fine; beyond four, watchlists and multi-pane layouts pay off.
  3. Do you need to take data out of the terminal? For Excel, Python or your own systems, only the Institutional plan provides an API.
See plan differences

Not sure which type you are?

Tell us your holding period and watchlist in 30 minutes and we will recommend a plan directly — and say so honestly if we are not a fit.