BareStax runs your NVIDIA GPU cluster from the installed server to the job queue

BareStax installs, expands, updates, and keeps NVIDIA GPU clusters running in your data center. It manages the path from an installed Ubuntu host to a schedulable BareStax Core node, with the same operating model on connected and fully air-gapped networks.

Your team performs the physical handoff

  1. Rack the servers

    Connect the GPU nodes, head node, storage, and cluster network in your data center.

  2. Install the operating system

    Keep your own Ubuntu installation. BareStax works above it and does not erase the disk.

  3. Run one command and give one approval

    The node reports its hardware, receives the matching profile, installs a tested software set, and passes cluster checks. BareStax handles the rest.

Declarative control reaches below the scheduler

No layers. Just compute.

Kubernetes applies desired state and reconciliation to workloads it manages. BareStax applies that operating model to layers Kubernetes does not manage: system settings, kernel, NVIDIA drivers, CUDA, NVLink, NVSwitch, InfiniBand, BMC, and job scheduling.

There is no Kubernetes or virtualization layer between the job and the GPU. BareStax Core assigns the full GPU directly to the job. BareStax classifies drift by whether correction needs downtime; disruptive changes wait for approved maintenance.

One control model covers the cluster lifecycle

  1. Day 0

    Install the control plane, connect identity, define network and storage targets, and test the alert path.

    barestax-server init
  2. Day 1

    One command and one approval start inventory, profile selection, stack installation, and hardware validation before BareStax Core accepts work.

    barestaxd joinbarestaxctl node approve
  3. Day 2

    Drift that needs no downtime is fixed in place; anything that does waits for an approved maintenance window. A faulty node takes no new work while its running job continues. Recovery follows policy.

    barestaxctl impact node gpu-03
  4. Growth

    New servers use the same join path, with separate queues for different GPU classes in one pool.

    barestaxd join
  5. Updates

    Signed releases start on one canary node and continue within the disruption budget while running jobs remain protected.

    barestax-server upgrade --offline
  6. Removal

    Drain and remove a node without losing active work. A returning node receives a new identity.

    barestaxctl node drainbarestaxctl node remove

Every fault is tied to operational impact

A failed node is not an isolated red status. The impact view identifies affected jobs, tenants, and services, separates verified impact from possible impact, and states the age of its data.

The path runs from alert to impact and controlled operation; a broken live stream marks the view as stale.

Air-gapped operation uses the same release process

Runtime stays inside the institution's network. Signed bundles cross by approved media or data diode, then deploy by canary within the disruption budget. Deployment details

01Bundler collects andsigns02Transfer by approvedmedia or data diode03Verify signature,integrity,compatibility, andscan report04Four-eyes approval05Canary node first06Roll out across thecluster within thedisruption budgetInternet sideAir-gap boundaryInternet side01Bundler collects and signsAir-gap boundary02Transfer by approved media ordata diode03Verify signature, integrity,compatibility, and scan report04Four-eyes approval05Canary node first06Roll out across the clusterwithin the disruption budget

Errors explain themselves in English and Turkish

English and Turkish cover the console, portal, CLI messages, errors, and runbooks; every coded error points to its offline runbook.

The first session starts with what is in the rack

GPU classes, fabric, and storage set the agenda. We work from your hardware, not a slide deck.