Private Cloud and On-Premises
PipesHub is designed to run entirely inside your own network. Nothing about the core product requires an outbound connection once the images are on the host, which makes it suitable for regulated environments and air-gapped networks.Requirements
- A Linux host with Docker and Compose v2.
- 16 GB RAM or more for the full deployment; 50 GB or more of disk.
- Internal DNS pointing a hostname at the machine.
- A TLS certificate, from your internal certificate authority or a public one.
Install
The Deployment Overview covers the standard install. On a machine with internet access:Air-gapped installation
On a host with no internet access, move the images across yourself. On a machine that does have access, pull and save the images:zookeeper and kafka images as well if you chose Kafka as the message broker.
On the air-gapped host, load them and install without pulling:
--no-pull tells the installer to use the images already present rather than trying to reach Docker Hub.
Choosing models
An air-gapped deployment cannot reach a hosted model provider, so configure local ones:- Text generation: Ollama or vLLM on your own hardware.
- Embeddings: Sentence Transformers, which run inside PipesHub with no separate server.
- Speech to text: Whisper, which runs locally.
Telemetry
PipesHub collects usage telemetry by default. On an isolated network those requests simply fail and nothing breaks, but you can turn the collection off in Settings → General so the attempts stop.Certificates
If you terminate TLS with a certificate from an internal certificate authority, make sure that authority is trusted by the machines people browse from. PipesHub itself does not care which authority signed it.Day-two operations
--upgrade will not find new images. Load the new image with docker load first, then run ./install.sh --upgrade --no-pull.
For backup and restore, follow the procedures in the GCP guide — they operate on Docker volumes and work anywhere.