FAQ Friday

The answer is just hours, and I don’t mean double digit hours, I mean single digit hours and low single digits if that. Now, there are a variety of factors that can affect the deployment time for Oxide, such as defining your actual start and end time, and just general logistics, things like power configuration and network configuration.

But assuming that all of those are good, you can have Oxide up and running in just a few hours. Let’s walk through the installation of an Oxide rack because I’ve attended a few customer installations and it’s a fantastic experience. So what happens is a crate arrives containing the Oxide rack to your location.

You uncrate the rack and wheel it to your location of choice. Then you connect power and networking. And then from there we’re gonna run what’s called a rack setup script or RSS that’s gonna initialize the rack with networking configuration, DNS, BGP, switch port settings, things of that nature.

Now the rack can connect to your upstream network. So we’ll use that connectivity to update the software on the rack, so all of the sleds, the switches, the power shelves. We’ll update the software, even the control plane. And then from there, we’ll ask you to generate TLS certificates and a password so that you can configure your first Oxide silo.

And then when you have that first Oxide silo, you can load your image of choice and deploy an Oxide instance and boom, you’re done and you’re ready to use Oxide, which is fantastic. It’s just a couple of hours from uncrating the rack, to actually using and deploying workloads on Oxide. I’ve seen companies that can’t even get hardware deployed like that in months, much less hours.

So if all that sounds interesting to you, and I’m sure it does 'cause it sounds interesting to me, let us know. Reach out to us at oxide.computer and we’re happy to chat. Thanks.