Skip to main content

Self-host ColabHive Community

ColabHive Community is the complete self-hosted control plane under the MIT license. The software license costs USD 0, with no node or accelerator-vendor limit. It enrolls nodes and handles placement, routing, model lifecycle, and observability across your CPU/GPU hardware. You operate the deployment, its security, backups, upgrades, and availability.

Requirements​

  • Linux with Docker Engine and Docker Compose v2
  • Python 3 and OpenSSL (used to generate local credentials)
  • Capacity for the control-plane containers, model metadata, observability data, and build cache
  • CPU/GPU nodes reachable from the control plane; accelerator drivers stay on their node hosts

Download and verify​

The versioned Community bundle is generated from a strict source allowlist. It contains no .env, repository history, runtime data, backups, planning material, caches, or secret/keyring paths. Its build gate scans for high-confidence secret patterns, verifies every payload file against the embedded SHA-256 manifest, and runs docker compose config --quiet after extraction.

curl -fLO https://colabhive.com/downloads/community/v1/colabhive-community-v1.tar.gz
curl -fLO https://colabhive.com/downloads/community/v1/colabhive-community-v1.tar.gz.sha256
sha256sum -c colabhive-community-v1.tar.gz.sha256
tar -xzf colabhive-community-v1.tar.gz
cd colabhive-community-v1
sha256sum -c MANIFEST.sha256

Treat a checksum failure as a hard stop. Do not run an archive that does not match both checks.

Start a local deployment​

For a private homelab evaluation on a trusted network:

./scripts/setup-env.sh development
docker compose config --quiet
docker compose up -d cockroachdb
./infra/cockroachdb/apply-all-schemas.sh
docker compose up -d --build

Development mode creates local-only credentials. Do not expose that configuration to the public internet. Check startup with docker compose ps and ./scripts/health-check.sh.

Operate it beyond a homelab​

Generate the production template, replace every placeholder through your secrets manager, enable TLS, restrict CORS and network ingress, then validate Compose before starting:

./scripts/setup-env.sh production
./scripts/generate-secrets.sh
# Move generated values to your secrets manager and replace every <PLACEHOLDER> in .env.
if grep -nE '<[^>]+>' .env; then echo 'unresolved placeholders' >&2; exit 1; fi
docker compose config --quiet
docker compose up -d --build

Before accepting workloads, configure backups, restore drills, monitoring receivers, storage retention, and an upgrade window. Community supplies the control plane; operating responsibility remains with you. Hosted and Enterprise plans are separate options when ColabHive-operated infrastructure or contractual support is required.

Reproduce the release gate​

The public bundle and checksum are produced from the working tree with:

python3 scripts/generate_community_bundle.py

The generator uses fixed archive metadata and sorted inputs, so unchanged source produces the same archive bytes. It fails closed on missing required inputs, symlinks, forbidden paths, sensitive patterns, manifest drift, unsafe tar members, or an invalid extracted Compose model.

For help, email support@colabhive.com. Report security issues privately to security@colabhive.com; never attach credentials or an .env file.