AeroFS
Summer 2010AcquiredSecure Enterprise Collaboration.
Pressure-test this opportunity
Explore the risks and possibilities with a prompt for ChatGPT, Claude, or your agent.
Secure Enterprise Collaboration.
Explore the risks and possibilities with a prompt for ChatGPT, Claude, or your agent.
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.
Enterprise file sharing was a large category, but AeroFS's strict private-custody segment was narrower. Customers needed both a compliance constraint and enough distributed collaboration pain to justify deployment. The Amium pivot pursued a broader collaboration market at the cost of entering a more crowded field.
AeroFS competed with Dropbox, Box, Microsoft file services, private-cloud storage, network drives, and managed transfer products. Its custody model was a meaningful technical distinction. Over time, larger vendors improved encryption, administrative policy, audit logs, hybrid deployment, and compliance programs.
Amium then faced Slack, Microsoft Teams, Box, Dropbox Paper, and numerous project-management systems. Redbooth already offered tasks and project coordination, which made the merger complementary while showing how much product surface a unified collaboration suite required.
AeroFS sold enterprise seats and deployment software. Larger customers brought contract value, though sales, security review, installation, support, and desktop compatibility increased the cost of each account. A free allowance for small teams could seed evaluation but did not remove enterprise procurement.
Amium adopted a cloud subscription model aimed at self-service teams. That changed the acquisition engine from identifiable information-technology buyers to a wide online audience. It also made user behavior observable, creating a new need for product analytics, engagement work, and higher-volume support.
AeroFS solved a sharp security problem but operated between two expanding platform categories. Cloud file vendors added enterprise governance. Infrastructure vendors offered private and hybrid storage. Collaboration suites absorbed files into chat, tasks, and documents. A specialized sync layer risked becoming a component rather than the system employees opened each day.
The Amium pivot acknowledged that pressure. It sought a daily collaboration surface, but it also exchanged a differentiated custody model for a crowded cloud market and an unfamiliar sales motion. AeroFS had to change product, customer, hosting, analytics, and go-to-market at once.
The Redbooth merger combined Amium's file-centered collaboration with an established task and project product. This was not a simple acquisition: the combined company kept Redbooth's name while AeroFS's chief executive took leadership. Terms and ownership were undisclosed. Amium's shutdown three months later confirms that the standalone product did not continue.
The original AeroFS brand and developer program also ended. Technology may have informed the combined product, but customers could no longer buy the independent proposition. The outcome suggests that private file sync was valuable, yet too narrow against suites with stronger distribution and broader daily use.