Breaking
MLPERF Quobyte claims fastest published 3D U-Net storage result 24 H100 GPUs per client on 4 servers ZOOX robotaxi AI training scales 2 PB → 30 PB on Quobyte STFC UK JASMIN supercomputer runs a single 90 PB Quobyte cluster, 1.5bn+ files V4 adds ARM support, cloud object tiering & end-to-end observability SIEMENS HEALTHINEERS 60+ FDA-approved AI models on Quobyte storage MLPERF Quobyte claims fastest published 3D U-Net storage result 24 H100 GPUs per client on 4 servers ZOOX robotaxi AI training scales 2 PB → 30 PB on Quobyte STFC UK JASMIN supercomputer runs a single 90 PB Quobyte cluster, 1.5bn+ files V4 adds ARM support, cloud object tiering & end-to-end observability SIEMENS HEALTHINEERS 60+ FDA-approved AI models on Quobyte storage
Company Dossier — No. 001 Santa Clara · Berlin Filed 2026
Quobyte logo
Software-Defined Storage

Quobyte.

“Storage Architected for AI.”

2013
Founded
~22
People
90 PB
Largest cluster
File / Block / Object
One system

The green Q, sitting on a field of highlighter green. Two engineers who once kept Google's storage humming decided the trick was never the hardware. It was the software - and they went home to write it down.

Share this dossier LinkedIn X Facebook Instagram
01

The Feature

A storage company that mostly refuses to sell you storage

Here is a business model that sounds slightly insane if you say it out loud: sell enterprises a storage product, but do not sell them any storage. No disks, no flash, no shiny rack-mounted appliance with a bezel and a support contract. Just software. You already own the servers - the boring x86 or ARM boxes humming in your data center - and Quobyte's pitch is that those boxes were the storage system all along. You just needed the right software to tell them so.

Quobyte was founded in 2013 by Björn Kolbeck and Felix Hupfeld, two engineers with a specific and useful kind of resume. Before Quobyte they spent more than seven years at the Zuse Institute Berlin building an open-source parallel file system called XtreemFS - the sort of deeply unglamorous distributed-systems work that most people never think about until the moment it fails. Then they both went to Google, where Hupfeld worked in the infrastructure team as a tech lead and capacity planner, and Kolbeck led engineering on the hotel-finder project. And at Google they noticed something that would become the entire thesis of the company: very small teams were operating truly enormous amounts of storage, and they were doing it without heroics.

The Google insight, stripped of jargon, is this. Everyone else in the enterprise storage industry solved reliability by buying more special hardware - redundant controllers, proprietary arrays, exotic interconnects, the works. Hyperscalers solved it in software. They assumed the cheap hardware would fail, constantly and rudely, and they wrote software resilient enough that nobody had to care. Kolbeck and Hupfeld's bet was that this approach didn't have to stay locked inside Google. So they left, took the lessons (though not the code - they rewrote XtreemFS from scratch for the enterprise), and built Quobyte.

Small teams at Google managed vast storage with almost embarrassing efficiency. Quobyte's whole premise is that this was never a Google secret - it was a software problem, and software travels. — The founding thesis

What they built is called the Quobyte Data Center File System, and the word “file system” undersells it. It presents as file storage, block storage, and object storage all at once, from one unified system, which is unusual because in most shops those are three separate products run by three separate sets of grumpy people. Quobyte collapses them into a single flat layer that can span thousands of servers and scale, the company says, roughly linearly - add hardware, get proportionally more capacity and performance, without the architecture folding in on itself.

The economic trick underneath is tiering. Flash is fast and expensive; spinning disk is slow and cheap; and Quobyte runs both in the same cluster, using policy-based automatic placement to decide what lives where. The marketing shorthand is “NVMe Speed, HDD Cost,” which is the kind of phrase that would be annoying if it weren't describing a genuinely real tradeoff that storage buyers spend their whole careers negotiating. You want your hot data on flash and your cold data on disk, and you'd prefer not to think about which is which. Quobyte's answer is: don't. Let the policy engine move it.

Then there is the resiliency, which is the part the founders clearly care about most, because it's the part they spent a decade studying. When a drive dies, or a whole server dies, or several things die at once - and in a large enough cluster something is always dying - Quobyte's software reroutes and self-heals and keeps serving data. No exotic hardware required. This is the hyperscaler philosophy imported wholesale: failure isn't an emergency, it's the default operating condition, and the system is designed around that assumption rather than in spite of it.

