ProjectX

ProjectX is an advanced front end futures trading platform and backend admin interface for managing traders at the firm level.

[ProjectX @projectxtrading]

@Wepth @CoachDBA Open API; Exceptional Mobile Experience; Faster & Deeper Data... oh wait, that's us.

[ProjectX @projectxtrading]

@NinjaTraderProp This is some next level creativity.

[ProjectX @projectxtrading]

@Tradovate you good or nah?

[Tradeify @Tradeify]

ProjectX + New Plans: Go-Live Schedule

📣 Tradovate Users

Updated Plans Go-Live: Friday, September 12 @ 8:00 AM EST
Reminder: Details of plan changes here - https://t.co/Y6LmHDbybm

📣 ProjectX

ProjectX will be available as a platform option for new accounts: Sunday, September 14 @ 5:00 PM EST

Get ready - bigger & faster payouts, cleaner rules, and a new platform option! 📈

https://t.co/KtYupoNfZx

[ProjectX @projectxtrading]

@FvckYourHedge @Topstep Do you have Level 2 Depth of Market data enabled?

[ProjectX @projectxtrading]

@Khldfx The choice is clear

[Eduard Driessen @Eduard_Driessen]

This drama is dragging longer than it should with everyone suddenly acting like a coder.

In our beta integration with ProjectX we assumed accountId was unique. Docs and metrics identified nothing, a month of testing was clean.

When we scaled to more users, a clash appeared; one follower account ID existed twice. Causing a trade to copy to the wrong follower of another Tradesyncer user.

Maybe we shouldn’t have assumed. But after a month of clean testing, focus naturally shifted to other edge cases and improvements.

Regardless, we caught it and fixed in 3 minutes.

Not a ProjectX issue. Issue closed.

[ProjectX @projectxtrading]

@jmutrades @vwapx @Wepth @Topstep @MichaelPatak This

[ProjectX @projectxtrading]

@vwapx @Wepth @Topstep @MichaelPatak That is not what happened here

[ProjectX @projectxtrading]

@vwapx @Wepth @Topstep @MichaelPatak Every database in existence has a userId = 1. All of our clients have separate databases (and connection URI's) as we do not use single tenancy, which is best practice for a B2B SaaS like us.

[ProjectX @projectxtrading]

@UncleBugatti @dotjosh @Wepth @Topstep @MichaelPatak It seems that Tradesyncer is saying their integration with us is in beta. Not that ProjectX is in beta. We have many services integrated successfully like @TradersPostInc etc

[ProjectX @projectxtrading]

@dotjosh @UncleBugatti @Wepth @Topstep @MichaelPatak You are correct @dotjosh

[ProjectX @projectxtrading]

@Travisdaman713 @aw_trades_ You set a PDPT which is simply a pending market order awaiting a trigger event. It triggered on the low liquidity news event (in your favor), and exited you where it could at the current best market price.

[ProjectX @projectxtrading]

@crypt0_reaper @Tradovate It was isolated to a single load balance and did not effect all data recipients.

[ProjectX @projectxtrading]

Today, at 12:39 CT, an upstream market data load balancer failed at the CME Chicago data center. This caused market data to stop flowing into our platform until 12:45 CT when fail-overs kicked in. The issue was resolved and the faulty hardware replaced.

[ProjectX @projectxtrading]

Slippage Comparison Test #2 using stop market orders:

FOMC Minutes (High Volatility period) 7/30/2025

ProjectX: 1 tick slippage (execute @ 23562 fill @ 23562.25)
Tradovate: 1 tick slippage (execute @ 23562 fill @ 23562.25)

[ProjectX @projectxtrading]

@TheSeanTrades Hint: it's not "everyone" :)

[ProjectX @projectxtrading]

Slippage Comparison Test using stop market orders:

FOMC Event 7/30/2025

ProjectX: 2 ticks on each order
Rithmic: 12 ticks order #1 / 14 ticks order #2
Tradovate: 4 ticks order #1 / 2 ticks order #2

[ProjectX @projectxtrading]

@zoofxing We understand your concern, but this claim is entirely inaccurate. You can verify your fills against CME raw tick data at any time to see the exact market conditions, ( bid/ask order book). This is possible because, unlike forex, futures trade on a single centralized exchange