Platform Paper Trading vs. IBKR Live: Key Differences
Understand what changes when you graduate from paper trading on this platform to live execution on Interactive Brokers. Learn the gaps you must close before risking real capital.
From Paper to Live: What Actually Changes?
Paper trading on this platform gives you instant, frictionless fills at the last market price, unlimited capital, and zero latency. That is intentional — the goal is to validate your signal logic, not to simulate every edge case of production infrastructure. But when you move to IBKR live trading, every one of those conveniences disappears.
Side-by-Side Comparison
| Dimension | Platform Paper Trading | IBKR Live |
|---|---|---|
| Order Execution | Instant fill at last price | Routed through SMART routing; fill depends on liquidity |
| Slippage | Zero (fills at exact signal price) | 0.01–0.10% per trade on liquid stocks; more on options |
| Partial Fills | Never — always complete fills | Large orders may fill across multiple prices/time |
| Market Hours | Optional (configurable) | Strictly enforced by IBKR; pre/after-market limited |
| Capital | Virtual $100K–$2M | Your actual funded account balance |
| Margin / Buying Power | Not enforced | Pattern Day Trader rules, margin calls, overnight rates |
| Data Feed | End-of-day EODHD historical bars | Real-time tick + L2 data (requires subscription) |
| Latency | Milliseconds (API call) | Round-trip to IBKR servers ~10–50ms |
| Risk Controls | None required | Hard stops, max loss limits, position limits mandatory |
| Cost | Free | $0.005/share (min $1) equities; $0.70/contract options |
| Connection | Always available | TWS/IB Gateway must be running on a live machine |
| Error Handling | Graceful simulation | Network drops, timeout rejections, rate limits in production |
The Three Biggest Surprises for Paper-to-Live Traders
Surprise #1 — Slippage Kills Edge
A strategy that returns 18% annually in paper trading may return 6% live once you account for the bid-ask spread on every entry and exit. If your average trade profit is $0.50/share and your average spread is $0.08, you are giving away 16% of your edge per trade. Always model slippage before going live.
Surprise #2 — TWS Must Stay Running
IBKR's Python API connects to Trader Workstation (TWS) or IB Gateway running locally. If TWS crashes, your algorithm stops receiving data and cannot place orders. In production, you need IB Gateway running on a dedicated server (Railway, VPS) with auto-restart configured.
Surprise #3 — Pattern Day Trader Rule
If your account has less than $25,000 and you execute 4+ day trades in a 5-business-day rolling window, IBKR will flag you as a Pattern Day Trader and restrict your account. Swing strategies (hold overnight) avoid this; intraday strategies require $25K+ funded accounts.
What Transfers Directly from Paper to Live
- Your signal logic: SMA crossover, RSI thresholds, breakout detection — all identical
- Position sizing formulas: percentage-of-capital, Kelly Criterion — identical math
- Stop-loss and take-profit levels: same logic, just enforced via real orders
- Backtested performance statistics: still valid as a reference point (after slippage adjustment)
- Entry/exit timing rules: same conditions trigger, just on live price feed
The IBKR Architecture
IBKR exposes a TCP socket API. You never talk to IBKR directly from Python — instead, you connect to TWS or IB Gateway running on your machine (or server), which then handles the communication with IBKR's servers. This is a critical architecture difference.
Your Python Script
│
│ (TCP socket, port 7497)
▼
Trader Workstation (TWS) / IB Gateway
│
│ (IBKR proprietary protocol)
▼
IBKR Servers → Exchange → FillThe practical implication: your Python bot cannot run "standalone." It needs a TWS/IB Gateway process to connect to. When deploying to Railway or any server, you run IB Gateway headless alongside your Python process.
Pre-Live Checklist
- Verify your paper strategy is profitable over at least 6 months of simulation data
- Run the same strategy on IBKR Paper Account (IBKR has its own paper environment) for 30 days
- Audit your code for look-ahead bias, hardcoded prices, and timezone issues
- Add hard circuit breakers: max daily loss, max open positions, max single-position size
- Test TWS/IB Gateway connectivity on your deployment server
- Configure auto-restart and alerting (email/SMS on errors)
- Start with 10% of intended capital; scale up after 60 days of live consistency
Rule of Thumb: Paper ≥ 3 Months Before Live
Three months gives you enough data to see the strategy through different market regimes (trending, choppy, volatile). If it is profitable for 3 months of paper trading with at least 30 trades, it is worth deploying with 10% of intended capital. Less than that and you are gambling on sample noise.
- Paper trading abstracts away order routing, margin, and fill mechanics
- IBKR requires TWS or IB Gateway running locally or on a server
- Slippage, partial fills, and data latency behave very differently live
- Risk controls that are optional in simulation become mandatory in production