For the complete documentation index, see llms.txt. This page is also available as Markdown.

Hardware

We keep a Marple Installation Guide on gitlab for self-managed teams. Please find an overview of the general hardware requirements below.

The following requirements are sufficient for deploying both DB + Insight. Contact us for specific requirements in case only DB or Insight will be deployed. The storage limits are indicative and depend on your data size.

Common Requirements

  • CPU: 4 vCPUs

  • RAM: 16 GB

  • Storage: Minimum 64 GB (for data storage, exports, and logs)

  • Network: 100 Mbit/s upload and equal or better download speed

  • Operating System: Linux (x86 architecture; ARM is not supported)

  • Internet Access: Required to pull Marple container images

For Kubernetes Deployment

  • Cluster Setup: A running Kubernetes cluster

  • Pods: 1 pod with the above minimum specifications

  • Persistent Storage: 64 GB volume for data and logs

For Docker Compose Deployment

  • Host System: Bare metal or virtual machine

  • PostgreSQL: Required (either included in Docker Compose or an external database)

  • Environment Variables: Configuration for storage paths, database connection, and deployment name

Marple needs a Postgres database to work.

If you are using Docker Compose, a second container with the database is included by default. If you are using Kubernetes, or you just want to run the Postgres separately, you will need to run a dedicated Postgres instance.

  • Recommended Version: PostgreSQL 17

  • Minimum Resources: 2 vCPUs + 8 GB RAM

  • Azure-Specific: Ensure UUID_OSSP extension is enabled

  • For safety, it is recommended this database is only accessible by the server IP

  • Enable backups (eg 7 day retention)

Security

  • HTTPS recommended (e.g., reverse proxy in front of Marple)

  • VPN access preferred for additional security

  • Assign a fixed domain name (e.g., marple.yourcompany.com) instead of a raw IP

Last updated