I've run my own servers for over 20 years now, but I guess I don't understand the pain point. Can you elaborate? They write:

  > Our system delivers all the hardware and software you need to run cloud…

To "run cloud?" Does this mean treating your own servers like "serverless?" Does it mean running Kubernetes? Is this primarily for people who want to self-host LLMs?

I'm literally so old that I write programs that run on a server and never think about infrastructure.

▲ steveklabnik 3 days ago | parent | next [-]

> To "run cloud?"

I agree that's a bit awkwardly phrased, let me send in a patch for that.

> Does this mean treating your own servers like "serverless?" Does it mean running Kubernetes? Is this primarily for people who want to self-host LLMs?

Not exactly any of that. We let you treat an entire rack as a single pool of resources, spinning up virtual machines that our control plane manages for you. Think "VPS provider but you own it." There's an API, but if you want to see what our console looks like, you can poke around with a demo here: https://console-preview.oxide.computer/

	▲	turnsout 3 days ago \| parent [-]
		That's helpful, thanks!

▲ throw0101c 3 days ago | parent | prev | next [-]

> To "run cloud?" Does this mean treating your own servers like "serverless?" Does it mean running Kubernetes? Is this primarily for people who want to self-host LLMs?

Machine/system/service deployment via API.

See §Essential Characteristics

> On-demand self-service; Broad network access; Resource pooling; Rapid elasticity; Measured service

* https://en.wikipedia.org/wiki/Cloud_computing

None are generally applicable to standalone pizza boxes as managed individual (as opposed to being herded by (e.g.) OpenStack).

▲ skybrian 3 days ago | parent | prev [-]

No GPU’s yet, so it’s not good for LLM’s. But they have a lot of funding now, so perhaps that will change?