Skip to main content

TradersPost Deep Dive & Gap Analysis

1. The Core Divergence: “Cloud API” vs “Local Bridge”

The most critical finding is structural. TradersPost is a Cloud-to-Cloud platform. It connects to brokers that offer Modern REST APIs (Tradovate, TradeStation, Alpaca, Kraken). The Prop Firm Gap:
  • TradersPost Target: Futures Prop Firms (Apex, Topstep) -> Use Tradovate/Rithmic (API available).
  • Certio Target: Forex/CFD Prop Firms (FTMO, The5ers) -> Use MetaTrader 4/5 (No API available).
Implication: TradersPost CANNOT natively serve the FTMO/MetaTrader market without complex, unsupported third-party middleware. This is Certio’s “Blue Ocean.”

2. Feature-by-Feature Gap Analysis

Feature CategoryTradersPost (The Benchmark)Certio (Current Status)Gap / Opportunity
ConnectivityDirect API (No VPS)Local Bridge (VPS Req)Neutral: We serve different markets. We cannot do “Direct API” for MT4 because it doesn’t exist.
DashboardRead/Write (Close Positions, Flatten)Read-Only (Logs + Panic Button)CRITICAL GAP: Users expect to “Manage” trades from the cloud. We need to add “Close Position” buttons to our Dashboard.
Trailing StopsServer-Side Engine (Calculated in Cloud)Local-Side (Relies on MT4 or Simple Logic)Opportunity: Certio’s “Local Bridge” is better for this because it works even if Cloud disconnects. We should market this “Edge Execution”.
Partial ExitsStateful (Tracks Position Size)Stateless (Fire & Forget)Minor Gap: TP tracks “I bought 10, sold 5, remaining 5”. Certio sends “Close 0.5”. If user manually closed some, Certio might error.
SafetyCloud-Only (Vulnerable to Broker disconnect)Zombie Guard (Orphan Protection)Certio Win: Our “Zombie Guard” works even if the Internet dies locally. TP relies on the Broker’s API being up.
Pricing$49/mo (Expensive)$19-29/mo (Target)Certio Win: We are priced for the mass market “Challenge” trader.

3. The “VPS Integration” Myth

The user asked about “VPS Integration”.
  • TradersPost: Does not integrated with VPS because it doesn’t need to (for its supported brokers).
  • PineConnector: Sells a “Recommended VPS” affiliate link.
  • Certio: Must provide a Dockerized or One-Click installer.
    • Recommendation: Certio should effectively “Bundle” the VPS physically or virtually. “Certio Cloud” could be a managed VPS service we upsell ($20/mo) where we host the bridge for them.

4. Strategic Recommendations

A. The “Smart Dashboard” (Priority: High)

TradersPost allows users to “Flatten All” or “Close Trade #123” from the web UI. Action: Upgrade Certio Dashboard from “Monitor” to “Controller”.
  1. Add Close Trade button next to active logs.
  2. Send {"action": "CLOSE", "ticket": 123} signal to Redis -> Bridge -> MT4.

B. The “State Engine” (Priority: Medium)

TradersPost knows exactly what the user owns because they query the Broker API. Certio is currently “Blind” (we only know what we sent). Action: Implement Two-Way Sync.
  1. Bridge (MT4) polls OrdersTotal() and sends “Snapshot” to Redis every 5s.
  2. Dashboard displays “Real-Time Equity” and “Open Positions” (not just signals).
  • Note: This closes the feature gap with TradersPost’s “Portfolio View”.

C. Marketing Pivot

Stop comparing Certio to TradersPost directly.
  • TradersPost = The “Ferrari” for API Traders (Stocks/Futures).
  • Certio = The “Tank” for Prop Traders (Forex/MT4).
  • Slogan: “TradersPost is for Futures. Certio is for Funding.”

D. Long-Term Vision: The “Universal Bridge”

We are not technically limited to MT4. We can and should target API brokers (Tradovate, Binance) to become the ultimate “All-in-One” bridge. The Hybrid Architecture:
  1. Ingress (Standard): Receives Signal -> Queues in Redis.
  2. Route A (Legacy/Prop): Redis -> Bridge Client -> MT4 (Current Product).
  3. Route B (Modern/API): Redis -> Gateway Service -> Broker API (Future Expansion).
Why MT4 First?
  • Blue Ocean: 90% of Prop Firms block APIs. TradersPost abandons this market.
  • Win the Hardest Problem: Building a reliable “Local Bridge” is hard. Broker APIs are easy. If we win MT4, adding Tradovate later is trivial.

5. Conclusion

We are not “behind” TradersPost technically; we are effectively building “TradersPost for the Legacy Web”. The biggest actionable gap is Two-Way Sync (Dashboard Visibility of live open positions).