For a long time this was a respectable but somewhat niche pitch - good for HPC centers, hosting providers, life-sciences labs doing cryo-EM microscopy or radar imaging, the kind of customers who move data by the petabyte and read storage benchmarks for pleasure. Then AI happened, and Quobyte's niche turned out to be sitting directly in the path of the single hottest infrastructure problem of the decade.

Because the dirty secret of AI training is that the bottleneck often isn't the GPUs. It's feeding them. A rack of NVIDIA H100s or Grace Blackwell nodes is a gloriously expensive thing to leave idle, and it goes idle the instant the storage layer can't shovel training data fast enough. Quobyte's response was to move the storage onto the GPU nodes themselves - “GPU-converged storage,” running the software on the same machines doing the training, shortening the path between data and model. In 2025 the company shipped v4, adding ARM support, cloud object tiering, and end-to-end observability, and re-badged the whole thing around a new tagline: Storage Architected for AI.

Then it did the thing that separates storage vendors who talk from storage vendors who publish: it put numbers on the board. Quobyte released results for MLPerf Storage, an industry benchmark specifically engineered to torture storage systems by simulating AI training loads. On the brutal 3D U-Net test, the company reported driving 24 H100 GPUs from a single client machine using just four standard servers - a result it says is about a third faster than the next-best published figure, at lower cost and energy per unit of performance. The results carry the usual “unverified” asterisk that accompanies self-published benchmarks, which is worth noting. But publishing at all, on a benchmark others can run, is a meaningfully braver posture than the slide-deck superlatives that dominate this industry.

The customer list is the other evidence. Siemens Healthineers runs more than 60 FDA-approved AI models across upwards of a billion datasets on Quobyte. The UK's STFC operates a single 90-petabyte Quobyte cluster holding more than 1.5 billion files on its JASMIN supercomputer. The robotaxi company Zoox stores its vehicle-sensor and simulation data on Quobyte, scaling from 2 to 30 petabytes as its self-driving models got hungrier. Yahoo Japan, UC Davis, HudsonAlpha, and OHSU round out a roster that skews heavily toward organizations for whom storage failure is not an inconvenience but a genuine problem.

And here is the detail that amuses and informs in equal measure: Quobyte does all of this with roughly 22 people. A company you could fit in a large conference room operates storage clusters measured in tens of petabytes for national supercomputers. That ratio is either a testament to the software or an indictment of everyone else's, and Quobyte would happily tell you it's both. It is, in the founders' framing, the entire point - if your storage requires an army to babysit, the storage is the problem, not the staffing.

It is worth sitting with the word Quobyte keeps returning to, which is “simplicity.” The company calls one of its design goals “unconditional simplicity,” and describes deployment in terms usually reserved for consumer gadgets - production in minutes, smartphone-easy. This is a slightly subversive thing for an enterprise-storage vendor to emphasize, because complexity has historically been how storage vendors make money. The more moving parts, the more professional services, the more lock-in, the more the customer needs to keep paying you to understand their own system. Quobyte's flat, single-layer architecture is a bet in the opposite direction: that the thing customers actually want is fewer things to think about, and that a vendor willing to remove complexity rather than sell it will, eventually, win the customers who have been burned by everyone else.

The philosophy shows up in the mundane operational details, which are the details that actually matter at three in the morning. Configuration and operations are decoupled from the hardware, so you can swap out a dead server without re-architecting anything. Redundancy is expressed as software policy rather than as a wiring diagram. There is multi-tenancy, end-to-end data protection, and multi-cluster support - all the enterprise-checklist features - but the pitch is that they arrive without the enterprise-checklist misery. A team of roughly two dozen people cannot afford to run a product that requires constant hand-holding, so the product is built not to require it. The constraint and the philosophy are, conveniently, the same thing.

None of this makes Quobyte a household name. It competes in a crowded, technical field against well-funded rivals like WEKA, VAST Data, DDN, and the open-source Ceph, and against incumbents like NetApp, Pure Storage, and Dell. It raised a Series A from Target Partners and High-Tech Gründerfonds in 2014 and a Series B around 2016 that pulled in the Samsung Catalyst Fund and ALSTIN Capital, and it has stayed deliberately lean since. But there's something clarifying about a company whose pitch is legible in one sentence - run your storage as software on the hardware you already own, and stop buying boxes - and that has spent thirteen years quietly proving the sentence is true. In an industry that loves to complicate things, refusing to sell you a box turns out to be a pretty good story.

