Legion tries to unify process of training, building and deploying ML/AI models, splitting them to 3 main phases.
Legion provides an ability to develop applications/tools that can be used for these phases. These applications are:
For cloud use case, these applications/tools have to be registered in Legion Platform using:
These registrations are required to have an ability to integrate training / packaging process with other subsystem Legion provides too (e.g. :term:`Model Training Metrics`, :term:`Model Training Tags`).
As an intermediate format for storing trained models Legion Platform declares :term:`Trained Model Binary Formats <Trained Model Binary Format>` for different languages.
Nowadays, Legion Platform declares:
There are ready for use :term:`Toolchain Train Integrations <Toolchain Train Integration>` and :term:`Toolchain Packaging Integration <Toolchain Packaging Integration>`:
- :term:`MLflow Model Training Toolchain Integration`
- :term:`Docker REST API Packaging Toolchain Integration`
But Legion Platform users are not limited to set of predefined :term:`Toolchain Train <Toolchain Train Integration>` and :term:`Toolchain Packaging <Toolchain Packaging Integration>` integrations and are free for installation of third-party integrations.
Legion subsystems are:
These subsystems are optional, and can be deployed not just inside Legion Cloud, but even in other products.
For integration with Legion, there are libraries and plugins:
- :term:`Python SDK Library`
- :term:`Legion CLI`
- :term:`Plugin for JupyterLab`
- :term:`Plugin for Jenkins`
- :term:`Plugin for Airflow`
Legion Platform can be installed locally or on Kubernetes cluster.