
Secure Enterprise Collaboration.
Turn this teardown into a decision-ready prompt for ChatGPT, Claude, or your agent.
If you only have a few minutes to spare, here’s what investors, operators, and founders should know about AeroFS (S10).
AeroFS offered file synchronization without storing customer files on the vendor's servers. Its desktop clients moved data among infrastructure controlled by the customer, giving regulated and security-sensitive organizations a Dropbox-like workflow behind their own boundaries.
The company raised about $15.52 million and won enterprise customers, then moved beyond private file sync. In 2016 it launched Amium, a cloud collaboration product organized around files and conversations. That pivot changed both the hosting model and the buyer. A year later AeroFS merged with project-management company Redbooth. The combined business used the Redbooth name, AeroFS founder Yuri Sagalov became chief executive, and Amium shut down in December 2017.
The merger ended AeroFS as an independent company. Its original insight remains sound: storage location and access control can be product requirements rather than back-office settings. The harder question was whether a private sync engine could support a large standalone business once Dropbox, Box, Microsoft, and other suite vendors added enterprise controls.
Yuri Sagalov and Weihan Wang developed the technical basis for AeroFS through graduate work in distributed systems. They founded the company in 2010 and joined Y Combinator's Summer batch.
The early pitch was unusually clear: a Dropbox-like folder that ran inside the customer's firewall. Files transferred directly among approved computers instead of passing through storage operated by AeroFS. Windows, Mac, and Linux clients made the system feel familiar to end users while information-technology teams retained custody.
AeroFS stayed in stealth for about three and a half years. By its public emergence in 2013 it had raised $5.5 million and said a financial-services firm had signed a 1,000-seat contract with almost no marketing. The quiet approach matched the buyer: large enterprises needed technical review, security validation, and deployment work before adopting a new file system.
The original AeroFS product synchronized selected folders across customer-controlled devices and servers. Because AeroFS did not hold the file contents, enterprises could apply their own security, retention, and compliance controls. Desktop clients hid much of the distributed-system complexity from employees.
The product sat between consumer convenience and enterprise custody. Administrators wanted control over where data lived, while users wanted a folder that updated automatically. AeroFS made those requirements coexist without requiring every employee to operate a virtual private network or manually copy files.
Amium broadened the scope. It connected files with conversations, version history, and collaboration across organizational boundaries. The move also reversed part of the original premise: Amium was cloud-based and sold to work teams rather than solely to technical buyers. AeroFS had to learn online acquisition and product analytics after years of enterprise sales.
The first target was an organization unable or unwilling to store sensitive files with a third-party cloud provider. Financial services, healthcare, professional services, media, telecommunications, and automotive companies fit that profile. Amium targeted a wider group of teams that wanted messages, files, and work context together.
Read the complete post-mortem, the rebuild playbook, and the exact reasons AeroFS is still worth studying now.