Deployment Options¶

There are two deployment options for 3LC. Regardless of which you choose, your ML data never leaves your infrastructure.

For most cases, we recommend the Default deployment. It uses services hosted by 3LC Inc. to manage user accounts and workspaces, and 3LC usage is authenticated using a 3LC workspace API key. The servers for the frontend components (3LC Hub Frontend Server, 3LC Dashboard Server) - which provide the static web resources (HTML and JavaScript) to render them in the browser - are also hosted by 3LC, with the latest versions available at https://hub-beta.3lc.ai and https://dashboard.3lc.ai.

The Enterprise On-Prem deployment can be used for running 3LC in isolated environments with restricted access to the public internet. There are no user accounts or workspaces, and 3LC usage is authenticated using a coarser license key. The servers for the frontend components (3LC Hub Frontend Server, 3LC Dashboard Server) are hosted internally in the enterprise infrastructure, and maintenance is necessary to update as new versions are released.

Click on the tabs below to compare the deployment options.

../../_images/default-deployment-components.png
  • Users pip install the 3lc wheel from the 3LC public package index

  • Users create accounts at https://account.3lc.ai and use associated API keys to authorize use of the tlc Python Package and 3LC Object Service

  • 3LC hosts the 3LC Hub Frontend Server and 3LC Dashboard Server that provide static UI resources for the latest version of the 3LC Hub and 3LC Dashboard

  • Users access 3LC in their browser by going to https://hub-beta.3lc.ai and https://dashboard.3lc.ai

../../_images/enterprise-on-prem-components.png
  • Users pip install the 3lc-enterprise wheel (with dependencies 3lc and 3lc-dashboard) from a 3LC private package index

  • Users pip install the 3lc-hub-frontend wheel from a 3LC private package index

  • Users use license keys provided directly from 3LC to authorize use of the tlc Python Package and the 3LC Object Service

  • The enterprise runs the 3LC Hub Frontend Server and 3LC Dashboard Server in its own infrastructure to provide the static UI resources for a particular installed version of the 3LC Hub and 3LC Dashboard at URLs accessible to users

  • Users access 3LC in their browser by going to the URLs where the 3LC Hub Frontend Server and 3LC Dashboard Server are running inside the enterprise infrastructure