Our $100M Series B
474 comments
·July 30, 2025neom
zem
I'm a fan just because they have such an incredibly good sounding product. like, it has no relevance to me, I'll never use it, but I get a deep sense of satisfaction just reading about how it works.
sethops1
I was skeptical as well, if only because just being a better product isn't enough to win the market. Everything we hear about Oxide sounds like an impressive green field implementation of a data center, but is that enough? Do the people making buying decisions at this scale care if their sysadmins have better tools?
esseph
I imagine most of the customers are highly technical, not typical generic business class.
9dev
If it translates to improved efficiency, sure. And this big of a round seems to indicate that idea has some merit
zer00eyz
> Do the people making buying decisions at this scale care if their sysadmins have better tools?
Look at who oxide is selling to and for what reasons.
It's about compute + software at rack scales. It does not matter if it is good it matters that it's integrated. Gear at this level is getting sold with a service contract and "good" means you dont have to field as many calls (keeping the margins up).
> Everything we hear about Oxide sounds like an impressive green field implementation of a data center, but is that enough?
Look at their CPU density and do the math on power. It's fairly low density. Look at the interconnects (100gb per system). Also fairly conservative. It's the perfect product to replace hardware that is aging out, as you wont have to re-plumb for more power/bandwidth, and you still get a massive upgrade.
keeda
As someone only tangentially familiar with this domain, I have questions about this:
> Look at their CPU density and do the math on power. It's fairly low density. Look at the interconnects (100gb per system). Also fairly conservative. It's the perfect product to replace hardware that is aging out, as you wont have to re-plumb for more power/bandwidth, and you still get a massive upgrade.
It sounds like the CPU density and network bandwidth are not great. If it's only suitable to replace aging systems, does that not limit their TAM? Or is that going to be their beachhead for grabbing further market share.
transpute
What percentage of enterprise IT compute has not moved to a public cloud?
chadk
Only 30% have moved to the public cloud
https://www.goldmansachs.com/insights/articles/cloud-revenue...
cortesoft
I know I have been involved in multiple efforts to move the same workloads into and then out of the cloud, as corporate budgeting requirements prioritized either capex or opex at different times.
esseph
Every single company I've worked with over the past 5 years has been repatriating from the cloud to their own DCs or colo.
The cloud doesn't pan out for long running, predictable workloads. Most companies are and will continue to use VMs for many years.
dmoy
I'm not sure anyone really knows
uptime institute publishes some good numbers from survey, which puts on prem + colo still at >50% last I checked.
And still some additional 5% in like... on prem in closets.
Last year Amazon said it was 85% on prem. I dunno who has the right numbers.
unicornhose
I must admit that I am much more unsophisticated than this, and yet I "invested" in Oxide (by running my own projects off Oxide servers), and it is gratifying to see them continue to grow. My (naive) assessment: (a) agreed with Cantrill's opinions on software, (b) liked his willingness to put himself out there, and (c) felt the eng blogs showed a high level of (socio-)technical ability.
I think for the internet to break out of walled gardens, high-quality independent datacenters need to exist -- nobody wants to manage their own datacenters, and nobody wants to rely on Google/Amazon/Microsoft's platforms or (even worse) business products. I hope this continues.
cpach
Did you order a unit from them or how did you manage to get access to the Oxide hardware?
throwpup666
I still dont get it. If someone else's software is running the hardware, what difference does it make if its on-prem or offsite?
steveklabnik
> If someone else's software is running the hardware
Our stack is open source.
> what difference does it make if its on-prem or offsite?
The difference is not where it runs, it's that you own our racks, rather than rent them. In the traditional cloud, you're renting. Other vendors who sell you hardware will still have you paying software licensing fees, so it never feels like you truly own it. We don't have any licensing fees.
stavros
I like you. Are you guys hiring?
doctorpangloss
First let me say I really like this part of your guys narrative: you have really strong opinions about how infrastructure and IT should work at many levels, like technically and aesthetically, that seems real and nice and likable.
Focusing on just this financial narrative you're weaving, what stops a bank from selling "virtual racks" that work financially the same as owning an Oxide rack, but it's just AWS?
$1m buys you 42U of, whatever. You're handed an AWS account you do not pay for, but it has the $1m worth of, whatever in it, in perpetuity. Maybe the bank even throws in some fakey market you can "part out" and "sell" your rack to, years later, at some "market price."
It seems like, the product - and maybe the experience of buying the product - is what is most important to Oxide. It's really interesting to me, because I cannot wrap my head around what this narrative is:
You guys are Apple of Racks. But minus the iPhone, because there is no monopoly here. So, Apple (Minus iPhone) of Racks. Is that it? It's the rest of their offerings, which without the iPhone monopoly effects, are Buying Experiences. It's like when people buy $10,000 Mac Studios to "run LLMs", which of course they are going to do like, zero to one times, because they are excited about the idea of the product. For the audience that needs to "run LLMs" they buy, whatever, or rent. But they don't buy Mac Studios. Just because people do something doesn't mean it makes sense.
Is the narrative, AWS Doesn't Make Sense? AWS makes a ton of sense, for basically everyone. Everybody uses it and pays up the wazoo for it. And there are good objective reasons AWS makes sense, at basically all levels. Who is fooled by, "AWS doesn't make sense?"
The problem with AWS isn't even that they are expensive. It's that Amazon is greedy. It could be cheaper, which is a different thing than being expensive. It matters because "AWS stays greedy longer than the average Y Combinator company stays private" is an interesting bet for an investor to take. They could decide to be less greedy at any time, and indeed, it did not take long after offerings of S3-like storage from others led them to simply reduce prices.
What that is telling me is, I could take $100m in funding, sell $1m "racks" of equivalent compute on the Rolls Royce of cloud infrastructure, making everything financially and legally and imaginarily the same as ownership, and then take a $300k loss, right? On each "rack", same as your loss? It's a money losing business, but here I am making the money losing very pure, very arby. Is this what you are saying customers want?
Clearly they want a physical rack. By all means, I can send them a big steel box that provides them that aesthetic experience. Cloudflare, Google, they do the physical version of this all the time: dumb, empty appliances that are totally redundant, because people ask for them. RudderStack, Weights & Biases, a bunch of companies come to mind doing the same thing in software, like so called Kubernetes Operators that literally just provision API keys but pretend to be running on your infrastructure. People ask for Kubernetes operators, they made them, but of course, they don't do anything. They are imaginarily Kubernetes operators.
The reason there are licensing fees and rentals and whatever is the enterprise sales pipeline, right? Enterprise sales is, give people want they ask for. People ask for a price that's below $X up front, so that's what IT vendors do, and then it turns out people are okay with some ongoing licensing fees, so there. That's what they do.
So what IS it?
vatican_banker
Banks care _a lot_ where the data is store, hence most banks are inclined to keep customer data on-prem.
Because data must be on-prem, banks are stuck in legacy infra paradigms. The whole org suffers, innovation is stiffled, yada yada…
An on-prem cloud product (hardware+software) is a game changer for these companies, IMO.
My question to oxide: how easy is to integrate external hardware into the cloud? For example: bunch of GPUs or a bunch of next-gen hardware like SambaNova.
transpute
Is the software open-source with reproducible builds of any runtime binaries?
Oxide has been remarkably transparent about the development and architecture of critical system components. We can only hope they succeed and inspire others to follow their transparency lead.
gtirloni
Open source is a requirement but not the only one. There are countless examples of companies building integrated solutions based off of open source projects that, when they went bankrupt, there was nobody to pick up the available pieces and continue moving the stack forward. Just pointing out that open source is not this magical escape hatch that some people think (at least not in corporate environments).
null
bpt3
Cloud computing is significantly more expensive than self-hosting for most large organizations. People are slowly figuring that out, and Oxide was a bet on the timing of that realization.
Aperocky
That's almost always been true but servers are more like commodities at this point.
iphone is nice and upgrade from commodities phone and I have one, but I wouldn't care much if my fridge has sleek UI because I just need it to be a fridge.
null
null
0xbadcafebee
Even if it makes no sense as a technical thing, businesses will buy it. Look at all the huge companies that keep spending millions trying to DIY their own datacenter for the 3rd time. Enterprise loves to buy big iron and self-hosting crap, so I'm sure they will be successful selling this. However, I think they're going to need to branch out to more services in order to continue increasing their revenue every year (after 5+ years lets say).
mike_d
> Look at all the huge companies that keep spending millions trying to DIY their own datacenter for the 3rd time
You mean all the huge companies that ran multiple datacenters before the cloud was even a thing?
null
mrcwinn
Everyone at Oxide makes the same salary:
>We decided to do something outlandishly simple: take the salary that Steve, Jess, and I were going to pay ourselves, and pay that to everyone. [https://oxide.computer/blog/compensation-as-a-reflection-of-...]
Does everyone at Oxide have the same equity grant?
Aurornis
> Does everyone at Oxide have the same equity grant?
I thought I saw this question answered in a previous thread and the answer was basically “no”, but the question has been avoided a lot.
Aspects of equity compensation would inherently need to be different over time due to valuation, fundraising stage, and so on. However I always thought it was strange that they made a big deal about paying everyone the same base salary but then were silent on the equity comp strategy. Everyone knows that in a job like this the total comp is important.
The old Oxide compensation discussions were interesting. There was discussion about how they thought candidates asking about compensation to be something of a negative signal because they wanted people who weren’t in it for the money, basically. I heard this from a now ex-employee of Oxide who was describing how to navigate their hiring process, so take with a grain of salt.
EDIT: I checked their website again. The compensation link goes to a blog post ( https://oxide.computer/blog/compensation-as-a-reflection-of-... ) which has this section about equity:
> Some will say that we should be talking about equity, not cash compensation. While it’s true that startup equity is important, it’s also true that startup equity doesn’t pay the orthodontist’s bill or get the basement repainted. We believe that every employee should have equity to give them a stake in the company’s future (and that an outsized return for investors should also be an outsized return for employees), but we also believe that the presence of equity can’t be used as an excuse for unsustainably low cash compensation. As for how equity is determined, it really deserves its own in-depth treatment, but in short, equity compensates for risk – and in a startup, risk reduces over time: the first employee takes much more risk than the hundredth.
Which doesn't answer the question.
mystraline
> There was discussion about how they thought candidates asking about compensation to be something of a negative signal because they wanted people who weren’t in it for the money, basically.
I've heard this from multiple hiring managers and C levels. The cognitive dissonance is amazing.
Do you know why I show up and work? Because I am paid for it, and in this country, medical is also gatekept by employment.
If I wasn't paid, I wouldn't work for them.
But somehow, I'm supposed to not care about money at the same time caring about money.
rtpg
Back when my salary was shitty I cared about the money a lot.
I still like the money and the number going up. But now that it’s above a certain multiple of what I consider a “comfortable” life, I’m not worrying as much.
Would for change your job for an extra 500k a year? Surely right? An extra 50k? An extra 5k? An extra 500 dollars a year?
Theres some mental calculus that includes everything. Some people will just take “offer with most money” every time. Hell of a lot of people don’t.
I do think that C suite folks might not have the right vision of what “normal/comfortable” is for employees though. So they might offer a low number thinking it’s actually a “comfortable to live with at this stage of life” number and then get confused why they can’t recruit good talent and think people are obsessed with money.
First offer has gotta be within the ballpark of the right number if you don’t want your interviewee to immediately come back to you with a much higher number!
dpritchett
It’s a bit of a class thing, isn’t it?
Independently wealthy folks can stay in the game longer without needing to extract a lot of cash compensation in the company’s early years.
diggan
> If I wasn't paid, I wouldn't work for them.
That's great, but useful to know not everyone thinks the same. When I transitioned to software development (from basically random "whatever pays my rent" jobs), besides my first software job, they were all because I liked the particular product in some way or another, and what the compensation was is basically the least interesting thing for me.
Of course, some level of base payment is needed, because I still needed to pay rent, but if I was choosing between two jobs where one was utterly boring but paid 3 times more than a fascinating job, I'd take the latter in a heartbeat. And no, I'm just an individual contributor who wants to like what I work with, not an executive, manager or similar.
mlyle
I think we live in a better world when the primary motivator for how we spend half of most of our working day isn't doing what's necessary to get strips of paper for survival.
That is, the work itself should be interesting and fulfilling.
Yes, we need money, but when the work relationship approaches being purely transactional the whole thing is demeaning for everyone and less effective.
Boy, it takes a lot of luck and skill and privilege to be able to shop for (or offer) work like this, and money is still important.
Keyframe
If I wasn't paid, I wouldn't work for them.
While this is true for most of the cases, it's not the case always. There are definitely jobs I'd work for less than I make at the job now and there are jobs which are considered "dream jobs", but ultimately there needs to be a solid base to make you and your family feel comfortable if you're spending at least 1/3 of your day on.
inerte
They know it's a lie but still need to say it.
I used to have a manager that gave me this line. He left this company to join another one, had multiple offers, and told me he accepted the highest one because "it's all about the money".
They know, we know, everybody knows, but that's not the playbook.
null
conjectures
> There was discussion about how they thought candidates asking about compensation to be something of a negative signal
It's not an unusual way of thinking, but every time I see it, it seems bizarre to me. If the candidate was to propose any project once hired, I'm sure these folks would want them to think about costs and benefits.
This policy selects either for people unable to reflect on their life with the same wit they apply to work; or people who will front about their motivations. Both seem like poor outcomes.
oooyay
> The old Oxide compensation discussions were interesting. There was discussion about how they thought candidates asking about compensation to be something of a negative signal because they wanted people who weren’t in it for the money, basically.
I can't say anything of Oxide because I don't really know the people involved other than reading their writing.
This is an attitude a lot of industry veterans have. Most of them were in software pre-2015 and have long made their money and paid their debts. They saw the haydays of job hopping, massive salaries, massive equity, and "rockstars" (that never were). The people I know that joined software post-2015 and onward are not in the same financial position.
ethbr1
Anyone who doesn’t ask about compensation (at least at a later point in the interview process) would be a red flag to me.
Most valuable people know they’re valuable, and do (and should!) negotiate compensation.
steveklabnik
I am not sure I fully agree with the characterization above (that asking about salary is a 'red flag' in our process), but if I had to try and steelman it: we prominently put
> Everyone at Oxide makes $207,264 USD, regardless of location. (Some sales positions have a lower base salary and contain a commission component.)
On our applications page (see it here: https://oxide.computer/careers/sw-control-plane)
It's also a pretty well known aspect of the company. Combine this with the fact that our hiring process is different, where interviews are the very last thing before possibly being hired, and someone who has missed this fact could come across as having not done some very basic research about the company that they're applying to.
To be clear, I still think calling it "a red flag" is a stretch. I fully agree with you in a general sense, for places that are willing to negotiate compensation in the first place, but we make it very clear up front that we do not.
Aurornis
Red flagging a candidate for not asking about compensation during the interview is not a good practice. This is an example of penalizing people for not following a specific script or candidate archetype you have in mind instead of judging them by their skills and abilities.
ge96
self esteem problem ha (not asking or thinking low)
tshaddox
> There was discussion about how they thought candidates asking about compensation to be something of a negative signal because they wanted people who weren’t in it for the money, basically.
I think companies avoiding discussions about compensation is a negative signal, because they’re only in it for my labor.
999900000999
At this point I've accepted most equity comp in a non public company is worth less than toilet paper.
When it comes time to actually cash out or you notice some animals are more equal than others, the excuses start. The drama happens. No one knows what the equity is worth. If you try and advocate for yourself you'll be told the equity is actually worthless.
From here the 200k salary seems fair. Just don't live in SF. Chicago , Philly, Pittsburgh, Cleveland, quite a few cities are perfectly livable on 200k.
In fact, in any of the above metros you will be living nice.
timerol
> Does everyone at Oxide have the same equity grant?
> equity compensates for risk – and in a startup, risk reduces over time: the first employee takes much more risk than the hundredth.
I think that paragraph answers the question pretty clearly. As an Oxide employee you will get equity. It will generally be less than the people that came before you, but more than people that come after you. So it's obviously not the same as everyone else
Aurornis
It doesn’t answer it clearly at all.
Do two people hired at the same time get the same equity? Or is there room for one candidate to get more equity due to their experience or simply because they negotiated more?
Obviously early employees get more equity. The question is whether or not there’s room for negotiation. They heavily imply that everyone is paid the same, but all of those claims are about base salary.
singron
"total comp" (salary+equity) is really hard to quantify for a private company. In order to qualify as ISOs, the stock options need to be priced at the Fair Market Value (FMV), which makes them essentially worth ~$0 on paper on the day they are granted. In order to value them differently, you need to guess if/how the company will increase in value in the future. If the gains were guaranteed, then that should be factored into the current FMV, so options always have significant uncertainty.
This is unlike an RSU from a public company, where you can sell the value of your shares as they vest and add that to your income with minor risk of price volatility.
illegalmemory
They have since updated it slightly
> Since originally writing this blog entry in 2021, we have increased our salary a few times, and it now stands at $207,264. We have also added some sales positions that have variable compensation, consisting of a lower base salary and a commission component.
ekianjo
so basically everything converges to having specific reasons to have different salary schemes.
ArnoVW
One exception, for sales. I don't see how they could have done it differently.
We have a "one rate per level" rule. The rates are published, and so are the definitions of the levels, and everyone's level (i.e. indirectly you can know everyone's salary)
Worked great, untill we started to look for sales. Doesn't work. They only know incentive-based schemes.
So now they have an incentive-based scheme just for the sales, which is (essentially) budgetted from their stock-option package (that everyone gets). I.e. they benefit from growth a little bit earlier and directer.
If we hadn't done that, we wouldn't have a sales department.
liamkinne
Yes, but you aren't wasting time early on negotiating compensation.
IncreasePosts
Why is sales special? Why not just have some performance bar for that, just like all the other positions?
castlecrasher2
Because good sales staff make a ton of money through a ton of sales. Any other incentive structure is unlikely to attract high performers.
darren0
It's pretty fundamental to the personality of people in sales to be driven by getting the sale and getting compensated based on the deal size. If you remove that carrot, it just doesn't work. Some sales people will make millions, some will make nothing.
OkayPhysicist
The key difference between everyone else in a company and Sales is that Sales is where the money comes in, directly. It's approximately trivial to point at a sale, see how much money it made, and then who made the sale. So commission is a natural compensation structure for salespeople. For everyone else at a company, their individual contribution to the company making money is a lot more diffuse, and any metric you might be tempted to try and put a commission on is at risk of being gamed. Whereas "how much $$$/worth of stuff did we sell" is pretty much THE metric by which we judge a business as a whole.
rubicon33
If you’re asking this question then you have really no idea how the sales engine works at a company. It’s inherently incentive driven.
sofixa
Because sales people are used to work on incentives, including going over and getting rewarded for it.
If they have a fixed salary with a high objective to "make it" (e.g. if you sell less than $X, you get fired), lots of sales folks will skip on it because they can't go over, and most probably prefer to have a quarter or two or year at e.g. 70% salary while working on longer term deals, rather than losing their job for not being good enough within that arbitrary time period. And going over their quota can be wildly lucrative depending on the terms.
hiddencost
Sales culture is heavily incentive and performance based.
It sucks but they like to think that if they work harder they'll get paid more.
Etheryte
Out of curiosity, how would you imagine that working out, technically and specifically? You start out with founders having equity, and maybe some early investors. Then you employ some people and... what happens exactly? Are new shares created, is everyone who was already onboard slowly diluted, what happens when someone joins and leaves? Etc, I don't think there is an approach to this where all sides would be happy, so I'm interested to hear your thoughts.
steveklabnik
Not your parent, and not suggesting in any way that Oxide is one, but the key term you want to search to learn more about that kind of arrangement is "worker owned cooperatives." There's a lot of variety in how it's handled.
dustingetz
indeed, founders are generally compensated at half the competitive rate
kortilla
This has been the biggest red flag to me about oxide since these blogs came out. You don’t join a startup for salary and every startup I’ve been at that emphasizes fair salaries is doing that to intentionally discourage people from pushing on total compensation.
Employees apart from the very early ones are likely really getting fucked on equity because oxide explicitly treats candidates asking about equity as a red flag.
Companies structured like this end up turning into a combination of rich people who don’t need money and are just interested in the problem space and then mediocre people who can’t get a better offer. (If you are good, remote work with high TC is definitely available.)
Unless Oxide is giving out huge equity bonuses for good perf (which would make their comp post hypocritical), it’s going to have a continuous talent decline as it grows. There aren’t enough independently wealthy high performers interested in what Oxide is doing to sustain a talent pool.
mwcampbell
> (If you are good, remote work with high TC is definitely available.)
But how good do you have to be at things other than the work itself (edit: and how lucky as well) to land one of those jobs with higher compensation? For someone outside of high-cost-of-living tech hubs, Oxide's fixed salary could be life-changing all by itself, even with minimal equity. The fact that they take that deal doesn't necessarily mean that they're mediocre.
Aurornis
> For someone outside of high-cost-of-living tech hubs, Oxide's fixed salary could be life-changing all by itself,
I’ve spent a lot of time looking at compensation tables and reference data. $200K is definitely good salary, but I wouldn’t call it “life changing” relative to what someone qualified to work at Oxide could earn in an average non-tech hub metro area.
The type of candidate who qualifies to work at Oxide has numerous options for high paying remote work, and probably well paying local work too.
actionfromafar
That would be even more outlandish, I don't think that's possible.
lumost
It depends, there are certainly founders who come from sufficient money that the value of founding a unicorn is not material to their Net worth.
However I’d also suggest that the concentration of tech in the last decade is also partly due to startups chronically stiffing their employees on equity. The difference in compensation potential naturally forces a talent split where talent joins larger and much better compensated firms.
NewUser76312
Of course not, what's the purpose of asking such as silly question?
Are you being snarky and suggesting that employees deserve the same upside that founders deserve?
diggan
> Of course not, what's the purpose of asking such as silly question?
How is it silly if they already do that for salaries? Co-ops with equal ownership isn't unheard of, and isn't silly at all.
AngryData
Yeah they aren't unheard of at all, co-ops have had slow but steady growth in the market for some decades now.
Aurornis
> Are you being snarky and suggesting that employees deserve the same upside that founders deserve
The founders are excluded from the employee compensation discussion. They own the company because they founded it. Nobody thinks they just put the equity into a structure that nobody owns.
The question is whether all employees are compensated equally, which is a very important detail. Giving everyone the same salary is very different than giving everyone the same total compensation.
TrackerFF
A company can't function without employees, so why not?
shortrounddev2
Salary and equity have nothing to do with what you "deserve", only what you're able to negotiate.
lumost
For early/mid stage startups - this is an awful position to take. These orgs are heavily influenced by who they hire - what you pay defines your incentive structure.
Does the world class engineer or business development lead just take it easy and travel around after they join?
Does the new manager push the team and business forward or prioritize stability?
Do engineers spend their time on reactors and impressive sounding projects or figuring out what customers need?
Do people feel lucky to have a seat in the org or do they spend their time complaining and looking for the exits?
Money isn't the only lever, but its a strong one - startups will never compete with established firms on cash outlays.
maerF0x0
Would love to engage in a discussion with you on this. How would you describe "deserve" in the sense of compensation? I agree with your premise that what you get is ultimately bound by the ceiling of the payer's generosity and your ability to negotiate.
But what sorts of things input into the function of "deserve"?
lostmsu
A lot of people with broken /s detector are replying to this comment.
diggan
It would seem like parent's something detector is off if they think the grand-parent's comment was snarky.
sneak
That isn’t a snarky position; early employees in high output orgs like this generally work just as much as founders do.
The founders aren’t really taking on that much more risk than the rest of the early team; it’s the VC’s money, not theirs.
I absolutely don’t agree with the idea that employees deserve the same upside as founders (because I think initiative and persistence against adversity/inertia is insanely rare and valuable and should be rewarded immensely), but it is not an insane proposition.
It’s especially popular among people who think the actual work output is more important than the leadership initiative. Both are obviously essential, and founders do both, while employees do only the first (or they’d be founders themselves).
no_wizard
>rewarded immensely
Let’s define this. Let’s say 1:25? 1:50? What ratio is appropriate?
siliconc0w
Pretty bullish, anyone who has tried to setup and manage their own compute knows the pain they're solving.
Plus I predict more companies will exit the cloud once they realize how thick the margins have become or want better guarantees over sovereignty.
jillesvangurp
I actually think that having more cloud providers might deflate a lot of the pricing. If you think about it, companies like Amazon buy server hardware and then rent it out by the vcpu (with throttling if they can get away with it) per month. Add memory and IO and you are looking at bills that pay for the server in mere months/weeks several tenants carving up all the hardware and each paying tens/hundreds per month.
There are of course benefits to using cloud based VMs and I use them as well. But you are paying a very steep premium for what is a pitiful amount of compute and memory. There's a lot of wiggle room for price decreases and the only thing preventing that is a lack of competition. There's a reason Amazon is so rich: nobody seems to challenge them on AWS pricing. There's value in having them do all the faffing about with hardware of course. That's why companies use them. I'm in GCP; but same principle. I don't want to have to worry about replacing hard disks in the middle of the night, deal with network routers that are misbehaving, cooling issues, etc. That's why I pay them the big bucks. But I'm well aware that it's not that great of a deal.
I used Hetzner a decade ago and paid something like 50 euros per month for a quad core xeon with a raid 1 disks, 32 GB, etc. Bare metal of course. But also, 50 euro. We had five of those. Forget about getting anything close to that with modern cloud providers for anything resembling a reasonable price. Your first monthly bill might actually add up to enough to buy your own hardware. Very tempting. They have beefed up their specs since then. You now get more for less. And they also do VMs now.
throwup238
I knew it was bad but I didn’t realize just how bad the pricing spread can be until I started dealing with the GPU instances (8x A100 or H100 pods). Last I checked the on-demand pricing was $40/hr and the 1-year reserved instances were $25/hr. That’s over $200k/yr for the reserved instances so within two years I’d spend enough to buy my own 8x H100 pod (based on LambdaLabs pricing) plus enough to pay an engineer to babysit five pods at a time. It’s insane.
With on-demand pricing the pod would pay for itself (and the cost to manage it) within a year.
wordpad
That's just hardware. If you need to build and maintain your own devops tooling it can balloon in complexity and cost real quick.
It would still likely be much cheaper to do everything in house, but you would be assuming a lot of risks and locking yourself in losing flexibility.
There is a reason people go with AWS over many competing cheaper cloud providers.
time0ut
In my experience, companies seem to want to pay the cloud provider tax in order to avoid capacity planning. Sometimes it makes sense because it is hard to predict when something is going to take off. I have also worked at companies with very predictable growth paying insane amounts. I didn’t understand the logic, but they still were profitable and paid well so whatever.
bambax
At the (very) low end it's pretty easy to build your own "cloud" with a NAS, containers, and reverse proxies and tunnels to the outside world. And this will get you suprisingly far.
But at the high end, I think the market is litterally infinite. Every large company should want this, and want it now. Cloud providers are extremely expensive and, outside of the 1-tier where prices are really outrageous, they perform poorly and often offer little support.
This really feels like the future.
boricj
> At the (very) low end it's pretty easy to build your own "cloud" with a NAS, containers, and reverse proxies and tunnels to the outside world. And this will get you suprisingly far.
Anyone can throw together a bunch of parts and software to run Internet-facing services from a closet. That doesn't mean that you're safe from issues that Oxide aims to solve, especially at that small scale.
My homelab (which hosts my blog and a couple of other things) runs off a Topton N17 micro-ATX motherboard ordered on AliExpress, featuring an AMD Ryzen 7 7840HS. Yes, that's a mobile CPU shoehorned onto a desktop platform with a funky mounting bracket to take AM4/AM5 coolers.
Anyways, I wanted to run SmartOS on it, but this system is so janky that the Illumos kernel couldn't find any PCIe devices at all. After spending an afternoon reconfiguring PCIe bridges by hand with the kernel debugger in an attempt to troubleshoot PCIe initialization, I gave up and installed Proxmox.
Admittedly, as far as janky hardware this takes the cake, but the point stands. To paraphrase Bryan, buggy firmware is the sysadmin's worst enemy.
naikrovek
like us old assholes were saying when the cloud really started to take off: "this is nuts, it's just someone else's computer! and they're making a profit off of this service, meaning it's more expensive than what we were doing!"
Now a lot of the things that were done pre-cloud were done in bad ways, and I'm not saying that we were right about those things. Having APIs for provisioning and monitoring are far better than submitting a request to some queue and having your VM provisioned manually 1 week later by someone who gets a key detail wrong. APIs and granular permissions are how this should be done, and "the cloud" taught everyone that very early. But a lot of companies are really stuck in the cloud mindset now, and won't let go of it.
I think companies like Oxide and product lines like theirs are going to start becoming common. Microsoft, of course, completely fumbled the ball with Azure Stack, and I've never even heard of anyone deploying AWS Outpost, both for the same reason: the costs for these are absolutely insane for what they provide.
What most folks really want is their own infrastructure running their own stuff using APIs that are either written in-house or provided by some vendor. Oxide is betting that they can sell you a working scalable system for less money than it would take to hire a team to write the APIs that would allow a company to do the same with off-the-shelf hardware. I think that they're probably right about that.
jeffbee
> they're making a profit off of this service, meaning it's more expensive than what we were doing!
I hope you can see that this is a logical fallacy known as "zero-sum thinking". It is not only possible for a business to profit while lowering prices, it is universal throughout the economy. Tomato farmers make a profit selling tomatoes at a price much lower than the cost to grow tomatoes at home. Bakeries radically undercut the cost of home baking. It is obviously cheaper to buy motor fuel at the gas station than it would be to buy crude and refine it yourself.
The main reason people think their on-prem is cheaper than cloud is that they are bad at accounting.
master_crab
I don’t disagree that there are some fat margins in the cloud, but how is vendor lock-in any different here? Companies could end up paying fat margins to oxide too while still managing physical gear and plant.
TZubiri
Well, their servers are mostly hypervisors, so the interface is mostly any virtual machine.
You can "just" migrate by exporting or importing the vms.
yencabulator
You're literally ignoring that the Oxide management stack is very much custom and effectively vendor-locking the purchase to be maintained by them. They are not general purpose PC servers.
You can "just" migrate away from Oxide but that would mean throwing away the hardware you now own. That's the grandparent's point; if you're migrating out of a cloud to avoid the margins demanded by the cloud vendor, now you're at the mercy of whatever Oxide thinks your support contract is worth.
Sure, the convenience may be worth it, but watch how many companies are now struggling to get off of VMWare after Broadcom moves.
AndrewKemendo
Having done web applications for oh…30 years now the key pain is network routing
That’s the only thing I can tell is useful about “the cloud”
I can build racks and servers easily, but the challenge is availability and getting past everyone’s firewalls
So the real win is any service that allows for instant DNS table updates and availability of DNS whitelisting.
This is why Google, Msft etc win in email because they have trusted endpoints
Alternative routes with self signed DKIM etc is more or less blocked by default forcing you onto a provider
We need more cloud flare tunnel and local hosting via commercial ISP routes and less new centralized data centers
chrisweekly
+1 Insightful.
I've also been doing web-related work for a living for over 25y and yours is the most spot-on take I've seen in this discussion.
AndrewKemendo
Thank you :)
davinoishi
[dead]
geodel
Agree. But those fat margins can get starting to be shared with CIOs, CTOs and other managers with purchasing power. IMO the constant hectoring at workplace about migration to cloud or cloud native crap is not coming from some deep technical principles. It is more of Do it before you get fired for non-compliance
turnsout
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
> 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
That's helpful, thanks!
throw0101c
> 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
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?
dcminter
Oxide, at least for an outsider, looks like a company that channels some of the spirit of early Sun Microsystems (I'm aware of the connections of course). I'm quite envious of those who work there - I hope the demands of big money don't crush any of that spirit.
Sadly when I look at their jobs posted I don't see much that would line up with my skillset, but I keep an eye on them just on the offchance.
Quarrel
Right?
And such a clear value statement.
If I could, I'd invest. Sure, they might fail, but they're shooting their shot, and to me it has a clear differentiator that would improve the market for most of their users (if not the incumbents).
criddell
I wish there was a way for small investors ($25-50k) to get in. AFAIK, the only thing we can do is wait for an IPO and hope we can get in at a reasonable price.
throw0101c
Meta: Oxide has talked about the designs of their cooling [1][2][3], so I'm curious to know if they ever start offering GPUs how they'd handle that.
Folks seem to be moving toward liquid cooling[4] either to the rack/chassis[5] or even to the chip[6].
[1] https://oxide.computer/blog/how-oxide-cuts-data-center-power...
[2] https://www.youtube.com/watch?v=4vVXClXVuzE
[3] https://www.youtube.com/shorts/hTJYY_Y1H9Q
[4] https://blogs.nvidia.com/blog/blackwell-platform-water-effic...
[5] https://datacentremagazine.com/data-centres/top-10-liquid-co...
jvanderbot
Oxide's blogs talk about cooling _a lot_, apparently their stack runs very cool b/c they've reorganized the whole thing around efficiency, and written all the firmware to support that goal.
vonneumannstan
Skeptical of that. There's only so much you can do against the physics of moving electrons around at high speeds... "Bigger Fans" and "compute density" doesn't change that
sunshowers
Commodity hardware doesn't quite tend to operate at a compute vs efficiency Pareto frontier — there's a lot of wasted energy that we've been able to optimize with our vertical integration. (I work at Oxide.)
pmichaud
I don't have any particular knowledge about oxide's cooling, but think about how bloated and inefficient literally every part of the compute stack is from metal to seeing these words on a screen. If you imagine fixing every part of it to be efficient top to bottom, I think you'll agree that we're not even in the same galaxy as the physical limitations of moving electrons around at high speeds.
capital_guy
I believe the fans are actually smaller. The rack is definitely quieter than other racks, but he says in the rear rack tour that it's quite hot. Check out these videos of it
[0] - https://www.youtube.com/watch?v=dHbgjB0RQ1s [1] - https://www.youtube.com/watch?v=lJmw9OICH-4
naikrovek
maybe you're not familiar with just how stupidly written most code is.
you're right that there are efficiency limits, but not once in my career have I ever seen anyone even attempt to write their code so that it is efficient to run, outside of gaming.
Aurornis
Oxide is doing some great things, but there’s only so much you can do with firmware tweaks. A CPU running any load at all is going to completely eclipse the power usage of everything else in the system.
Incremental improvements from things like more efficient fans and reducing the number of power conversions is great, but the power drawn by the CPUs or GPUs is on another level.
Rendello
If after that you're not satiated with data center cooling talk, Jane Street's Signals and Threads just did an episode about their cooling infrastructure a few days ago:
https://signalsandthreads.com/the-thermodynamics-of-trading/
suprgeek
In the era of anything even remotely AI-adjacent raising ridiculous amount of money - and proving to vaporware - this is one raise that makes me happy. We need more of the Bryan mindset (and less of Larry) to ensure that when the AI-Enabled future shows up we have some semblance of a fair society that works for all. https://www.youtube.com/watch?v=-zRN7XLCRhc&t=2047s
jvanderbot
There is something so calming and pleasant about a well-structured thesis statement:
> Our thesis was that cloud computing was the future of all computing; that running on-premises would remain (or become!) strategically important for many; that the entire stack — hardware and software — needed to be rethought from first principles to serve this market; and that a large, durable, public company could be built by whomever pulled it off.
Very clear and logical, stating from their first principle world view what the result could be if they succeed.
chubot
I would say it's very clear and logical ... but is it really "from first principles"?
I thought that Oxide was based on OpenCompute, which is basically the rack designs that Facebook open sourced, after hiring some Google employees to build their custom data centers. This project started in 2011:
https://en.wikipedia.org/wiki/Open_Compute_Project
https://github.com/opencomputeproject
Google definitely rebuilt the stack from first principles -- the data center was basically a huge embedded system, from power to racks to CPUs/memory/disk/network to kernel to user space to cluster software. (And no, they did not use Kubernetes.)
I have no idea how active the OpenCompute project is -- is Facebook still the main contributor, and are they still releasing their new rack designs?
And I also wonder how much Oxide has diverged from it? At least on the hardware side. On the software side, I guess the Illumos-derived parts and Rust parts are completely different.
Well, when they say they did their own:
- board designs
- microcontroller OS
- platform enablement software
- host hypervisor
- switch
- integrated storage service
- control plane
Then yeah it seems like maybe only board designs and the switch COULD have either come from or been influenced by OpenCompute, but maybe those didn't either. (I have no idea tbh)Maybe they only got the mechanical and power stuff from OpenCompute? i.e. the parts that change more slowly
bcantrill
We didn't use anything from OCP. When we first started the company, we thought we might use the enclosure (and considered ourselves "OCP inspired"), but there ended up being little value in doing so (and there was a clear cost). And on the stuff that we really cared about (e.g., getting rid of the traditional BMC), we were completely at odds with OCP (where ASPEED BMCs abound!).
So in the end, even the mechanical and power didn't come from OCP. We clearly build on other components (we didn't build own rectifiers!), but we absolutely built the machine from first principles.
hinkley
My read on the situation is that you copied OCP only inasmuch as OCP made some observations about physics and you made the same observations.
The most obvious change is that you guys use half-width, full length enclosures.
But I'm realizing now that I haven't looked at the OCP specs in a long, long time. I recall the common DC rail from some early Facebook papers on this topic, and I thought they were pretty similar to how you plug into power.
I just looked at the OCP power connector, and I would have lost any bet anyone was willing to make me about what they looked like. That's not at all where I thought we were. I think I understand now why you guys went to such pains getting the keyed connectors to work exactly right. Their power connectors look like something from a scifi movie, and not in a good way.
chubot
Ah OK, thanks for clarifying! I'm glad to see these kinds of machines being built, especially with so much open source software
jeffbee
How does the Oxide 48V architecture compare to what is known about the Google/OCP architecture? Does Oxide use single stage conversion, intermediate 12V buses, or ??
steveklabnik
We initially talked about OpenCompute, yeah, but as far as I know we ended up moving away from that years ago.
krelian
>public company
Why does it have to be a public company though?
steveklabnik
It is either that or acquisition, and we would prefer an IPO.
GoatInGrey
Speaking from the experience of 8 acquisitions/IPOs, your compensation structure will not survive public ownership. It could survive a PE acquisition, but definitely not public ownership (in my experience). I would recommend petitioning for a dual-class share structure to protect founding leadership.
bcantrill
Because VCs need to have a way to sell their shares within the (limited) lifetime of their fund.
ang_cire
Good for them! I used to walk my dog past their (office? warehouse?) in Emeryville, and when the weather was warm they'd have the doors open and the giant server stacks just sitting there, looking awesome. I guess it's not really a concern that someone will steal something that looks like it'd take a forklift to move.
The ultimate aspirational homelab setup, ngl.
manquer
Vandalism / sabotage would still be a concern even if theft isn’t ?
stego-tech
Congrats to Oxide on this milestone! I’ve been following their progress since discovering them in COVID, and would love to see them shake up what’s presently a stagnant marketplace with their product line. The idea of deploying a rack of kit on-prem that’s tightly integrated instead of wrangling multiple vendors of discrete components has a strong appeal, and while the proprietary hardware stuff did initially give me pause, their commitment to building atop Open Source quelled any lingering doubts I had.
Would love to see their growth result in more versatile options, like quarter-rack or industrial deployments someday. In the meantime, congrats on the successful fundraising!
piker
Aside from the actual product, On the Metal / Oxide and Friends are really great podcasts that manage to make programming topics entertaining and educational. Bryan Cantrill is wildly entertaining and knowledgeable at the same time. His co-hosts and guests are great, too, and I attribute a lot of that to feeding off of his energy and storytelling. Highly recommend, especially for Rust folks.
kensai
All the best! I personally came to know Oxide for their cool RFD culture. It's worth a read:
https://rfd.shared.oxide.computer/
Start from RFD 1 ;)
bcantrill
Just because it's hopelessly on-brand for us to offer up a podcast episode for everything, you may also be interested in our Oxide and Friends episode on RFDs with our colleagues Robert Mustacchi, David Crespo, Ben Leonard, and Augustus Mayo.[0]
[0] https://oxide-and-friends.transistor.fm/episodes/rfds-the-ba...
ghaff
I need to dive back in. Lots of distractions recently.
KetoMojito
Bryan you absolute legend. You give the best technical seminars i've ever watched (& countlessly rewatched). Ty for inspiring a generation of engineers. Best of luck with everything at Oxide!
chrishare
What was it?
cosmic_quanta
I love the idea. RFD 1 mentions taking inspiration from Golang and Rust proposal processes. The Haskell Foundation also uses the same proposal process, and I love it.
I'm a big proponent of the "writing is thinking" mantra. Unfortunately, in my experience, not all technical leaders value grassroots proposal processes like the Oxide RFDs
bflesch
the rfd interface looks really nice. I couldn't find the github repo for it, is it proprietary?
Edit: some popup on their page links to https://github.com/oxidecomputer/rfd but it's a 404
Edit2: it's at https://github.com/oxidecomputer/rfd-site
Rafuino
Great news for Oxide. I followed their podcasts for a while but they petered out and I haven't heard much about their products/growth for a while. Sounds like it's still viable.
USIT... what a cryptic website! Is it government-related (like In-Q-Tel) or private? Have no idea...
I'm a Bryan Cantrill fan so I'm glad this is working out, I was extremely skeptical of them at the beginning(on HN too), I think because I've built DCs for many years and was stuck in a mindset that served my use case, I've come around to Oxide. My main concerns originally were 2 fold: "this seems bougie", is there actually a market for this, and, is there a good interoperability story with mix and match. From what I could tell the answers were "yes" and "don't care" - I had thought this wasn't a great answer but it seems I'm wrong. I was chatting with Boris Mann just last week about them and he said "actually John that isn't correct, think of how much quick compute needs to come online and how much discreet compute is going to be required with low management overhead, they're doing just fine and that market will grow" - After that I did some research and pondered on it for a day - I think my friend is right and I am wrong, I think at this point Oxide is going to be a really strong name and I wish them the best of luck.