Log In

Kili Technology has three deployments options:

Kili on Cloud (SaaS)

The easiest solution is to use Kili Technology cloud platform, with a Software as a Service model.

Both the platform and your data are hosted on our infrastructure.

The SaaS version of Kili is deployed with two different cloud providers:

  • Google Cloud, using a data center located in Belgium (Europe)
  • Azure, East US region located in Virginia

Kili on Cloud deployed in Azure Marketplace

You can deploy Kili as a managed application in Azure Marketplace, on a private Azure subscription. The deployed Kili instance is based on these associated Azure services:

  • Kubernetes cluster: Azure Kubernetes Services (three  Standard_D2as_v5 machines and one Standard_D4as_v5 dynamic pool)
  • Object storage: two Blob storage buckets
  • Relational database: Azure Database for PostgreSQL (Standard_D4ds_v4: 4 CPUs, 16 GB RAM, 128 GB disk space)

Updates to newer versions of the Kili application are managed automatically through the Azure marketplace, following the pace of the Long Term Support versions of Kili (updated twice a year).

To deploy Kili on Azure Marketplace, you must first create the resources that will interact with Kili.

The required resources are:

  • An Azure Machine Learning workspace
  • A compute instance to execute your notebook code

The required version of the compute instance depends on the scope of tasks that you're planning to execute using Kili. For simple data management tasks like project setup, labeled data access and management, a basic compute instance will be enough. For more advanced applications, like model-assisted labeling, you will need a a slightly more advanced instance.

For details and available plans, refer to the information in Kili Technology's overview page on Azure Marketplace.

Kili On-Premise

The third solution is to have Kili Technology on your own servers: on-premise.

System architecture

For details, refer to Kili architecture.


Hardware and software

Minimum configuration for 20 labelers or 5 reviewers:

For the services:

  • A Kubernetes cluster of at least 3 nodes for high availability (4 CPU and 12 GB RAM per node).

For the database:

  • A PostgreSQL v14 server (4 CPU, 16GB RAM, 100GB storage) with timescaledb plugin version 2.11.0 installed.

For the object storage:

  • An S3 compatible object storage solution (GCP cloud storage, Azure blob storage, AWS S3 or a local installation of Minio).

Additional Requirements

During the installation:

  • Internet access
  • Root access

There is no need for Internet/root access after installation.

The S3 compatible storage, the database and the Kubernetes cluster are accessible from collaborators' desktops.