Request a demo

GPU cluster software that never needs the internet

BareStax installs, operates, updates, and recovers your on-premises NVIDIA GPU cluster, from racked server to running job. It works the same way connected or fully air-gapped, and your cluster never depends on a connection to us.

See how it works →

Why institutions choose BareStax

  1. Every server enters production the same way

    One command and one approval. BareStax inventories the hardware, installs a tested driver stack, runs a two-node fabric check, and hands the node to the job queue. No hand-built driver stacks. How a node joins

  2. Operations stay predictable

    Drift is fixed in place or held for a maintenance window. Faulty nodes stop taking work while running jobs finish. Critical actions need a second person who reads the impact first. Health and recovery

  3. Control stays inside your institution

    Full operation without internet access. No outbound connections, no telemetry, an offline license file, and cluster keys and audit records that stay in your data center. Security

Why BareStax

You rack and install. BareStax does the rest.

  1. Rack the servers

    Connect GPU nodes, the head node, storage, and the cluster network.

  2. Install Ubuntu

    Keep your own Ubuntu 24.04 installation. BareStax never erases the disk.

  3. Run one command, give one approval

    The node joins, validates, and starts taking jobs.

No Kubernetes. No hypervisor. Just the GPU.

No layers. Just compute.

BareStax brings declarative, self-healing control to the layers Kubernetes never manages: kernel, NVIDIA drivers, CUDA, NVLink, InfiniBand, BMC, and the job scheduler.

Every job gets the whole GPU. Nothing sits in between.

One product for the whole cluster lifecycle

  1. Day 0

    Install the control plane, connect identity, and test the alert path.

    barestax-server init
  2. Day 1

    Servers join with one command and one approval.

    barestaxd joinbarestaxctl node approve
  3. Day 2

    Drift is corrected; faulty nodes stop taking new work.

    barestaxctl impact node gpu-03
  4. Growth

    New servers follow the same path; each GPU class gets its own queue.

    barestaxd join
  5. Updates

    Signed releases start on one canary node, then roll out within your disruption budget.

    barestax-server upgrade --offline
  6. Removal

    Drain a node without losing work, then remove it.

    barestaxctl node drainbarestaxctl node remove

See what a fault affects before you act

When a node fails, BareStax shows the jobs, tenants, and services it touches. Verified and possible impact are kept apart, and every view shows how old its data is.

Air-gapped by design, not by exception

Nothing in BareStax needs the internet. Updates arrive as signed bundles, are verified and approved inside your network, and roll out one canary at a time. How releases work

Internet sideAir-gap boundaryBundler collectsand signs01Transfer byapproved media ordata diode02Verify signature,integrity,compatibility, andscan report03Four-eyes approval04Canary node first05Roll out across thecluster within thedisruption budget06Internet sideBundler collects and signs01Air-gap boundaryTransfer by approved media or datadiode02Verify signature, integrity,compatibility, and scan report03Four-eyes approval04Canary node first05Roll out across the cluster withinthe disruption budget06

Your team fixes faults without calling us

Every error carries a code, its impact, what BareStax already did, and the next step, with an offline runbook. Standard support is still part of every subscription. The product interface is in English.

Check every claim before you sign

  • The full specification, in writing

    Every capability on this site is specified in the technical overview: architecture, lifecycle, security, deployment, and licensing.

    Download the PDF
  • A pilot with written acceptance drills

    Run BareStax on your own hardware for 90 days. Acceptance is proven by drills your team witnesses, from node join to a control plane restore.

    Acceptance checklist
  • A license that cannot strand you

    If you do not renew, the cluster keeps running on the last imported release and your licensed capacity. The license is a signed offline file.

    Licensing
  • Security your team can test

    Signed release bundles, an exportable hash-chained audit record, and a published contact for vulnerability reports.

    Security

See it on hardware like yours

Book a guided remote demo. Then run a paid pilot on your own servers, with written acceptance tests.