Oxide Computer Company
@oxide
The cloud you own.
Release 20 is LIVE & bringing even more network performance. Jumbo frame support for external networks ( already used internally) raises instance MTU from 1500 to 8500 bytes, substantial for network IO-intensive workloads, plus additional self-service update and block storage services goodness.
How is Oxide different from hyperscaler infrastructure? FAQ Friday #51
Why can't commodity server vendors just do what we've done? FAQ Friday #50
What is Oxide doing about System Management Mode (SMM)? FAQ Friday #49
What's THE differentiator for Oxide Computer Company? FAQ Friday #43
How does the Oxide Cloud Computer's power shelf work? FAQ Friday #42
Release 19 is now LIVE & you're going to want to check out Trust Quorum. How do we truly attest to the security of a system distributed across many physical hosts that will be swapped out over the system's lifetime? Read the full release notes here: buff.ly/cobURMz
Is Oxide hardware made by Super Micro (or any other OEM/ODM)? FAQ Friday #40
This is a BIG one that enables our customers to expand the types of workloads they land on the Cloud Computer. Read more here: buff.ly/4EGrUq6
Were we crazy for building our own network switch? FAQ Friday #37
Can I use Oxide to satisfy data residency requirements? FAQ Friday #35
Self-service updates have arrived! Oxide system v17 adds support for installing complete system updates without Oxide involvement, further enabling organizations to own your cloud. Here's a look at what's new in v17: