Docker Compose

Atfinity can run on a multi VM setup. While the setup is battle-tested and used by a few clients, we recommend, whenever possible, to use our Kubernetes Setup to deploy Atfinity on your infrastructure.

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


Atfinity can be deployed as either a one, two or three tier architecture:

  1. All in one publicly or internally available CORE server (application and storage)

  2. A publicly or internally available CORE server and a specially protected storage server (two tier).

  3. A publicly or internally available CORE server.

This diagram details containers and communication between them:

Required setup

The atfinity backend is available as a collection of Docker containers and one or two Docker Compose files binding these together. If you choose to run the Digital Form Tool separately, there is a second Docker Compose file for its web server, too.

Required Services

atfinity services will communicate with a MariaDB database and an NFS file storage to permanently store data. In addition, atfinity uses a ephemeral Redis to cache certain data for a short period of time. This means, you will have to install and provide the following services:

CORE Server

  • Docker (~v24.06)

  • Docker Compose (~v2.21.0)

DATA Server

  • MariaDB (~10.6)

  • NFS File Storage

For performance, it is critical to make sure these servers have enough resources to run the required services and the application.


atfinity is able to handle various firewalls between the components. It is critical though, that transport between the tiers is possible and of good performance. The above diagram and the respective documentations of used tools, gives an overview of needed ports.

Approximate Port Map (Adapt for your circumstances)

From / To





443 (actual communication), 80 (let's encrypt setup)


3306 (SQL), 111+2049 (NFS)


We are happy to assist you, but since the spectrum of firewalls and other tools is huge, ultimately it’s within the clients responsibility to make sure tiers are configured correctly.

Last updated