Operators and researchers work from one consistent interface

The BareStax console connects cluster inventory, health, impact, operations, approvals, alarms, queues, quotas, image promotion, and runbooks.

The console runs on the head node inside the control plane. The researcher portal opens from the login node and follows the same design. Neither interface needs an external web service.

Cluster state comes first

The cluster summary shows node and GPU state, active work, alarms, pending operations, and queue conditions. Inventory connects each node to its hardware topology and assigned profile.

Object pages use the same tabs for Summary, Metrics, Configuration, Impact, Events, Jobs, and Audit. Operators can move from a node or storage target to its current work, recent events, declared settings, and recorded actions without reconstructing context across tools.

Operations and Approvals views list proposed, pending, running, and completed changes with their targets. Alarm, queue, quota, and image promotion views use the same resource context.

Live server changes appear immediately. If the connection to the update stream breaks, the page marks its data as stale.

The impact view connects an alarm to affected work

An alarm identifies a symptom. The impact view connects that symptom to affected jobs, tenants, and services. It separates verified impact from possible impact and displays the age of the underlying data.

From that view, the operator can open the relevant controlled operation. The workflow stays attached to the affected resource and its operational context.

Critical actions require independent approval

Node removal, image promotion, restart, and other critical operations use four-eyes approval. The requester cannot approve the same request, and approval belongs to a person rather than a shared account.

Approval has two steps: impact review comes first, followed by the target name. The view shows the requested change, target, requester, and current decision state before execution.

Approval: drain-gpu-03

Read the impact on gpu-03; press Continue to approve.

Verified: 1 node, 2 jobs, 1 tenant4521, 4533 · 2 min ago

Confirm the approval: drain-gpu-03

The person who opened the request cannot approve it.

user:operator-2

Sample product interface

Every error states what the operator can do

BareStax gives each error a code. The console explains what happened, the impact, what the product already did, what the operator should do, and which offline runbook applies.

The runbook reader is part of the console and works in an air-gapped network. Operators do not need an external documentation site while handling a fault.

Cluster metrics stay connected to inventory and work

A node-by-GPU heat map shows state across the cluster. Related views cover GPU utilization, memory, power, temperature, and network behavior.

Deep monitoring dashboards open inside the console under the same authenticated session. Exporters, alert rules, and prepared dashboards include the head node as well as compute nodes. Stale measurements remain visible with their age shown.

Queue and quota state stays beside health data, so idle capacity can be read together with waiting work. Usage reports identify idle GPUs while jobs remain queued.

Every console operation has a CLI path

The console and CLI call the same declarative API. Policy, approval requirements, live status, and audit behavior therefore remain the same when an operator copies the command-line form of an action.

barestaxctl serves operators with plans, health reports, node actions, operations, and approvals. Output can be a readable table or JSON for automation.

barestaxctl impact node <name>
barestaxctl operation list
barestaxctl operation approve <name>
barestaxctl node drain <name>
barestaxctl node remove <name>

The researcher portal exposes work without cluster authority

Researchers see their jobs, current state, waiting reason, quota, logs, and cancellation controls. A template form submits batch, array, multi-node training, or interactive work through BareStax Core.

Jupyter, VS Code, RStudio, and remote desktop sessions start as BareStax Core jobs and open in the browser. Only the session owner can enter. An idle session closes and releases its GPU.

The portal also provides a file manager and browser terminal. Actions run under the researcher's own Linux identity, while the persistent workspace keeps packages and environments between sessions.

The interface works in English and Turkish

The console, portal, CLI messages, error explanations, and runbooks are available in English and Turkish. Users can choose light or dark theme, operate the interface by keyboard, and open actions through the command palette.

The console follows an alert through impact and approval