What is connected, and what is not.
You are about to point software at an account with real pass/fail conditions. So here is the current state of every integration, including the ones that do not exist yet.
Atlas does not yet route live orders to TopStep, Tradovate or Rithmic.
The current build trades a paper broker against a simulated market. The live venue is a Rust trait with an explicitly unconfigured implementation that refuses every order — chosen over a stub that accepts orders and drops them, because a system that appears to be trading and is not is the most dangerous failure this product could ship.
What Atlas gives a prop trader today is the rule engine the firm grades you against, running live on every decision, plus a full research and journalling stack to develop against those constraints. When an adapter lands, nothing above the broker layer changes — that is what the trait is for.
Integration status
Paper broker (simulated market)
ShippingDefault and fully functional. Regime-switching synthetic feed with GARCH-style volatility clustering, Student-t innovations and real intraday seasonality. Models commission and slippage.
TopStep prop rule profile
ShippingThe rule set, not the connection. Trailing drawdown against the equity peak, daily loss with a configurable safety buffer, consistency ratio, minimum trading days and flat-before-close are enforced on every decision.
TopStep / Tradovate order routing
Not connectedNot connected. Atlas ships a broker-agnostic Broker trait and an unconfigured live stub that refuses every order rather than silently doing nothing. An adapter is the trait plus credentials; no engine code changes when one lands.
Rithmic order routing
Not connectedNot connected. Same position as above.
Level 2 depth feed
PartialThe OFI calculation is implemented to Cont–Kukanov–Stoikov and its book-update entry point is ready. No depth subscription ships, so the engine drives a Lee–Ready tick-rule proxy, labelled as a proxy everywhere it appears.
Five rules, evaluated on every decision.
Prop-firm rules are not risk management — they are pass/fail conditions imposed by a counterparty, and one breach ends the account no matter how the strategy is performing. They get their own gate, evaluated independently of and in addition to internal risk.
- Trailing drawdown
- The loss floor follows the equity peak, including unrealised profit at most firms. A trader up 2,000 and back to flat has consumed 2,000 of drawdown without ever having a losing day. Atlas tracks the floor continuously and refuses any trade whose stop would breach it.
- Daily loss with a buffer
- The working limit is the firm's hard limit less a safety buffer you set, floored at a tenth of the stated allowance so a misconfigured buffer cannot collapse the limit to zero and veto every trade from the first bar.
- Consistency ratio
- No single day may contribute more than a set share of gross profit. Passing the target on one lucky session fails the account. Atlas warns as the ratio approaches the ceiling, with the arithmetic shown.
- Minimum trading days
- Counted and reported against the profile's requirement, so hitting the profit target early does not read as done when it is not.
- Flat before close
- Where the profile requires it, holding a position inside five minutes of the session close is a veto — and the veto names the minutes remaining and the position count.
Four steps, once.
- 1
Install and activate
Download Atlas-Setup.exe from your client portal and paste the licence key shown there. The key binds to this machine's hardware ID on first launch. Autonomous execution is off by default and stays off until you arm it.
- 2
Pick a prop profile
Prop Profiles → choose or clone a profile matching your evaluation: account size, daily loss limit, maximum drawdown, whether the drawdown trails, profit target, consistency percentage, minimum trading days. Set a safety buffer — the amount of the firm's daily limit you refuse to spend.
- 3
Store broker credentials
Your prop-firm API token and username go in the client portal's credential vault, encrypted with AES-256-GCM before they touch our database. Atlas reads them locally at connect time. The token is never displayed again after you save it — the portal shows only the last four characters.
- 4
Run in paper until it earns live
Leave the paper broker attached and let Atlas evaluate a full session. Read the refusal log. The point of the exercise is to see what it declines and why, because that is the behaviour you are actually buying.
On shared servers and VPNs
Most prop firms prohibit trading from a shared server or a commercial VPN endpoint, because that is how one signal gets copied across a hundred funded accounts. Atlas is a desktop application: it runs on your machine and connects from your IP. The only traffic it sends us is a licence heartbeat containing a key, a hardware ID and a version string — no positions, no orders, no P&L. See the privacy notice for the exact payload.