Self-Managed Features

This article describes the options and features provided for self-managed LILT deployments.

LILT Platform Features

The features listed below can be enabled/disabled during the LILT installation process.

LILT Application Feature	Functionality
Audit logging	Logs database and access events received by the LILT Platform. Users can perform an audit of the application by querying the logs for events of interest, such as database access or API access.
Custom UI banners	The following aspects of the LILT Platform UI header and footer can be changed • Header text • Footer text • Text color • Background color Custom UI banners does not support images. Custom UI banners can be updated at any time.
Document security scan	All files uploaded into LILT are scanned for malicious threats. The scan is performed against the Clam AntiVirus image. Document security scanning is not supported for files uploaded into LILT via API.
Hard delete	When deleting documents and projects, segment information is permanently removed from the system.
Instant translate documents and Instant translate text	Users can utilize the organization’s Translation Memories to quickly translate documents and text blocks outside the LILT Translate.
Single sign-on (SSO)	Users can authenticate to the LILT Platform using an identity provider other than LILT.
Segment logging	Segment information is logged in the Platform’s backend logs. Admin can enable/disable this feature at any time.

Technical features

Super admin user

Functionality: The super admin user is the initial Platform user with administrative privileges. It has admin privileges only inside its own organization. Configuration: By default, the super admin user is set to admin@LILT.com, but can be changed during the initial LILT installation process.

GPU batch worker count

Functionality: GPU batch workers are used for parallel batch processing. GPU batch workers speed up document processing by providing quicker translations and memory updates. Configuration: The following GPU batch worker settings can be set for the cluster:

maximum number of GPU batch workers
number of standby GPU batch workers

The optimal number of GPU batch workers is dependent on the available resources and the organization’s translation workflow. Optimal configuration will speed up parallel batch processing operations.

Minimum segments count for GPU batch workers

Functionality: Each document must meet or exceed a minimum segment count before a GPU batch worker will process the document. Configuration: Batch-related custom configurations are available to set the minimum segment count. Since GPU resources are limited in availability, care should be taken when setting the minimum segment count so that GPU usage benefits your workflow and is not just a resource drain.

Persistent data location

Functionality: The persistent data location is used to store persistent data for LILT and the applications listed below in the Infrastructure applications section. Data is stored and retrieved from this location during application usage. Data is not removed if the applications are deleted. Configuration: The admin can configure the persistent data location during the LILT Platform installation. The volume should be attached to the Kubernetes worker nodes. The volume cannot be updated without destroying the cluster.

Host name

Functionality: The host name is used to access the LILT Platform. Customizing the host name allows for each organization to create a host name that can be easily remembered by the organization’s members. Configuration: The host name can be specified during the LILT Platform installation and can be updated at any time after installation. When configuring the host name, failure to provide a valid SSL certificate and key for the host name will result in SSL error and inability to access the LILT Platform.

Infrastructure applications

For self-managed installation of LILT, the applications below are also installed to enable LILT to function:

MinIO: object storage server
OpenEBS: local persistent volume provisioner
MySQL: relational database
MongoDB: audit logs database
ClickHouse: analytics database
Elasticsearch: search and indexing
Qdrant: vector database
Redis: data structure caching
RabbitMQ: message queue
Istio: service mesh and ingress gateway, deployed in ambient mode (per-node ztunnel proxy for transparent mTLS, no sidecars)
MetalLB: bare-metal LoadBalancer that provides the external IP for the Istio ingress gateway
Argo CD: GitOps continuous delivery for managing in-cluster releases
KubeRay: Kubernetes operator for Ray distributed compute
Prometheus: metrics collection
Nvidia-device-plugin: GPU management in Kubernetes

​LILT Platform Features

​Technical features

​Super admin user

​GPU batch worker count

​Minimum segments count for GPU batch workers

​Persistent data location

​Host name

​Infrastructure applications