Write Python in the browser
Completion, go-to-definition, run and debug in the same editor. Export the file and run it locally whenever you want.
Write in Python, backtest on built-in historical data, and connect to QMT, XTP or CTP through one interface. Research, validation and order routing share the same environment — no more stitching market data to a broker API yourself.
Reports settle daily. Export to CSV.
ILLUSTRATIVENot four open-source tools bolted together — one pipeline from market data to backtest to matching to order routing.
Completion, go-to-definition, run and debug in the same editor. Export the file and run it locally whenever you want.
Replays minute or tick data with slippage and commissions included.
Swap gateways without touching strategy code — only the binding changes.
Per-symbol limits, daily loss caps and available cash are enforced pre-trade.
Backtest and live read the same data source, so curves actually line up.
Strategy files are never locked in. Export, migrate, reproduce locally at any time.
Watchlist on the left, chart in the middle, orders on the right. Switching between backtest and live keeps the layout — only the data source changes.
One codebase for the backtest, another for live orders — and the moment matching logic, slippage assumptions or event ordering diverge, the pretty curve stops reproducing. LingBunny runs both through the same engine.
Placement, cancellation, partial fills and limit-up rejections all go through the same execution engine. There is no second implementation.
No storing ticks, no reconnect loops, no calendar or corporate-action maintenance. The platform handles it; your strategy only sees signals.
Export strategy files and run them on your own machine. Hosting is available, but your strategy is never bound to the cloud.
What you can actually trade depends on the permissions your broker or futures firm grants you. The table lists what the platform supports.
| Gateway | Market | Instruments | Connection | Status |
|---|---|---|---|---|
| QMT | A-shares | Shanghai/Shenzhen equities, ETFs, convertibles | Broker client | Supported |
| XTP | A-shares | Shanghai/Shenzhen equities, options | Broker counter | Supported |
| CTP | Futures | Commodity and financial futures | Futures counter | Supported |
| SIM | All markets | Same engine as live | Built in | Supported |
Gateway availability depends on whether your broker or futures firm has enabled the corresponding interface for your account. Confirm with your account manager before connecting.
The expense isn't only development — it's the daily consistency maintenance and incident handling.
| Concern | Self-assembled | LingBunny Quant |
|---|---|---|
| Market data | Integrate vendors separately You reconcile adjustment factors and halts yourself | Single data source One adjustment basis and calendar |
| Backtest vs. live | Two codebases Matching details drift; curves stop reproducing | Same matching implementation Switching modes only swaps data and gateway |
| Reconnection | Write your own watchdog and alerts Overnight drops are found the next morning | Hosted by the platform Crashed processes restart and log automatically |
| Risk controls | Patched in as you go Limits and cash checks get missed | Enforced before every order Per-symbol caps and daily loss limits are configurable |
| Operations | Servers, processes, logs on you | Cloud-hosted, or fully local |
| Time to first run | Weeks | First backtest the same day |
Bind a broker or futures account in the console and pick the matching gateway. Simulated accounts need no binding — usable right after sign-up.
Write the strategy in Python, set the universe and date range, then run. Review equity, drawdown, turnover and fills.
Once the backtest checks out, deploy the same file to a live gateway. Orders, positions and fills appear in the console in real time.
Backtest and live share the matching implementation. Switching modes does not rewrite the strategy or change its parameters — only where quotes and orders come from.
The strategy itself is Python. The platform ships templates and wrappers for market data, order placement and positions, so a dual moving-average strategy is about 20 lines. You don't handle tick storage, connection management or the trading calendar.
Strategy files live under your account and can be exported at any time. We don't use customer strategies for proprietary trading or provide them to third parties. If the code must never leave your machine, use local runtime — the cloud only provides data and gateway access.
It depends on whether they offer QMT, XTP or CTP and have enabled it for your account. Most major brokers offer QMT; futures firms generally offer CTP. Confirm your permissions with your account manager before connecting.
Yes. Historical data used in backtests and real-time data used in live trading come from the same source, with identical adjustment and calendar handling — so results don't drift due to inconsistent data.
Simulated backtesting is free. Live hosting is billed by the number of running strategies and excludes trading fees charged by your broker or futures firm. See the subscription page in the console for current pricing.
Cloud strategies don't depend on your local machine or connection. The platform monitors each process and restarts crashed ones automatically, with logs. Positions are not liquidated automatically in extreme cases — you'll need to confirm in the console.
Simulated backtesting needs no account binding. Sign up and start.
No credit card · Unlimited strategies in simulation