Components and Data Privacy¶

3LC is composed of three main components:

  • The Python Package used to integrate with your existing ML code to capture metrics during training

  • The Object Service used to provide the Dashboard access to ML training data and metrics captured during training, requires access to the same storage backend as the training

  • The Dashboard web application used to analyze and make revisions to ML training data and metrics in the browser, with ML data accessed through the Object Service

../_images/main-components.png

Data Privacy¶

The component architecture of 3LC has been intentionally designed to ensure that your ML data never leaves your infrastructure. Your ML data, including the metrics captured during training using the tlc Python Package, are stored in locations (on local drive(s), network drive(s), and/or cloud storage) that you control. They are never uploaded to 3LC in any form.

The 3LC Object Service always runs on your own infrastructure, indexing your ML training data and metrics to make them available to the 3LC Dashboard. The 3LC Dashboard itself is a web application running in the browser on your own machine.

The 3LC Dashboard needs two things to allow you to analyze and edit your ML training data and metrics. First, it needs the data itself, which it accesses through the Object Service running on your machine. Second, it needs the static web resources (HTML and JavaScript) used to render the UI, which it pulls from the 3LC Dashboard Service. The 3LC Dashboard Service may be hosted by 3LC or in your own infrastructure depending on deployment, but in either case it is just the source of those static web resources and never receives any data.