Hacker News Reader

Comment by bakies | Hacker News Reader

Yeah me too. Like I kinda compare oxide to coreweave and coreweave is built on top of k8s afaik. I'm wondering what the underlying tech oxide leans on. If I was doing this I would be using talos and k8s on baremetal and building on top of that. Container first rather than VM first seems like a big advantage imo. Most workloads will be containers.

View on HN

Coreweave is a cloud provider right? I dont think it is apple to apple comparison.

What's a cloud? K8s is a cloud imo, so is what oxide is providing afaict

Cloud is an API you can hit to get access to hardware. Oxide sells hardware.

Oxide has an API on top that gets you services. The whole pitch is AWS with purchased hardware, no? That's cloud

Yes but you buy the hardware and have to rack it, and then you have a cloud at home.

Extreme nit: because you purchase a rack at a time, you don't actually rack it. You wheel it in, plug in network and power, and hit "on".

Oh man, genuinely thank you for that nit. Gives me different imagery to imagine for the Oxide node I'll never be able to afford.

I'm glad, I meant it in semi-jest, because it's true, but also just a very funny thing to "well actually" about.

> The whole pitch is AWS with purchased hardware, no?

HBOM

SBOM

Unparalleled support w/ vertical integration

Tons of companies will see you a "cloud". The other parts seem pretty unique.

Most security minded orgs and also AWS deploy containers in VMs for better security

oxide and coreweave?

Oxide is in-house custom everything. Switches. Racks. Power bus. BMC. Firmware. OS. Software and APIs. Virtualization. Etc.

Reply on news.ycombinator.com