Live data from Hacker News

Our $100M Series B

oxide.computer

391–400 of 522 posts

Re: Our $100M Series B

#391
post #124

Earlier quoted context omitted.

No, it's just how sales works, it's almost always on commission.

Tesla salespeople do not work on commission. Also you can align incentives through stock grants which appreciate by you selling more.

> Tesla salespeople do not work on commission

I work with tech salespeople with a variety of former employers as tech sales people, and I've never heard of anyone having worked without a commission. I'm vaguely in tech sales myself (solutions architect) and I'm on commission too, and so is everyone who joins our division from similar employment (solutions engineers/architect, or even customer success folks).

Re: Our $100M Series B

#393

Earlier quoted context omitted.

Yes, we're primarily an engineering company, not a research organization. It's also about what we don't have. We don't have a UEFI, for example, which means we don't have UEFI vulnerabilities.

Yeah and you're doing good work there. It just kinda annoys me when people go from "oh that's a cool company" into idolatry. 1U servers were always a poor form factor for modern day hot chips & drives. Breaking that mold has been done over and over and isn't something that should be treated as new. Scaling from the 8U (that blades could already do in the 90s) to full rack as the unit of "slide unit in to connect" DC…

I can't speak to others' views, but having worked with large-scale bare-metal deployments at Meta, I personally admired Oxide for its clear product vision and rigorous first-principles approach (Rust is a real game-changer!), and applied to work here for that reason.

Re: Our $100M Series B

#394

Earlier quoted context omitted.

Oh I would love to have some healthy competition to Linux, but I am not rooting for Solaris to do that, I'd rather have one of the Rust-based microkernel actually git gud. Time to shake the foundations of the age-old security and isolation models, not resuscitate a dusty old thing built on piles of C and shell on top of a large monolithic kernel and pretend everything's fine.

Well, good news: we have one of those too![0] [0] https://oxide.computer/blog/hubris-and-humility

Oh I am well aware. But I am hoping to run dynamic workloads, including virtual Linux machines, on a PC. It's a bit of a different world.

Latest one still in my to-read pile: https://lwn.net/Articles/1022920/

Re: Our $100M Series B

#395

Earlier quoted context omitted.

I'm not someone who works on this part of the product, but we talk a little about this stuff here: * https://oxide.computer/blog/how-oxide-cuts-data-center-power... * https://docs.oxide.computer/guides/introduction I feel like we had a good Oxide and Friends on this too... https://oxide-and-friends.transistor.fm/episodes/bringing-up... has some info about our power setup. Anyway, I barely know anything about this top…

Probably the sweet spot, since you can get to market fast with known 12V designs, but still enjoy the possibility of later announcing you've made the sled even more efficient by getting rid of the intermediate voltage!

At a certain point in EE power design you don't really want to go from 54V -> point of load for every rail (1.8V, 1.1V, 0.9V, SVI3 rails etc), so sticking with an intermediate voltage makes sense often even when viewing this from an efficiency perspective. Voltages such as 54V require different creepage and clearance requirements, so saddling every point of load regulator (of which we have many many!) with those requirements is often detrimental to an already complex board layout. Picking something like 12V or 24V as an intermediate voltage helps balance those requirements with the amount of copper you need for power delivery since the parts use low voltages but are extremely power hungry so your current at the point of load rail is a lot. This also means that your point of load regulators have to be distributed around the board near their loads otherwise the copper losses and noise would become problematic.

Re: Our $100M Series B

#396

Earlier quoted context omitted.

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?

> 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 licen…

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?

Re: Our $100M Series B

#397

Earlier quoted context omitted.

> Salary is identical, equity is not. Thank you. This is the question I was hoping to see an answer for.

More important than just getting answer, do you understand _why_ every employee isn't granted the same amount equity?

Isn’t it obvious? This is where they vary compensation for the same reasons everyone else varies compensation.

If they gave everyone the same equity compensation presumably they’d put that front and center like they do for the base salary.

The claims about paying everyone the same are a red herring because it’s only about base salary.

Re: Our $100M Series B

#398
post #305

I am wondering what they have on Roadmap and if Zen 6 will come. Their AMD EPYC™ 7713P is 4+ years old already. Or is Hardware performance not a main focus for Oxide but Software that came with it? In 2027 - 2030, We will have 256 Core Zen 7 CPU with PCIe 6.0 or 7.0 SSD and Network. If Liquid Cooling ever come to Oxide we are looking at 5 - 10x the compute power of its current hardware. Somewhere along the line a Sin…

at any rate, I'm looking forward to decommissioned Oxide racks making it into my homelab for pennies on the dollar

Re: Our $100M Series B

#399
post #242

Earlier quoted context omitted.

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 ta…

> 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. I agree, but that number for most people is not the $207k/yr Oxide is paying. For most people that number is likely north of $500k, if not single digit millions.

That heavily depends on where you live and your life situation (young kids? older kids? No kids?).

Re: Our $100M Series B

#400

Earlier quoted context omitted.

I applied in early 2021. Getting rejected from any company carries a sting, but I was grateful to have gone through the process. I didn’t realize at the time, but Oxide’s application process was the best form of interview prep I’ve done. The process forced me to thoroughly document my values and career accomplishments. In later non-Oxide interviews, I effectively recited what I had written my materials. In that way,…

Loved reading your experience here. Thank you for posting it. I've written about the value of an artifact in the past when people pushed back against the Oxide materials saying they are a lot of work for no guarantee. When I first applied to Oxide I was also rejected and the materials process taught me a ton about myself and changed the way I viewed job searching and my work. I shifted course and increased my skills…

> they are a lot of work for no guarantee.

Well, its the assymetry of wanting a 10 year long documented CV with various orthogonal points in your career, versus actually having a 30 minute call.

Unlike an actual interview, which is equal time investment, this 20 page paper gets the commentary and result of "no". "No" what? You can ask an interviewer about concerns, and discussion points. This email from no-mail@ is just nothing.

And its not the sting of rejection. I've been turned down, and I too have turned down. But its the mechanistic, dispassionate, legalistic response after months of a "No". And not even a 'What we're looking for is.... '

Post reply on HN