Local Platform

• Share access to centralized servers with expensive specialized hardware. Set up a powerful server with plenty of RAM, CPU, and GPU resources for your team to build and train the latest models.
• Provide distributed teams with safe, monitored access to proprietary data. Centralizing data allows your team to access it without the potential for distribution.
• Keep infrastructure costs low by reducing total hardware expenses and making better use of hardware.

To use a Private Cloud, you need an Institutional Subscription to the Local Platform with the Private-Cloud Add-On. This is licensed per server and supports scaling up to 10 servers. If you're interested in this solution, make an appointment with our team to discuss if it will work for your fund.

For full pricing information, see the Pricing page.

The following image describes the Private cloud infrastructure:

Clients run research notebooks, backtests, optimizations, or live trading strategies on their laptops using the QuantConnect extension in VSCode. The work runs on the centralized servers utilizing the centralized data and powerful servers inside the corporate local network. Results are streamed back to the Local Platform user interface so the quant can research as before.

To deploy a private cloud, follow these steps:

Set up a Master Work Server

1. Install and authenticate the LEAN CLI.
2. Run the lean private-cloud start LEAN CLI command to start a work queue and listen for jobs from the team.
   

   $ lean private-cloud start --master --stop --master-domain {example.master.domain} --compute="[{\"count\":3,\"type\":\"both\"}]" --token {token}

If you are setting up a single server, this is all you need to do.

If you don't provide the --token, LEAN CLI generates one. If you don't define the --compute, LEAN CLI prompts for configuration options. The --stop optional argument stops any previous deployment (see lean private-cloud stop).

3. To expand the private cluster further so work is distributed across many servers, install the LEAN CLI into the second server and run lean deploy private-cloud --slave.
   

   $ lean private-cloud start --slave --master-domain {example.master.domain} --slave-domain {example.slave.domain} --compute="[{\"count\":2,\"type\":\"both\"}]" --token {token}

This will spin up the second work-server to consume jobs.

Set up a Team Thin-Client

1. On the quant analyst's computer, install the Local Platform.
2. Install and authenticate the LEAN CLI.
3. Open a QuantConnect project inside the VSCode extension and select the Private Cloud deployment target.
4. Enter the IP/DNS of the master-work server provided when running the LEAN CLI start-up command.