Astrofund and order flow software: dxFeed, not Rithmic

The backend decides compatibility, not the brand

Futures prop firms sit on a small number of technical backends. Most of the ones a retail trader meets route through Rithmic; some use Tradovate; Astrofund issues dxFeed credentials to its funded traders. A platform speaks one or more of these protocols, and a firm whose backend it does not speak is not a configuration problem but an absence of one.

This is worth checking before buying an account rather than after. The order in which most people discover it is the expensive one: pass an evaluation, get funded, then find the charting software they have trained on cannot see the account.

What dxFeed changes in practice

dxFeed is a market data vendor rather than a brokerage routing protocol, and its access model differs from Rithmic's in a way that matters to platform builders: there is no single universal endpoint. Each firm issues its own credentials and its own entry point, so a platform cannot ship one address and expect every dxFeed account to work. That address belongs on the connection profile, entered with what the firm provided.

Senzoukria documents dxFeed in its connection catalogue so that the backend is recorded, but the rail is not shipped and the entry cannot be selected. Saying that plainly is more useful than listing the firm as supported and letting a funded trader discover the gap.

If you trade order flow and are choosing a firm

• Ask which backend the account runs on before you buy: Rithmic, Tradovate, dxFeed or the firm's own platform.
• Ask whether the answer is the same for the evaluation and the funded account, because several firms change it at conversion.
• Check that your platform speaks that backend, and that the account carries the historical data entitlement if you replay or backtest.
• Confirm separately whether third-party software and unattended automation are permitted by the account agreement.