Skip to content
SHC Docs

Catalogue vendor-minimum sweep (§45.6, ruled 2026-08-14)

Layer 6. Services. Services

One row per catalogue app that creates a container; the headless packages are listed separately below, and between the two every package under apps/ is accounted for. Cap is the primary (or tightest vendor-relevant) service. “Vendor min” is a published figure for that workload, not a host-size guess. “None published” means the vendor does not document a RAM floor; the shipped cap stands.

Floors that this sweep raised are marked BREACH→fixed. Caps that already cleared a published floor are OK. Caps that sit on a published floor were raised (sonarqube precedent: a minimum is a floor to clear).

Guards: tests/unit/catalog/resource_floors_test.go (named + class floors), tests/unit/catalog/host_sized_workers_test.go (the by-construction nginx / JVM / Node mitigations), and tests/unit/catalog/vendor_floor_table_test.go (this file’s COVERAGE; an app added to apps/ with no row here turns it red by name).

appprimary servicevendor minshipped capverdictsource
activepiecesactivepieces0.5 vCPU / 1 GB per concurrent flow (worker); app 1 vCPU / 1 GB per 10 workers4GOK (single WORKER_AND_APP container carries both roles)activepieces.com/docs/install/configure-operate/production-setup
static-sitenginxnone published (static files)256MOKnone
stirling-pdfstirling-pdfnone published; ~1 GB headroom for LibreOffice, ~2 GB for OCR on large scans4G (2G reservation)OK (matches upstream compose)upstream docker-compose; docs.stirlingpdf.com
onlyofficeonlyofficenone published for the fork; upstream ONLYOFFICE documents 2 GB min, 4 GB recommended4G (2G reservation)OK (image bundles postgres+rabbitmq+converter pool in one container)helpcenter.onlyoffice.com system requirements; Euro-Office README
affineaffine2 GB2GOK (already floored)docs.affine.pro self-host requirements
affine-rsaffine-rsnone for the Rust binary (Node affine is 2 GB)1GOK; different binary; not the Node floornone
agent-canvasagent-canvasnone published4GOKnone
blockscoutblockscout-backendnone published512MOKnone
ciso-assistantbackendnone published1GOKnone
cisobackendnone published1GOKnone
clickhouseclickhouse4 GB4GOK (already floored)clickhouse.com/docs/operations/tips
crowdseccrowdsecnone published512MOKnone
defectdojodefectdojo-uwsginone published1GOKnone
defectdojo-classicdefectdojo-uwsginone published1GOKnone
dependency-trackdtrack-apiserver2 GB / 2 CPU4G / 2.0OK (already floored)docs.dependencytrack.org deploy-docker
difydify-plugin-daemonnone published2GOKnone
docusealdocusealnone published1GOKnone
drover-relaydrover-relaynone published (upstream happy-server documents no floor)1GOK (one replica, Postgres on the estate’s own stack)none
ethereumgethmainnet often 8 GB+; package posture unstated1GLEFT; may be light/dev; not raised without package intentgeth.ethereum.org docs
fizzyfizzynone published (upstream’s Docker and Kamal guides size no floor)1GOKbasecamp/fizzy docs/docker-deployment.md
fleetfleet4 GB / instance4G / 1.0BREACH→fixed (was 512M / 0.5)fleetdm.com reference-architectures
frappefrappe-webnone published (bench-sized)4GOKnone
ffxfrappe-webnone published (bench-sized)4GOKnone
fusionpbxfusionpbxnone published2GOKnone
garagegarage-N1 GB RAM (stated requirement)1GOKgaragehq.deuxfleurs.fr
giteagitea~512 MB–1 GB typical1.5GOKdocs.gitea.com
gitlabgitlab4 GB Omnibus min6GOK; lowered from 16G on measurement (see note below)docs.gitlab.com
gitlab-fizzygitlabfizzynone published256MOKnone
gitlab-hulygitlabhulynone published512MOKnone
gitlab-runnergitlab-runnernone published2GOKnone
glitchtipglitchtip-webnone published1GOKnone
goalertgoalertnone published512MOKnone
graphitineo4jheap+pagecache+1 GB3GOK (already floored)neo4j operations-manual docker
greenbonegvmdnone published (data images are large)4GOKnone
hockeypuckhockeypucknone published512MOKnone
hookshothookshotnone published512MOKnone
hulyelastic / redpanda / nginxES 2G; Redpanda 2G; nginx idle floor 256M2G / 2G / 256MOK (already floored)elastic.co; redpanda sizing; measured
huly-matrix-notifiernotifiernone published512MOKnone
hyperswitchhyperswitch-servernone published512MOKnone
identity-brokerbrokernone published512MOKnone
immichimmich-server / ML6 GB install / ML spike3G / 2GOK (already floored)docs.immich.app/install/requirements
ivatarivatarnone published768MOKnone
jellyfinjellyfin~2 GB typical2GOKjellyfin.org
journivjournivnone published1GOKnone
keygenkeygen-webnone published1GOKnone
kubokubonone published1GOKnone
kuttkuttnone published512MOKnone
lookoutlookoutnone published (first-party One/node server; better-auth is stateless JWE)1GOKnone
librechatlibrechatnone published2GOKnone
mailmailpitnone published256MOKnone
mailbox-reconcilermailbox-reconcilernone published128MOKnone
mailbox-reconciler-ffxmailbox-reconcilernone published128MOKnone
mailcowstack (mysql+dovecot+clamd+…)~6 GB host typicalservices sum ≫ 6GOKmailcow docs
mariadbmariadbnone published1GOKnone
matomomatomonone published512MOKnone
matrixsynapse1 GB (large rooms)2Gsits-on-floor→cleared (was 1G)matrix-org.github.io/synapse installation
matrixjitsi-jvbheap 768m inside 2G2GOK (already floored + VIDEOBRIDGE_MAX_MEMORY)jvb.sh default; issue #1575
mauticmautic2 GB host min2GBREACH→fixed (was 512M)mauteam.org hardware requirements
medusamedusanone published2GOKnone
metabasemetabase1 GB typical4GOKwww.metabase.com
midpointmidpoint~2 GB typical4GOKdocs.evolveum.com
midpoint-classicmidpoint~2 GB typical4GOKdocs.evolveum.com
mongodbmongodb~1 GB typical2GOKnone
monicamonicanone published512MOKnone
monicamonicancnone published512MOKnone
monica-nextcloudmonicancnone published512MOKnone
multiplatformnginxidle floor 256M256MBREACH→fixed (was 128M)measured; host_sized_workers
multiplatform-keycloakkeycloak1000 MB base for an idle instance, plus 500 MB per 100k active sessions1536MOK (the heap follows the limit at MaxRAMPercentage=50; idles near 950M RSS on this image)keycloak.org high-availability/concepts-memory-and-cpu-sizing; apps/integrated/multiplatform-keycloak/vars.yaml
mysqlmysqlnone published1GOKnone
netbirdnetbird-managementnone published512MOKnone
nextcloudnextcloud512 MB min / 2 GB rec2GOKdocs.nextcloud.com
nginxnginxidle floor 256M256MOK (already mitigated)measured
ollamaollamamodel-dependent12GOKnone
openarchiveropenarchivernone published3GOK; sized to the heap it authorises, not to a vendor figure: the container runs five node processes (frontend, backend, ingestion worker, indexing worker, sync scheduler) and hands the indexing worker INDEXING_WORKER_MAX_OLD_SPACE_MB=1536, so the cap is twice the heapupstream .env.example; apps/standalone/openarchiver/vars.yaml
openarchivermeilisearchnone published2GOKmeilisearch.com docs
openarchivertikanone published1GOK (JVM + tesseract-ocr on a scanned attachment)tika.apache.org
openhandsopenhands4 GB, published as a SYSTEM figure (“a system with a modern processor and a minimum of 4GB RAM is recommended to run OpenHands”)2GOK; the cap is the ORCHESTRATOR only, and the vendor’s figure is not this cgroup’s floor: the app container binds /var/run/docker.sock and spawns each session’s SANDBOX_RUNTIME_CONTAINER_IMAGE on the HOST daemon, so the runtimes are siblings drawing host RAM outside this limit. Same reading as affine-rs (different subject, not the published floor) and mailcow (a host figure against a multi-service sum)docs.openhands.dev/openhands/usage/run-openhands/local-setup
openreplaychalice-openreplaynone published1GOKnone
openreplay-chclickhouse4 GB4GOK (already floored)clickhouse.com/docs/operations/tips
paperlesspaperless~1 GB typical2GOKdocs.paperless-ngx.com
peertubepeertube1.5 GB2GBREACH→fixed (was 1G)joinpeertube.org/faq
penpotpenpot-frontendidle floor (host-sized workers)1GOK (already floored + autotune)measured
planeplane-apinone published2GOKnone
pmmpmm-server~2 GB typical4GOKdocs.percona.com
postizpostiznone published1536MOKnone
pulppulp-workernone published3GOKnone
redisredisnone published512MOKnone
s3-migratemigratenone published1GOKnone
s3managers3managernone published256MOKnone
shlinkshlinknone published1GOKnone
sonarqubesonarqube4 GB Docker6GOK (already floored)docs.sonarsource.com linux pre-install
supabasepostgres / kongnone published as a stack floor1GOKnone
supersetsupersetnone published2GOKnone
uptimeuptime-kumanone published512MOKnone
uptime-kumauptime-kumanone published512MOKnone
vaultwardenvaultwardennone published (tiny)512MOKnone
wazuhwazuh-indexer1 GB heap → 2G cap2GOK (heap raised 512m→1g; floor added)documentation.wazuh.com indexer memory
whoamiwhoaminone published256MOKnone
windmillwindmill-server / worker2 GB stack; 2048M/worker2G / 2GBREACH→fixed (was 512M / 512M)windmill.dev self_host; official compose
wordpresswordpress~512 MB typical512MOK (sits on typical; no vendor floor)none

