QuantConnect: algorithm development, live infrastructure and data rights

The organization model accommodates independent developers, academics, emerging managers and teams building quantitative investment systems. Members can share computing, datasets and projects. The Free tier supports research and backtesting; paid tiers add development interfaces, collaboration and resources for live strategies. Team size, collaboration rights and node ceilings are separate features, so a higher resource allowance does not itself purchase the additional machines.[2]

Research data spans equities, options, futures, foreign exchange, CFDs, cryptocurrencies, indices and alternative datasets. Coverage needs to be selected at dataset level, including its history, resolution and licence. A strategy’s historical research universe and the instruments it can trade through a particular live connection can differ.[1]

Terminal Link is a QuantConnect add-on; the provider expressly says that Bloomberg does not endorse it. The cloud EMSX route and the local desktop route also have different data arrangements. This distinction matters when moving an existing Bloomberg-based workflow: an execution connection is not enough to establish that every research or live-data entitlement transfers with it.[8]

The CLI can authenticate to the QuantConnect API, synchronize projects and submit cloud jobs from a local workflow. Local engine execution also depends on Docker. Developers should match the brokerage integration’s supported functions to the intended environment before installing and configuring the trading stack.[3]

Pricing is built from organization seats, computing, add-ons, market subscriptions and support seats. The billing documentation offers suggested bundles or a custom configuration, with monthly or annual billing. The displayed setup is therefore a collection of resources rather than a universal all-in price for every deployment.[11][10]

A commercial comparison should preserve the selected billing period, node models, data permissions and support seats. The reviewed configurator exposed the resource structure and the onboarding starting charge, but did not consistently return the dynamic recurring prices. A verified recurring-cost example therefore needs a dated configuration or quote; a seat-only figure would omit material parts of the service.[10]

Exit choices have different consequences. The billing guide’s cancellation confirmation specifies termination at the end of the current billing cycle and says live nodes will stop. A downgrade to Free permanently deletes backtest results, logs, Object Store contents and projects exceeding Free limits. A one- or two-month pause preserves the configuration but suspends access.[11]

The billing guide provides routes to retain project code and results before cancellation. Object Store exports require an eligible Institution organisation; permitted use also depends on the data licence.[11][18]

In a local development workflow, install the CLI’s Python-package prerequisites and Docker, authenticate, and initialize the organization workspace. That workspace holds the configuration and project structure used for synchronization. These are software setup steps; the selected live brokerage still supplies the credentials and functionality described in its integration guide.[3]

Private Cloud adds a central work queue and one or more corporate work servers. Developers use the QuantConnect extension in VS Code while jobs execute against centralized computing and data. The published setup creates the master work server, adds further servers where required, and connects the team’s clients. This is a distinct infrastructure project from using the hosted web environment.[5]

Restart behaviour is a material deployment requirement. LEAN initializes a new algorithm instance after a stop and redeployment or an automatic recovery. Cash and holdings are recovered from the brokerage; QuantConnect Paper Trading pre-fills its saved cash and holdings in the deployment wizard. Open-order recovery depends on the connector, and QuantConnect Paper Trading does not restore open orders. Indicators, class variables and strategy-specific state need rebuilding or explicit persistence. The guide recommends warming up data-driven state, saving other required state in the Object Store and checking recovery during paper trading.[13]

QuantConnect’s reconciliation view compares live results with an out-of-sample backtest. Differences can arise from data timing, custom-data availability and the way live events arrive. The documented time frontier reduces look-ahead problems but cannot correct a custom dataset whose timestamps disclose information before it was available. An acceptance exercise should therefore compare orders, fills and data availability, alongside the equity curves.[9]

Private engineering tickets require a support seat. QuantConnect publishes Bronze, Silver and Gold tiers with a rolling one-month ticket allowance. The human team operates Monday to Friday; the AI assistant is available continuously. The response figures below are the provider’s published support descriptions and should be matched to the purchased contract rather than treated as a universal resolution deadline.[15]

This profile covers software, data access and hosting for quantitative trading. QuantConnect describes its execution role as routing instructions to the customer’s brokerage. Brokerage-account permissions and the relevant execution relationship remain specific to that connection. The technology subscription is not evidence that every brokerage instrument, jurisdiction or customer category is available through the platform.[17][7]

Data rights require particular care. The 8 October 2026 terms restrict Platform Data to the hosted environment, including derivatives from which original values can be reconstructed or approximated. Permitted export routes are separately purchased CLI downloads under the applicable agreement, or institutional Object Store downloads under a signed Derived Data Agreement. Owning strategy code does not confer unrestricted rights to export the underlying datasets.[18]

The current site terms identify QuantConnect Corporation as the operator. Version 1.5 is dated 8 October 2026 and incorporates additional platform and subscription agreements. The LEAN engine’s separate open-source licence is published in the official code repository; it should be distinguished from the commercial site, service and data contracts.[18][4]

QuantConnect says code is private by default and remains the user’s intellectual property. Its support workflow can grant a named engineer access to a project, while posting code to a public forum changes who can see it. The documented encryption feature protects stored code with a locally held key. For a firm, project-sharing and support-access choices therefore belong in the implementation design.[17]

Operator

QuantConnect Corporation

Service scope

Algorithm development, research data, backtesting and live-running infrastructure built around LEAN. Hosted and local configurations have separate computing, data and brokerage requirements.

Customer types

Quantitative trading teams; Emerging investment managers; Financial institutions; Independent algorithm developers; Academic researchers

Delivery

SaaS; Hosted; On premises; API; Hybrid

Pricing publication

Public and quoted pricing

Platforms

QuantConnect Cloud; LEAN; LEAN CLI; Local Platform; Private Cloud; LEAN Enterprise; Terminal Link

Integrations

OANDA brokerage integration; Bloomberg EMSX through Terminal Link; Visual Studio Code

Pricing scope

Public configurable subscriptions and an advertised onboarding starting charge; a complete recurring price depends on the selected resources and service scope.

Implementation

Configure an organization, development environment, computing and licensed data, then authenticate the brokerage connection. Local CLI use requires a paid organization; Private Cloud adds corporate servers and an Institution add-on.

Support

Published contact email and private engineering tickets through support seats. Bronze, Silver and Gold have distinct allowances; the human team operates Monday to Friday.

Permissions and regulatory scope

Software, data and hosting scope. Instructions are routed to the customer’s brokerage; the subscription does not establish account-level execution permissions. Data exports require the applicable contractual rights.

Provider metadata checked 20 Oct 2026Source 1Source 2Source 3Source 5Source 10Source 15Source 16Source 18Source 17Source 8Source 4Source 6Source 7

The current AI workflow includes agents for ideas, research, backtesting, paper testing and live monitoring, with Mia as an assistant. Permissions separate read and write access by domain, and the live-trading domain requires an explicit write grant. The listed create_live_algorithm tool deploys to QuantConnect Paper Trading. In chat mode, file and notebook changes require human approval with a diff preview. Agent budgets, tool permissions and code review therefore need separate configuration.[19]