You can deploy Atfinity in a Kubernetes Cluster. For this, we provide a helm chart, that also includes descriptions of necessary dependencies.

Note: All support files and credentials are available via your dedicated support agent.


Atfinity needs a Kubernetes cluster (as of writing at least Version 1.25.11) that can be prepared to run Atfinity. It needs to be possible to install a custom ingress and cert manager in the cluster. If you would like to run an external database (MariaDB and MySQL, inquire for versions) those also need to be available in a recent version. Apart from that, no further components are required.

Preparing the cluster

Atfinity needs a few components to be installed in the cluster.

  • Atfinity Registry Secrets (will be provided through your support agent)

  • NGINX Ingress

  • Cert Manager

Our readme file outlines our recommended installation procedure.


Once you have all the necessary credentials and a prepared cluster, you can install or upgrade a release like this

helm upgrade --install NAME oci://atfinity.azurecr.io/helm/atfinity --version 11.1.0

Make sure to change the version to the one you would like to install

List and description of Pods

"api" Pod

This pod runs the backend of Atfinity. It provides the API for both external systems and the Atfinity Frontend. This pod mounts a persistent volume to store all uploaded files.

"mariadb" Pod (optional)

This runs a MariaDB, to be used as the Atfinity database if you do not choose the external option. All data points about configuration and clients will be stored here. The pod uses a persistent volume for the database.

"elastic" Pod

An ephemeral Elasticsearch is used to provide overviews and full text search.

"web" Pod

This runs a hardened nginx server to serve the web frontend application.

Routes overview (ingress)

  • /api/1 serves the api backend

  • /auth/ serves the Atfinity login page

  • / serves the Atfinity web frontend

Last updated