AeroFS, YC Founder Story

Company: AeroFS (later rebranded Amium; acquired by Redbooth) Founders: Yuri Sagalov (CEO) & Weihan Wang (CTO) YC Batch: Summer 2010 (S10) Industry: Enterprise SaaS / Private Cloud / File Sync Founded: 2010 | Public Launch: April 2013 (stealth for 3.5 years) Total Funding: $15.52 Million Exit: Acquired by Redbooth, September 2017 Notable: Paul Graham called AeroFS "one of the most important companies from any of YC's batches"

The One-Line Summary

A Russian-born, Canadian-raised grad student who had immigrated twice and rebuilt twice, left a Masters degree mid-program to turn a distributed systems research project into the "Dropbox that lives behind your own firewall", earning Paul Graham's highest praise and the trust of Fortune 500 security teams who couldn't store a single byte outside their own servers.

Lens 1, The Before State

Who Was Yuri Sagalov Before YC?

Yuri Sagalov's life before AeroFS was defined by one recurring theme: building from nothing in a new place.

He was born in Russia. As a child, his family emigrated to Israel. Then, as a teenager, they emigrated again, this time to Canada. Three countries. Three fresh starts. Each time, the family operated from the same belief: "you have to make it yourself because you can't expect anyone to give you anything." That conviction wasn't a motivational poster on a wall. It was lived, repeated, tested.

In Canada, Yuri enrolled in the University of Toronto's Engineering Science program, one of the most demanding undergraduate engineering degrees in the country. He majored in Computer Engineering and graduated before enrolling in a Masters of Applied Science program, focusing specifically on distributed systems, the academic discipline of making multiple computers work together as if they were one. This was not a casual interest. It was the technical foundation that would directly become AeroFS.

His co-founder, Weihan Wang, was a fellow student and classmate, they developed the core technology together in graduate school, long before they ever thought of it as a company.

The Personal Pain They Were Living

The frustration that became AeroFS didn't come from a consumer experience, it came from inside a research lab. Yuri and Weihan were working with sensitive data, large files, and distributed machines across a university network. They needed files to sync between computers. The options available were: use Dropbox (and send your research data to a third-party American server), use a clunky university FTP system, or do nothing.

None of those answers were acceptable for anyone working with genuinely sensitive or large-scale data. Yuri looked at Dropbox and asked a simple question: "Why does all the syncing have to go through someone else's server? What if the files just went directly between the computers that need them?"

That question, in 2009, years before data privacy became a mainstream conversation, became the entire company.

Why They Almost Didn't Think of It as a Company

Yuri was deep inside a graduate program. He was on the academic track, thesis, publications, maybe a PhD. The jump from "interesting distributed systems research" to "company that enterprises will pay for" was not obvious, especially for someone in a university engineering program in Canada, far from Silicon Valley's gravitational pull.

What pushed him was the combination of two things: the technology actually worked during development, and Weihan was equally convinced. When two engineers who built something together both believe it solves a real problem, the activation energy for "let's apply to YC" drops dramatically.

Key Insight for Aspiring Founders

Your academic research can be your unfair advantage. Yuri didn't pivot from research into startups, he took his research directly into a company. If you're studying something deeply technical at a university level, the gap between "thesis project" and "product" may be much smaller than you think. The technical moat you're building in school is real.

Lens 2, The Idea Origin

How the Idea Was Actually Born

The idea started inside the University of Toronto's computer engineering department. Yuri and Weihan were studying distributed systems, specifically, how to make multiple machines synchronise state with each other reliably and efficiently. This is deeply complex computer science. But at its core, what they were building was something deceptively simple to describe: files that sync between computers without going through a central server.

Dropbox had launched in 2008 and was growing fast. Everyone could see it was solving a real problem. But Yuri saw the exact flaw that Dropbox was ignoring: its architecture required your files to live on Dropbox's servers, even temporarily, before syncing to your other devices. For most consumer users, this was fine. For healthcare companies, law firms, financial institutions, government contractors, movie studios, and anyone dealing with regulated or sensitive data, it was disqualifying. They simply could not use Dropbox, legally or ethically.

The insight was not "let's copy Dropbox." The insight was: "Dropbox's architecture is a dealbreaker for an entire category of users who have no good alternative."

The First Version, Pure Research Meets Real World

The first version of what became AeroFS was built as a graduate research project, a peer-to-peer file synchronisation system that moved data directly between devices without touching any central server. Files travelled machine-to-machine, encrypted in transit, never touching AeroFS's infrastructure.

The product's original positioning was almost purely technical: it appealed to developers and IT administrators who understood what "behind the firewall" meant. The consumer-friendly language, "it's like Dropbox, but it runs inside your firewall", came later, once they started talking to non-engineers.

When Yuri applied to YC, he was leaving a graduate degree program mid-stream. That's not a small thing. In academic culture, walking away from a Masters is treated as failure. Yuri treated it as prioritisation.

The Signal That It Was Working

The signal came from the type of customers who started finding them, without any marketing. A financial services firm in New York signed up for 1,000 seats. Companies in Germany reached out because they legally could not store data on American servers. Healthcare providers, law firms, and movie studios started asking how quickly they could deploy.

Yuri's observation was sharp: "I assume customers are proactively searching for what AeroFS does." The Snowden revelations in 2013, which exposed the NSA's mass surveillance of data stored on American cloud servers, sent a wave of enterprise customers specifically looking for AeroFS-style solutions. The problem had been real all along. The broader public just hadn't been paying attention.

The Pattern This Follows

AeroFS fits a specific YC archetype: the "infrastructure gap" play, finding a product that has massive consumer traction (Dropbox) and identifying the large, underserved enterprise segment that the consumer product structurally cannot serve. This pattern has produced enormous companies. The key insight is that consumer and enterprise often need the same outcome through completely different architectures. Spotting that architectural gap is the idea.

Lens 3, The Application Anatomy

What Made Their Application Work

AeroFS applied to YC Summer 2010 with three genuine advantages that most applicants don't have simultaneously:

1. The technical depth was real. Yuri and Weihan weren't proposing to build distributed file sync, they had already built it during their graduate research. YC partners could look at working technology, not a pitch deck.

2. The market they were targeting was ignored by everyone. Dropbox was winning consumers. Nobody was winning enterprises that couldn't use Dropbox. The white space was specific and defensible.

3. The one-liner landed with zero ambiguity. "Dropbox, but it runs inside your firewall." Every technical person in the room immediately understood the problem, the solution, and why it mattered. Comparison pitches work when the comparison is universally understood and the differentiation is unmistakable.