Gato gTrader Suite

gTrader is the trading screen for the Gato suite. Desktop, web, and mobile all read the same orders, rules, and risk checks.

Order entry spans market, limit, stop, stop-limit, bracket, and multi-leg option tickets, with time-in-force and per-group permissions set by configuration rather than code.

Charts, option chains, and the blotter read live records, so quotes, working orders, and buying power update on the same tick a trader acts on.

Firms trade equities, options, futures, and FX here. Market data, order entry, and positions sit in one place.

Trading screens are judged on small things. How fast does a partial fill show up? Does the option chain stay quick at the open? Does the phone show the same positions as the desk? The answers come from where the data lives.

gTrader reads the same records as gHub and gPrecision. There is no nightly job to sync the front end. There is no separate position file for mobile.

Firms can also give gTrader to their own clients. Access rules set what each group sees and does. One setup serves many audiences.

Rollouts go desk by desk. One desk moves while the rest stay put. Both read one order record. So positions and buying power agree the whole time. No cut-over weekend.

Support work drops after the move. A client, a trader, and risk staff see one record. It has one history. A question becomes a lookup.

Every order passes through the same server-side check before it reaches the market, whether it originates from the desktop client, a browser session, or an API integration. If a limit would be breached, the order is rejected at the gateway — not flagged after the fact. Limit configuration lives in gPrecision, so risk and trading teams always see the same numbers.

Layouts are set once and shared. A desk template can define watch lists, order tickets, option chains, and position views. New traders start from it instead of building a screen from scratch.

Order entry covers the basics and the rest. Market, limit, stop, and stop-limit sit next to bracket orders, multi-leg options, and time-in-force choices. What a group can send is a permission, not a code change.

Charts read the same history as the blotter. A trader can move from a fill on the blotter to the chart around it without leaving the screen.

Alerts stay useful. Price, position, and margin alerts arrive on the device a trader is using, and each alert links to the record behind it.

To offer gTrader to outside clients, admins create a client-facing group with its own branding, order types, market data entitlements, and default layout — separate from the group used by internal desks. Because both run on the same deployment, updates and risk controls roll out to everyone at once, with no separate environment to maintain.

Onboarding a new trader is quick. Access is granted by group, so entitlements, limits, and layout arrive together on the first login.

Market data stays under your contracts. Quotes, depth, option chains, and history come from the feeds you license, and entitlements are applied per group, so a professional desk and a retail client can share one deployment without sharing one data package.

Multi-asset work happens on one ticket. A trader can send an equity order, a multi-leg option spread, a futures order, and an FX order without switching applications, and the resulting positions land in one portfolio view instead of four.

Performance is measured where it matters. The option chain, the blotter, and the position view all read live records, so the numbers a trader acts on at the open are the same numbers risk and operations see at that moment.

Operations teams get the same picture. Every route, state change, cancel, replace, and fill appears on one screen with its timestamps, which is what makes an end-of-day question a lookup rather than a reconstruction.