BluSky and order flow software: one shared Rithmic system, both phases

The system name and what it implies

BluSky uses Rithmic Paper Trading, a shared environment several firms route through for their simulated products. The orders are simulated; the market data is live. That distinction is the one that matters for order flow analysis, because it means the bid and ask volume you read during an evaluation came from the real auction rather than from a price generator.

The same name covers the funded account, so nothing on the connection profile needs editing when the account converts. Firms that switch system names at that point are the ones where a first funded session starts with a login failure.

What an order flow trader can build on it

One concurrent market-data session per login applies, as everywhere on Rithmic: R | Trader Pro and a charting platform compete for the same feed.

• Footprint charts, from trades carrying the aggressor side.
• A DOM ladder and a liquidity heatmap, from depth of market.
• Session replay and volume profiles, from historical bars and ticks, subject to the entitlements on the account.
• A trade journal reconstructed from the account's own fills and P&L.

What belongs to the firm, not the software

Drawdown, daily loss limits, consistency requirements and payout terms are set and enforced by BluSky, and they change. Software can mirror a rule set to warn you before you cross a line, which is genuinely useful during a session, but a mirror is not the rule: it reflects the terms as they were entered, and it can be out of date. Check the current terms with the firm.

The same separation applies to automation. A platform being technically able to place an order on the account says nothing about whether the agreement allows a strategy to do it unattended. Ask in writing before arming anything.