Figures above are drawn from Quobyte's own materials and public reporting; benchmark results are self-published and, per MLCommons convention, marked unverified. Revenue and valuation figures are third-party estimates.

90 PB
Largest single cluster (STFC JASMIN)
1.5B+
Files in one cluster
60+
FDA-approved AI models (Siemens Healthineers)
2→30 PB
Zoox AI training scale-up
02

The Founders

Björn Kolbeck

Co-Founder & CEO

Former Google tech lead on the hotel-finder project (2011-2013) and lead developer of the open-source XtreemFS. His PhD focused on fault-tolerant replication - the exact problem Quobyte solves in software.

Felix Hupfeld

Co-Founder & CTO

Former Google infrastructure tech lead and capacity planner (2009-2013), and architect of XtreemFS. PhD in distributed storage. The engineer who watched small teams run vast storage and decided to bottle it.

ex-GoogleXtreemFSZuse Institute Berlindistributed systemsfault tolerance
03

What You Can Build With It

2016

Data Center File System

Turns commodity x86/ARM servers into one unified system serving file, block, and object storage with linear scale, fault tolerance, and self-healing.

2020

Hybrid NVMe + HDD

Flash and disk in a single cluster with policy-based automatic placement and cloud tiering. “NVMe Speed, HDD Cost.”

2025

GPU-Converged Storage

Runs directly on GPU nodes, including NVIDIA Grace Blackwell and Hopper, shortening the data path to keep expensive accelerators fed.

2025

Quobyte v4

Adds cloud object storage, ARM support, and end-to-end observability - a release built explicitly around AI training.

Deploy anywhere - data center, cloud, or edge - across AI, HPC, financial services, life sciences, and Kubernetes environments. One system to run, not three.

04

Timeline

2006

XtreemFS begins

The founders-to-be architect the open-source XtreemFS parallel file system at the Zuse Institute Berlin.

2009

The Google years

Hupfeld and Kolbeck join Google and learn how small teams operate storage at massive scale.

2013

Quobyte founded

They leave Google to rewrite XtreemFS as enterprise-grade storage software.

2014

Series A

Target Partners and High-Tech Gründerfonds provide multimillion-euro financing.

2016

Series B & launch

Backed by the Samsung Catalyst Fund and ALSTIN Capital, Quobyte ships its Data Center File System.

2020

HPC & ML push

Quobyte expands into HPC and machine-learning workloads with hybrid unified storage.

2025

Storage Architected for AI

Ships v4, launches GPU-converged storage, and publishes MLPerf Storage results.

05

Funding

Series A
Target Partners · High-Tech Gründerfonds
Sep 2014 · multimillion €
Series B
ALSTIN Capital · Samsung Catalyst Fund · Target Partners · High-Tech Gründerfonds
c. 2016 · undisclosed

Estimated revenue ~$8M/yr and valuation ~$8.9M per third-party sources (GetLatka). Quobyte does not publicly disclose full financials.

06

Watch & Explore

Product demos, technical talks, and the company's own channel:

07

FAQ

What does Quobyte do?

Quobyte makes software-defined storage that turns commodity x86 or ARM servers into a single unified system offering file, block, and object storage - aimed at AI, HPC, and enterprise workloads.

Who founded Quobyte and when?

It was founded in 2013 by Björn Kolbeck (CEO) and Felix Hupfeld (CTO), two former Google engineers who previously created the open-source XtreemFS parallel file system.

Who uses Quobyte?

Customers include Siemens Healthineers, robotaxi maker Zoox, the UK's STFC/JASMIN supercomputer, Yahoo Japan, UC Davis, HudsonAlpha, and OHSU, among others.

How is Quobyte different from traditional storage?

Instead of selling a hardware appliance, Quobyte is downloadable software that runs on hardware you already own, delivers fault tolerance and self-healing in software, and scales linearly across thousands of servers.

Has Quobyte raised funding?

Yes - a multimillion-euro Series A in 2014 (Target Partners, High-Tech Gründerfonds) and a Series B around 2016 with investors including the Samsung Catalyst Fund and ALSTIN Capital.

08

Links & Sources

software-defined storageai storagehpcparallel file systemkubernetesobject storagenvmecommodity hardwareself-healingmlperf

Sources: quobyte.com · Crunchbase · Blocks & Files · StorageNewsletter · MLCommons · Target Partners · Tracxn. Some figures are approximate or self-reported.