System

Clients & Fleet (Mothership)

The mothership — provisioning customer servers from the Clients page.

The Clients page (System section) manages your customer fleet. It only exists on the mothership — the box holding the license signing key. On every other install the page hides and its API refuses.

Provision a new client

Fill the form: client name, apex domain, SSH target (root@ip; blank = this box), initial gateway password, licensed + expiry, Chroma. Click PROVISION and watch the event log stream:

Push and install

Release artifact pushed and installed on the target.

Run provisioning

provision.sh runs (idempotent full-stack setup).

Install provider keys

Customer provider keys installed (BYOK, --env-file on the CLI).

Issue license

License issued and installed.

Acceptance gate

The e2e suite must pass — the tenant is ACTIVE only on a green gate; failures land as FAILED with the reason logged.

Re-running resumes safely; every step is idempotent.

CLI equivalent

aios-control new-client --name acme --apex acme.com --host root@1.2.3.4 \
  --artifact dist/vibeai-os-vX.tar.gz --admin-password ... \
  --licensed --expires 2027-07-01 --env-file acme.env
aios-control list | events --name acme | check --name acme | renew --name acme --expires ...

Ongoing operations

re-gate re-runs the acceptance suite against a tenant anytime (failures mark it DEGRADED with the reason in its event log)
renew reissues + installs a license to a new expiry
The registry (/root/.aios-control/control.db) is the book of record; the page and the CLI always agree.

Release artifacts

./deploy/release.sh vX.Y.Z builds a versioned, sha256-summed tarball (binaries + deploy tooling + web UI + manual) — that’s what new-client pushes to customer boxes.