@oxide.computer.bsky.social
The cloud you own. https://oxide.computer/bio
Reminder that this is today: join @booch.com, @ahl.bsky.social and me at 5p Pacific for what promises to be a lively and wide-ranging discussion!
02.02.2026 16:40 β π 21 π 4 π¬ 0 π 0Can I use Oxide to satisfy data residency requirements? FAQ Friday #35
30.01.2026 15:46 β π 11 π 0 π¬ 0 π 0Yes, absolutely. We do ask that your workday overlaps with US Pacific Time for at least four hours.
26.01.2026 23:26 β π 3 π 0 π¬ 1 π 0How can I integrate with Oxide Computer? FAQ Friday #34
23.01.2026 16:03 β π 10 π 2 π¬ 0 π 0
Job description for Oxide Operations Support Engineer
Operations Support Engineer might be of interest?
17.01.2026 15:29 β π 2 π 0 π¬ 1 π 0And yes, weβre hiring!
oxide.computer/careers
Screenshot from our website showing our salary now at $250,000
At @oxide.computer, we pride ourselves on terse performance reviews: we have exceeded expectations!
17.01.2026 03:22 β π 162 π 6 π¬ 2 π 5Does Oxide Support Windows Instances? FAQ Friday #33
16.01.2026 16:05 β π 12 π 2 π¬ 1 π 1
On Monday, @sunshowers.io and @davidcrespo.bsky.social joined me and @bcantrill.bsky.social to talk about their use of LLMs for building software--not to make vibe-coded one-offs, but to build much *more* robust systems software.
14.01.2026 15:55 β π 55 π 14 π¬ 2 π 5These guys make a great service and are incredibly attentive. We host Oxide and Friends on @transistor.fm and I have zero complaints.
15.01.2026 19:59 β π 15 π 1 π¬ 1 π 0Today, @ahl.bsky.social and I are going to take on a hot topic: what does engineering rigor look like in the age of LLMs? We will be joined by Oxide engineers who have been at the forefront of using LLMs to increase the rigor in their own work. Join us, 5p Pacific!
discord.gg/QrcKGTTPrF?e...
1 year: It will become undeniable that LLMs write good code 1 year: Weβre finally going to solve sandboxing 1 year: A βChallenger disasterβ for coding agent security 1 year: KΔkΔpΕ parrots will have an outstanding breeding season 3 years: the coding agents Jevons paradox for software engineering will resolve, one way or the other 3 years: Someone will build a new browser using mainly AI-assisted coding and it wonβt even be a surprise 6 years: Typing code by hand will go the way of punch cards
I joined the Oxide and Friends annual predictions podcast episode this week - here are my 1, 3 and 6 year predictions for AI and LLMs (and KΔkΔpΕ parrots) simonwillison.net/2026/Jan/8/l...
08.01.2026 19:44 β π 126 π 18 π¬ 12 π 5
Oxide and Friends first pod of the year is up! And predictions are open if you have some ones you'd like to get on record: github.com/oxidecompute...
08.01.2026 16:39 β π 15 π 2 π¬ 0 π 0
New year, new Oxide and Friends predictions episode! @bcantrill.bsky.social and I were joined by @simonwdc.bsky.social and @steveklabnik.com to predict 1, 3, and 6 years into the future. Winners from previous years? Apple in and out of the VR/AR business? Looking prescient! Agents not a thing? Sure!
07.01.2026 18:13 β π 33 π 5 π¬ 4 π 1Love your customers bcantrill.dtrace.org/2025/12/31/l...
31.12.2025 20:11 β π 57 π 8 π¬ 1 π 0
In a move eerily reminiscent of my own accurate-but-wrong three-year prediction of the iPhone in 2003, @ahl.bsky.social wanted to predict vibe coding in 2023 (!) -- but then dismissed it because "I don't know who is going to debug that" youtu.be/6nQbe9EYFaw?...
27.12.2025 21:24 β π 34 π 1 π¬ 2 π 0What does it mean to love our customers? FAQ Friday #32
26.12.2025 19:25 β π 34 π 2 π¬ 0 π 1
Last OxF of the year! @bcantrill.bsky.social and I reflected on the year of Oxide and Friends. Big theme this year? Bugs and debugging. Or as ChatGPT put it inaccurately, "filled with painful specificity and earned insight". Sure, whatever! youtu.be/kGNoSYQchS8
21.12.2025 00:28 β π 14 π 3 π¬ 2 π 0Why do Oxide Compute Sleds have one processor? FAQ Friday #31
19.12.2025 16:18 β π 41 π 1 π¬ 3 π 0How have servers and the cloud evolved in the last 30 years, and what might be next? @bcantrill.bsky.social has been at the thick of the industry since the Dotcom Boom, and shares fascinating stories.
Bryan is one of my all-time favorite people to talk with - don't miss this one.
(cont'd)
It's our last episode of the year -- so @ahl.bsky.social and I will be engaging in our @changelog.com-inspired annual tradition of reviewing the year of episodes. Join us at 5p Pacific -- and bring your own favorite moments!
discord.gg/QrcKGTTPrF?e...
Another awesome @monktoberfest.com talk by @bcantrill.bsky.social ! It's absolutely worth watching the whole talk, but I think the last bit is great way to wrap up, where Bryan talks about broken institutional and organisational trust using RTO example:
www.youtube.com/watch?v=WF7J...
β’ self-service update without Oxide involvement
β’ SCIM 2.0 support for instant user and group management via identity providers
β’ Additional role-based access controls
Read More: buff.ly/5FHE5JV
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:
Can Oxide Run in an Air-Gapped Environment? FAQ Friday #30
12.12.2025 16:43 β π 21 π 2 π¬ 0 π 0
I love getting to work on strange debugging problems and get to learn a little more about a system oxide.computer/blog/cosmo-sp
11.12.2025 15:57 β π 74 π 14 π¬ 4 π 2Look, I know you think that @oxide.computer only builds computers to turn interesting bugs into podcasts, but that's obviously not true: we also write blog entries
11.12.2025 16:05 β π 99 π 6 π¬ 3 π 0I have put together a (long overdue!) draft RFD on using LLMs at @oxide.computer, but I know that there is a ton more to be said on the topic; thoughts and experiences welcome!
rfd.shared.oxide.computer/rfd/0576
Is Oxide ideal for CI/CD runners? FAQ Friday #29
05.12.2025 16:18 β π 7 π 0 π¬ 0 π 0
Why do you want to work for Oxide? I have spent nearly two decades dealing with servers in different personal and professional settings. I have been a customer of Dell and of HP. I have watched for a long time an industry that has seen no lasting, ground-breaking improvement in commodity server technology (especially for scale) since the advent of rack mountable servers with Intel x86 processors. We stand in the long shadow cast by deeply proprietary, but historic and visionary technologies from large companies like DEC, and IBM, and Tandem. Technologies that were defined at least in part by the joint engineering and deployment of hardware and software to provide ground-breaking reliability and features mostly unmatched in more open, commodity systems today. We have an opportunity to build on decades of isolated advancements in commodity software and hardware. To bring together open and commodity components, both new and existing, into one engineered computing system that scales from a single rack up to a warehouse. We can build, as a product and an ecosystem, the kinds of computing platforms that are today bespoke within the walls of the hyperscalers like Google and Facebook and Microsoft. Most importantly, though, we can do it all while building a fantastic team, united in a shared mission, a shared set of values, and a shared trust!
Reflecting on my application materials after six years at Oxide, and I feel that I continue to stand by all of this.
05.12.2025 05:59 β π 51 π 2 π¬ 0 π 2
