Oxide Computer partners with Carahsoft for US public-sector cloud sales

Oxide Computer Company has named Carahsoft Technology Corp. as its Master Government Aggregator, giving US public-sector agencies a procurement route to Oxide's rack-scale cloud system through established contract vehicles including NASA's SEWP V programme and OMNIA Partners. The agreement makes Oxide's hardware available through Carahsoft's network of resellers, systems integrators and consultants for the first time.

Steve Tuck, co-founder and chief executive of Oxide, said public-sector organisations are looking for ways to modernise infrastructure while retaining control over data and operations within environments they own. The Carahsoft channel, he said, gives federal, state and local government customers access through procurement frameworks they already use.

What Oxide sells

Oxide's Cloud Computer is a rack-scale system that integrates compute hardware with a cloud control plane, delivered as a vertically integrated unit the company says can be operational within hours of installation. The platform exposes elastic compute, storage and networking through APIs, a CLI and a web console, allowing developers to provision resources in self-service mode without raising IT tickets or writing manual configuration scripts.

The company positions several capabilities as specifically relevant to government buyers: a hardware root of trust, an auditable open-source software stack, and the elimination of third-party virtualisation licensing dependencies. The system is described as capable of supporting agentic AI workloads, high-performance computing, classified data processing and general-purpose IT operations. Oxide describes itself as the creator of the first commercial rack-scale system that unifies hardware and cloud control-plane software in a single product, though that claim is the company's own and has not been independently verified.

Erica Raymond, Director for Infrastructure Solutions at Carahsoft, said Oxide fills a gap for agencies that need cloud agility but require data sovereignty and operational control that only owned infrastructure can provide.

Market context and competitive landscape

On-premise cloud infrastructure is a growing category, driven by government and regulated-enterprise demand for sovereign compute. The space sits at the intersection of several converging trends: tightening US federal data-residency requirements, growing reluctance to route classified or sensitive workloads through hyperscaler public clouds, and rising interest in owning rather than renting compute capacity as AI inference costs accumulate.

Oxide's approach competes with a range of converged and hyperconverged infrastructure vendors, including Dell's VxRail, HPE's GreenLake on-premise offering, and Nutanix's cloud platform, as well as AWS Outposts and Azure Stack, which extend hyperscaler control planes into customer data centres. The Oxide proposition differs in that it integrates bespoke hardware with a fully open-source control plane rather than licensing an incumbent virtualisation stack, which may appeal to agencies seeking to reduce supply-chain risk or satisfy open-source policy mandates.

The SEWP V and OMNIA contract vehicles are well-established routes into the US federal and state markets. Being listed on SEWP V in particular is a meaningful commercial step, as it removes the procurement friction that can delay purchases by months in the public sector. For a hardware-led startup, channel access of this kind is often as strategically significant as the product itself.

Regulatory read-across

The digital sovereignty angle is increasingly relevant under US executive-branch guidance on cloud security. FedRAMP authorisation, which the release does not mention, remains a common requirement for cloud services deployed in federal environments. Oxide's model, where the agency owns the hardware and the software stack is open-source, may allow some customers to bypass or simplify FedRAMP obligations depending on workload classification, though the company has not made that case explicitly. Buyers will also want to understand how Oxide's open-source control plane maps to NIST SP 800-53 controls and whether the hardware root-of-trust implementation meets FIPS 140-3 requirements for classified or sensitive workloads.