Skip to main content
The rest of this site is written for your engineers: keys, routes, webhooks. This page is the other half of the deal. Your traders do not call the API — they sign in to trdrs and get a finished trading platform, and every feature below is one you do not build, host, or support.

The chart

Live candles, 20+ built-in indicators, a full drawing toolset, market sessions, and per-symbol settings that follow the trader between devices.

Alerts

Price alerts on any symbol, delivered while the trader is away from the screen.

The order ticket

Market, limit, stop and stop-limit orders with bracket exits, saved exit plans, and one order path with the safety rails on by default.

Bar replay and backtesting

Replay any session bar by bar, and test strategies against history before risking an account.

Strategies and scripts

Author strategies and custom indicators in the built-in editor, with the platform’s own scripting SDK and built-ins.

The journal

A calendar of every session, with the trades attached — the review habit a firm wants its traders to have.

The trade copier

Mirror one account’s trades into others, for traders running more than one account.

Leaderboard and competitions

Real-P&L standings and prize-pool competitions, if you want your traders competing in public.

The AI assistant

An assistant that reads the trader’s own charts and journal, in the same workspace.

Phone and desktop

The same workspace on a phone, including the chart, the ticket, and every menu built for touch.

Why this matters to your integration

Your engineers integrate the parts a firm actually owns: issuing accounts, governing risk, reconciling billing, and reacting to events. The trading experience is already built and already maintained — so an evaluation you sell on Monday is tradable on a full platform the same day, without a front end of your own.
Building your own front end anyway? The chart library and the TypeScript SDK are the same pieces this platform is made of.

What you still decide