Note: gitlab, lowered 16G → 6G (2026-08-17)

Section titled “Note: gitlab, lowered 16G → 6G (2026-08-17)”

This sweep only ever looked UPWARD: a cap that cleared its vendor minimum was marked OK and left alone. gitlab’s 16G cleared the 4 GB Omnibus minimum four times over and so was never examined, and the sweep’s own framing (“shipped cap”) hid what the number really is. limits.memory in an app compose is the quota, and the renderer derives both the reservation and the limit from it: reservation = quota × deploy.reservation_ratio (1.0) and limit = quota × deploy.limit_ratio (1.5). Placement admits a replica when that reservation fits the node’s free capacity. A 16G quota is a 16 GiB reservation. On a 30.6 GiB node it held 16 of 28.5 GiB of reservations, left 2.1 GiB schedulable, and blocked a 4 GiB placement for a day while the node’s real usage was ~7.7 GiB.

Measured on the running package (puma worker_processes 1, prometheus off, external postgres, gitaly in-container), from cgroup v2 memory.current / memory.peak: steady 3.18 GiB; memory.peak over a 13.5 h window 3.30 GiB; with one full forked gitlab-rails runner (the shape gitlab-backup create/restore takes) 3.98 GiB. No OOM kill in 14 days of that node’s kernel log.

