Pages
Setting up a Rithmic-connected prop firm account means downloading R|Trader Pro, selecting the correct server plant from your firm's credential email, accepting the market data agreement, and connecting your preferred front-end platform. This guide walks through every step in order, covers the most common setup errors, and closes with a note on where SHARK Futures fits. SHARK traders on TradeSea skip the Rithmic setup entirely.
Rithmic is an order routing and market data infrastructure layer used by futures clearing firms (FCMs) and the prop firms that work with them. When a prop firm says it "uses Rithmic," it means the firm's FCM has registered accounts on Rithmic's network. Your evaluation or funded account exists on that network, and any platform you use to send orders must authenticate against it.
Rithmic is not a broker and not a platform. It is the pipe. The firm's FCM sits on one end; your front-end software sits on the other. A wrong server plant, bad credentials, or blocked ports will prevent you from trading even if the account itself is fully active.
Most traders never open R|Trader Pro past the initial credential test. They connect a third-party front end like NinjaTrader to the same Rithmic account and trade there. R|Trader Pro is Rithmic's own desktop application, useful for confirming that credentials work and that the correct account is visible before committing to a specific front-end setup.
Before downloading anything, locate the credential email from your prop firm. It will contain at minimum:
If your email does not specify a server plant, contact your prop firm's support before proceeding. Guessing is not productive.
Prop firm accounts go through a provisioning step between join and activation. Before you download R|Trader Pro, reply to the credential email or open a support ticket to confirm the account status is "active" or "live" on the firm's side. A credential set that arrives before provisioning is complete will appear to fail even with correct inputs.
On first launch, R|Trader Pro presents a login screen with a gateway dropdown. This is the server plant selector. Set it to the plant your firm specified. If the firm specified "Chicago," select the Chicago gateway. Do not leave it on the default, which is typically the Rithmic paper trading environment rather than the live prop account network.
After entering your username, password, and gateway:
If quotes do not populate after accepting the agreement, see the troubleshooting section below.
NinjaTrader is the most common front end used with prop Rithmic accounts. Setup requires Multi-Provider Mode because NinjaTrader defaults to its own brokerage connection:
Several charting and execution platforms support Rithmic as a data and order routing provider. Each will have a Rithmic connection option in its broker/data setup screen and will require the same username, password, and server plant. The process mirrors the NinjaTrader steps above. Consult your specific platform's documentation for exact field names; the required inputs do not change.
Before submitting any order, open the account selector inside your front end and verify the account string matches the prop account identifier you confirmed in R|Trader Pro. Some Rithmic setups surface multiple accounts, a paper account alongside the live eval, and routing an order to the wrong one wastes a trade on an account that does not count.
Rithmic maintains a paper trading environment accessible through R|Trader Pro and most front ends. Set the server plant dropdown to Rithmic Paper Trading rather than your firm's live plant. Some firms issue separate paper credentials, so check with support before assuming your live credentials work here.
The Rithmic demo replicates order entry mechanics, platform connection behavior, and data feed structure. It does not replicate your prop firm's specific drawdown rules, position limits, or consistency requirements. Use it to confirm that your platform connects, that orders submit without errors, and that your hotkeys and order templates behave as expected. Do not use fill quality or P&L from demo sessions to calibrate your edge; the execution environment is simulated.
If R|Trader Pro or your front end returns an authentication error despite correct credentials, the server plant is almost always the cause. Return to the gateway dropdown and confirm the exact value your firm specified. Rithmic plant names are case-sensitive in some front ends. If you received a plant name with mixed case, enter it exactly as written.
Symptom: the connection status shows green (authenticated) but no bid/ask data appears on any contract. This means the market data agreement was not accepted during the R|Trader Pro first-login flow. Log in to R|Trader Pro directly, navigate to the agreement prompt (found under Account > Market Data Subscriptions on some versions), accept it, and reconnect your front end.
Rithmic uses TCP port 443 and several ports in the 10000-range depending on the plant. Windows Defender and most corporate firewalls allow 443 but may block higher ports. A timeout rather than an authentication error means the connection is being dropped before it reaches Rithmic's servers. Add an outbound rule in Windows Firewall for the Rithmic executable, or contact your network administrator with Rithmic's published port requirements.
Apex Trader Funding, Bulenox, and Take Profit Trader route through Rithmic and expect you to complete the setup described above yourself. You receive credentials, select the plant, and configure the front end. The firm provides the account; the connection work is yours.
SHARK Futures accounts also trade on Rithmic infrastructure, through the SHARK x TradeSea platform. The difference is what you do about it: nothing. No R|Trader Pro install, no server plant to choose, no activation email to wait on. Log in at tradesea.ai and the broker sync is already done. TradeSea handles the Rithmic connection on the back end, so the setup process described throughout this guide does not apply to SHARK traders on TradeSea.
This matters in practice. Every step where a generic Rithmic setup can stall, wrong plant, firewall block, data agreement not accepted, is a step SHARK traders on TradeSea do not encounter.
Volumetrica is available as an alternative platform for SHARK traders who prefer it. It runs on a dxFeed connection, not Rithmic, and has no involvement with the Rithmic infrastructure described in this guide. The R|Trader Pro steps above do not apply to Volumetrica users either.
Platform setup is a one-time friction. Account rules are ongoing. Before committing to any evaluation, read the drawdown mechanic carefully.
Most prop firm accounts use a trailing drawdown that moves on intraday high-water equity. One mid-session spike in unrealized P&L permanently raises the floor. You can give back those unrealized gains and close the day flat, but the drawdown floor is now higher than it was at the open.
SHARK's drawdown mechanic works differently. The floor reads the highest closed end-of-day balance, not the intraday tick. Unrealized equity during an open position is never evaluated. A position that runs up significantly during the session and closes at a modest gain does not raise the floor beyond that modest gain. The allowance is a fixed dollar figure per account size: $1,000 on a $25K account, $2,000 on $50K, $3,000 on $100K, and $4,500 on $150K.
The profit split is 90%. Account sizes are $25K, $50K, $100K, and $150K. You can hold up to five accounts simultaneously for a maximum of $750K in capital. The full rules are published at sharkfutures.com/programs.
If you are ready to start an evaluation, the entry point is app.sharkfutures.com/entry. Basic Evaluation plans start at $99 for a $25K account; Instant Pro plans start at $399.
For platform and account questions specific to SHARK, the help center is at help.sharkfutures.com.