Can traders use their own charting software?

Integration options depend on the deployment and the provider involved. The default is that traders work inside the branded Nexus workspace so that risk enforcement, order lifecycle and support context stay in one place; external tooling is scoped case by case.

Which instruments are supported?

Futures are the primary evaluation market, with crypto supported and additional asset classes scoped per deployment. Which markets your program offers is a configuration and licensing question rather than a fixed product boundary.

Is the platform white-labelled end to end?

Yes. The trading workspace carries your brand, your domain and your program's rules. Traders do not encounter Nexus branding in a white-label deployment.

Nexus Trading

The trading platform built for funding evaluations.

A native, white-label trading workspace with advanced charting, simulated order execution and risk controls that read the same account record your back office does.

A funding evaluation is not ordinary trading. The platform is simultaneously the place a trader works and the instrument that decides whether they pass, which means it has obligations a retail front-end does not: every fill has to be attributable, every rule has to be enforced against a state the operator can later reconstruct, and the trader has to be able to see the same thing the risk engine sees.

Nexus Trading is built to that standard. It is a workspace traders will use daily — charting, order entry, watchlists, depth, indicators — sitting on execution and risk machinery designed for evaluations rather than retrofitted from a retail product.

The Nexus Trading workspace showing charting, watchlist, order entry and account-aware risk controls — Actual Nexus Trading capture with sample data and a static connection state, cropped above the app header to remove a storefront promotion. Provider branding is redacted in public derivatives until its use is approved.

A trading workspace built to earn daily use

If traders dislike the terminal, the program has a retention problem no marketing budget fixes.

Advanced charting

Multi-timeframe charts, a broad indicator library, drawing tools and chart-attached order interaction, so a trader is not switching to a third-party terminal to think.

Simulated order execution

Market, limit, stop and bracket orders resolved by a simulated matching engine against licensed data. Deterministic and reconstructible, which is what an evaluation dispute requires.

Account-aware controls

The workspace knows which account is selected, what its plan allows and how close it is to a limit — because it reads the account record rather than a cached copy.

Depth and market context

Order book depth, time and sales, and the market context traders expect before committing size, sourced from the same licensed feed the evaluation runs on.

Live position and P&L state

Realised and unrealised P&L, open positions and working orders reconciled against the authoritative account, not derived independently in the browser.

Protective order behaviour

Global protective orders and per-account constraints applied at the platform level so a rule cannot be bypassed by trading around the interface.

Where execution authority sits

The most consequential design question in an evaluation platform is which system is allowed to say what happened. If the trading front-end computes a fill and the back office computes a different one, the firm has no defensible position when a trader disputes a breach.

In Nexus, order lifecycle and matching resolve centrally, and the resulting fills, positions and P&L are written to the account record that risk, CRM, payouts and support all read. The trading interface renders that state; it does not own it.

That boundary is worth interrogating in any vendor evaluation, not just this one. How to measure and verify it sets out the properties an operator should test before signing.

Connected to everything downstream

Risk rules enforced in place

Drawdown, daily loss, consistency and account-state rules are evaluated against the same record, so enforcement and explanation match. See risk management.

Licensed real-time data

Real-time prices and depth across CME, CBOT, COMEX and NYMEX under Nexus's own licenses, with every identifier published. See market data.

Trader context for support

When a trader asks about a fill, the person answering can see the order, the account and the rule that applied. See native support.

Fraud signals from trading behaviour

Coordinated trading and hedging patterns surface as trading-risk signals rather than being invisible until payout. See fraud prevention.

Common questions

Can traders use their own charting software?: Integration options depend on the deployment and the provider involved. The default is that traders work inside the branded Nexus workspace so that risk enforcement, order lifecycle and support context stay in one place; external tooling is scoped case by case.
Which instruments are supported?: Futures are the primary evaluation market, with crypto supported and additional asset classes scoped per deployment. Which markets your program offers is a configuration and licensing question rather than a fixed product boundary.
Is the platform white-labelled end to end?: Yes. The trading workspace carries your brand, your domain and your program's rules. Traders do not encounter Nexus branding in a white-label deployment.

Keep reading

Back to hub

Platform

One platform connecting the branded trader experience with CRM, risk, fraud prevention, payouts and support so every team works from the same account context.

Read

Risk management

Configure evaluation rules, monitor account state in real time, review breaches and keep every risk decision connected to the underlying account record.

Read

Market data

Nexus Prop holds direct CME, CBOT, COMEX and NYMEX licenses for real-time receipt, distribution and market-depth SIM. Every identifier is published here.

Read

Next step

Contact

Talk with Nexus about launching, migrating or building a funded-trader platform, and get a scoped view of deployment, integrations and operating support.

Read

See the trading workspace against your own scenarios.

The useful version of this demo is your evaluation rules, your instruments and your edge cases — not a generic tour.

Book a technical walkthrough See the whole platform