--- title: "Data Providers" description: "Data providers provide a stream of asset prices and quotes delivered to your trading algorithm during live execution." canonical: https://www.quantconnect.com/docs/v2/writing-algorithms/live-trading/data-providers markdown: https://www.quantconnect.com/docs/v2/writing-algorithms/live-trading/data-providers.md language: python source: https://github.com/QuantConnect/Documentation/tree/master/03%20Writing%20Algorithms/40%20Live%20Trading/03%20Data%20Providers modified: 2026-10-30 index: https://www.quantconnect.com/llms.txt --- # Data Providers [Documentation](https://www.quantconnect.com/docs/v2.md) > [Writing Algorithms](https://www.quantconnect.com/docs/v2/writing-algorithms.md) > [Live Trading](https://www.quantconnect.com/docs/v2/writing-algorithms/live-trading.md) > Data Providers > Code examples are shown in Python. Append `?lang=csharp` to this URL for the C# version of this page. ## Introduction Data providers provide a stream of asset prices and quotes delivered to your trading algorithm during live execution. You need live data provider to inject data into your algorithm so that you can make real-time trading decisions and so that the values of the securities in your portfolio update in real-time. You can source data from QuantConnect, brokerage, or a third-party source. To view the available data providers you can use in QuantConnect cloud, see [Datasets](https://www.quantconnect.com/docs/v2/cloud-platform/datasets.md). To view the available data providers you can use with local algorithms, see the [Data Providers](https://www.quantconnect.com/docs/v2/lean-cli/live-trading/data-providers.md). ## Data Providers You can source data from QuantConnect, your brokerage, or third-party providers. The following table lists the data providers: | Data Provider | Cloud | Local | | --- | --- | --- | | [QuantConnect](https://www.quantconnect.com/docs/v2/cloud-platform/datasets/quantconnect.md) | ![green check](https://cdn.quantconnect.com/i/tu/check.png) | | | [Alpaca](https://www.quantconnect.com/docs/v2/cloud-platform/datasets/alpaca.md) | ![green check](https://cdn.quantconnect.com/i/tu/check.png) | ![green check](https://cdn.quantconnect.com/i/tu/check.png) | | [Alpha Vantage](https://www.quantconnect.com/docs/v2/local-platform/datasets/alpha-vantage.md) | | ![green check](https://cdn.quantconnect.com/i/tu/check.png) | | [Binance](https://www.quantconnect.com/docs/v2/cloud-platform/datasets/quantconnect/crypto.md) | ![green check](https://cdn.quantconnect.com/i/tu/check.png) | ![green check](https://cdn.quantconnect.com/i/tu/check.png) | | [Bitfinex](https://www.quantconnect.com/docs/v2/cloud-platform/datasets/quantconnect/crypto.md) | ![green check](https://cdn.quantconnect.com/i/tu/check.png) | ![green check](https://cdn.quantconnect.com/i/tu/check.png) | | [Bybit](https://www.quantconnect.com/docs/v2/cloud-platform/datasets/quantconnect/crypto.md) | ![green check](https://cdn.quantconnect.com/i/tu/check.png) | ![green check](https://cdn.quantconnect.com/i/tu/check.png) | | [Charles Schwab](https://www.quantconnect.com/docs/v2/cloud-platform/datasets/charles-schwab.md) | ![green check](https://cdn.quantconnect.com/i/tu/check.png) | ![green check](https://cdn.quantconnect.com/i/tu/check.png) | | [Coinbase](https://www.quantconnect.com/docs/v2/cloud-platform/datasets/quantconnect/crypto.md) | ![green check](https://cdn.quantconnect.com/i/tu/check.png) | ![green check](https://cdn.quantconnect.com/i/tu/check.png) | | [FactSet](https://www.quantconnect.com/docs/v2/lean-cli/datasets/factset.md#10-Live-Trading) | | ![green check](https://cdn.quantconnect.com/i/tu/check.png) | | [Interactive Brokers](https://www.quantconnect.com/docs/v2/cloud-platform/datasets/interactive-brokers.md) | ![green check](https://cdn.quantconnect.com/i/tu/check.png) | ![green check](https://cdn.quantconnect.com/i/tu/check.png) | | [IQFeed](https://www.quantconnect.com/docs/v2/lean-cli/live-trading/data-providers/iqfeed.md) | | ![green check](https://cdn.quantconnect.com/i/tu/check.png) | | [Kraken](https://www.quantconnect.com/docs/v2/cloud-platform/datasets/quantconnect/crypto.md) | ![green check](https://cdn.quantconnect.com/i/tu/check.png) | ![green check](https://cdn.quantconnect.com/i/tu/check.png) | | [Polygon](https://www.quantconnect.com/docs/v2/cloud-platform/datasets/polygon.md) | ![green check](https://cdn.quantconnect.com/i/tu/check.png) | ![green check](https://cdn.quantconnect.com/i/tu/check.png) | | Samco | ![green check](https://cdn.quantconnect.com/i/tu/check.png) | ![green check](https://cdn.quantconnect.com/i/tu/check.png) | | [Theta Data](https://www.quantconnect.com/docs/v2/lean-cli/live-trading/data-providers/theta-data.md) | | ![green check](https://cdn.quantconnect.com/i/tu/check.png) | | [TradeStation](https://www.quantconnect.com/docs/v2/cloud-platform/datasets/tradestation.md) | ![green check](https://cdn.quantconnect.com/i/tu/check.png) | ![green check](https://cdn.quantconnect.com/i/tu/check.png) | | [Quant Bridge](https://www.quantconnect.com/docs/v2/lean-cli/datasets/quant-bridge.md#10-Live-Trading) | | ![green check](https://cdn.quantconnect.com/i/tu/check.png) | | [Tradier](https://www.quantconnect.com/docs/v2/cloud-platform/datasets/tradier.md) | ![green check](https://cdn.quantconnect.com/i/tu/check.png) | ![green check](https://cdn.quantconnect.com/i/tu/check.png) | | Zerodha | ![green check](https://cdn.quantconnect.com/i/tu/check.png) | ![green check](https://cdn.quantconnect.com/i/tu/check.png) | ## Bar Building We aggregate ticks to build bars. In live trading, bars are built using the exchange timestamps with microsecond accuracy. This microsecond-by-microsecond processing of the ticks can mean that the individual bars between live trading and backtesting can have slightly different ticks. As a result, it's possible for a tick to be counted in different bars between backtesting and live trading, which can lead to bars having slightly different open, high, low, close, and volume values. ## Latency Live data takes time to travel from the source to your algorithm. The QuantConnect latencies vary depending on the data provider. A much more significant source of latency is the round trip order times from brokers, which can vary from 100ms to 5 seconds. QuantConnect is not intended for high-frequency trading, but we have integrations to high-speed brokers if you need. ## History Requests In live trading, if you make a history request for minute data at noon and the history period covers the start of the previous day to the present moment, the data from the previous day will be backtest data. The data of the current day will be live data that we collected throughout the morning. If you make this history request in a backtest, you might get slightly different data for the current day because of post-processing from the data vendor. In cloud deployments, QuantConnect is the default data provider. If you remove it and use a different data provider, you won't get any price data from QuantConnect. However, we provide the following datasets: - [US Equity Security Master](https://www.quantconnect.com/datasets/quantconnect-us-equity-security-master) - [US Futures Security Master](https://www.quantconnect.com/datasets/quantconnect-us-futures-security-master) - [US Equity Option Universe](https://www.quantconnect.com/datasets/quantconnect-us-equity-option-universe) - [US Index Option Universe](https://www.quantconnect.com/datasets/quantconnect-us-index-option-universe) - Universe selection datasets - Non-streaming [alternative datasets](https://www.quantconnect.com/docs/v2/cloud-platform/datasets/interactive-brokers.md#07-Alternative-Data) ## Warm Up Periods LEAN supports an automated fast-forward system called "Warm Up". It simulates winding back the date you deployed your algorithm by a specific time period. In backtests, it changes the start date of your algorithm to an earlier time. In live trading, it fetches data from before your deployment and fast forwards through your strategy up to the present day. Warm Up is a great way to prepare your algorithm and its indicators for trading. You can't place trades during the warm-up period because the data feed is replaying historical data for setting algorithm state.