Command-line control for Oxide rack-scale infrastructure management
Provision virtual machines, configure VPC networking, and import raw disk images on an Oxide rack using the Oxide CLI, a Rust-built command-line tool. Oxide Computer Company supplies this desktop utility to let DevOps engineers and sysadmins manage on-premises cloud resources with API-driven commands and scripting hooks. Key capabilities include instance lifecycle commands, browser-based authentication with token management, and CLI output suitable for automation, making it suited to teams that run physical cloud hardware.
What does Oxide CLI actually do?
The CLI issues API calls to the Oxide control plane to perform core tasks: create, start, stop, and delete virtual machines; import raw disk images and create snapshots; and configure virtual private clouds, subnets, and networking rules. It exposes project-scoped resource commands so administrators can keep multi-tenant resources separated, and it surfaces system metrics and timeseries data via dedicated subcommands for monitoring.
Does it affect desktop performance during operation?
Because the binary is written in Rust and described as having a small footprint, the tool runs as a standalone command-line process rather than a background service. Installation on Windows is possible via a WinGet package or a standalone ZIP binary, which keeps interaction local to the calling shell. The design implies minimal persistent overhead; commands run, call the control plane, then exit, so continuous CPU or RAM consumption on the desktop is limited to the process lifetime.
Is it safe to use on production machines?
Authentication flows use a browser-based identity provider handshake and produce local credentials, and the CLI supports environment variables (OXIDE_HOST and OXIDE_TOKEN) for non-interactive scripts. The presence of project isolation and token-managed auth indicates the tool is built to keep access scoped. Because it ties directly to the control plane, operators should apply standard access controls and store tokens securely before running commands against production hardware.
Do I need technical knowledge to operate it correctly?
The CLI targets DevOps engineers and system administrators and supports both interactive and scripted workflows. It provides explicit commands for instance and disk operations and supports environment variables for automation, which means basic shell and scripting familiarity is required for safe automation. Users who manage images and networking should understand VM provisioning concepts and Oxide project boundaries to avoid accidental resource changes.
Clear choice for infrastructure teams managing on-prem rack-scale hardware
The Oxide CLI serves administrators and developers who run Oxide rack hardware and want API-first control from a desktop shell. Its Rust implementation and token-based browser login support predictable operation and scripted automation. For teams that already operate physical cloud hardware and know VM provisioning, the CLI provides direct, low-latency control. Recommended.