6G ⇒ reservation 6 GiB (1.51× the measured worst case) and limit 9 GiB (2.26× it, and above GitLab’s own 8 GB recommended figure). A cap far above a vendor minimum is not automatically safe; on this platform it is capacity withdrawn from every other deployment, so a large one now wants a measurement, not just a floor check.

Headless apps: no services, nothing to size

Section titled “Headless apps: no services, nothing to size”

These twelve packages render services: {}. Each exists to declare a socket onto an external or managed instance (RDS, a vendor SMTP relay, someone else’s S3, a GitLab this estate does not administer), so it creates no container, holds no cgroup, and has no cap a vendor minimum could floor. They are absent from the table above by construction, not by oversight, and they are named here so the next reader diffing the table against apps/ does not re-walk twelve packages to discover there was nothing in them.

  • external-gitlab
  • external-imap
  • external-llm
  • external-mailcow
  • external-mongodb
  • external-mysql
  • external-oidc
  • external-postgres
  • external-redis
  • external-s3
  • external-smtp
  • s3

The exemption is declared rather than inferred on purpose: a package that grows a real service while sitting on this list would otherwise keep a silent pass from the sweep. vendor_floor_table_test.go fails by name in that case, and in the reverse case of a row naming an app that is gone.

Class floor (every *-pgclient): 512M / 0.5 cpu, measured; already enforced.

By-construction nginx mitigations (original six + later siblings): penpot-frontend, huly/nginx, nginx/nginx, greenbone/nginx, defectdojo/defectdojo-nginx, mailcow/nginx-mailcow, plus pulp-web, openreplay frontend, shlink, dify, multiplatform. Guarded in host_sized_workers_test.go.