Skip to content


This page lists software and hardware requirements for eccenca Corporate Memory deployments. For a general overview of a deployment setup please refer to the System Architecture.

Minimal Setup¤

A minimal single-node deployment for testing/evaluation purposes means:

  • no memory consuming linking and transformation workflows,
  • nearly no concurrent users.

Depending on how much RAM is dedicated to the triple store, Knowledge Graphs up to several million triples can be built and served.

  • Operating System / Hardware
    • Bare metal server or VM with Debian based linux OS (see Installation for details)
    • 16 GB RAM
    • 100 GB free disk space (10 GB for docker images + data + logs over time)
    • docker and docker-compose (we deliver an orchestration including all needed components)

For an example of a single-node installation refer to the following scenarios:

Typical Setup¤

In a typical deployment all components are installed on separate VMs (nodes). Therefore, six separate VMs are required.

The following numbers are based on existing customer deployments running Knowledge Graphs up to 300 million triples with 40 concurrent users.

Component CPU Memory
eccenca DataPlatform >= 4 cores1 >= 8 GB RAM
eccenca DataIntegration >= 4 cores2 >= 8 GB RAM2
eccenca DataManager 2 cores >= 2 GB RAM
Triple / Quad Store >= 4 cores1 >= 8 GB RAM3
Keycloak incl. PostgeSQL4 2 cores >= 4 GB RAM
Proxy Server4 >= 2 cores1 >= 2 GB RAM


Browser / Web Client¤

We support all (LTS/ESR) versions of the below listed browsers that are actively supported be the respective publishers:

  • Microsoft Edge > v88.0
  • Google Chrome or Chromium > v92.0
  • Firefox > v78.0


Internet Explorer 11 as well as Safari Browser are not officially supported. IE11 is reported not to work.

Command Line Client (cmemc)¤

cmemc is supported by the following Python versions: Python Version

There is also a docker image available.

  1. Needs to be scaled with concurrent users. 

  2. Depends on the DataIntegration workflows. 

  3. Needs to be scaled with the amount of triples. 

  4. In cloud deployments, this could / will be a cloud service.