Skip to main content
These are the figures the Docker Compose installer (install.sh) checks before it starts anything. For Kubernetes, see Kubernetes (Helm).

​
What the installer checks

With --yes, the memory prompt is skipped and the install continues. The checks do not run for --upgrade or --rotate-signing-secrets. The installer supports macOS, Linux (x86_64 and arm64) and Windows through WSL or Git Bash.
20 GB is the point at which the installer warns, not a sizing target. Indexed content, vectors and uploaded files grow with your data, so leave room for them.

​
Deployment types

The installer asks for a deployment type, or reads it from PIPESHUB_DEPLOY_TYPE: By default, every type uses Redis as the key-value store and Neo4j as the graph database. The types differ in these ways:
  • Message broker: full uses Kafka. slim and eval use Redis Streams.
  • Coding sandbox: slim and full have one. eval does not.
  • The slim image is smaller. It downloads the embedding model the first time it is needed, so that first start needs internet access.
  • The latest image has the embedding model built in. Use it where the host cannot reach the internet.
  • eval does not pull the coding-sandbox image and does not start the Slack bot, so agents cannot run code.
You can change the graph database (Neo4j or ArangoDB), broker and key-value store in the installer. eval defaults to Neo4j and needs it. Do not pick ArangoDB for eval.

​
Ports

Docker Compose publishes one port on the host: 3000 by default (APP_PORT in .env). If 3000 is taken, the installer tries the next free port, or you can set PIPESHUB_PORT. The other services talk to each other on the internal Docker network.

​
HTTPS

Anyone reaching PipesHub by a hostname, rather than localhost, needs HTTPS. See Serving it over HTTPS.