pipe
The business, the turning points, and the decisions behind them.
01 / WHAT IT BUILT
What the company did
Pipe was a Berlin-based file-sharing startup whose founding team came from Gracenote and Songbeat. It built a Facebook app for drag-and-drop file transfer — send files of up to 1GB to any Facebook contact, running over WebRTC between Firefox and Chrome, one of the first apps to do so. Released from beta in June 2013, it was music in its DNA; but as one industry report put it, Pipe wasn't a stayer, and the app stopped working soon after.
02 / pipe FAILURE REASONS
Failure factors supported by the current evidence
The evidence on why Pipe shut down is thin: no postmortem was ever published. What the record shows is a Facebook-platform app whose core feature — sending up to 1GB files to friends — spooked rightsholders, as contemporary coverage noted, in a music industry already fighting piracy. Requiring both sender and receiver to run Pipe at the same time made every transfer a coordination problem, and building on Facebook's platform meant living on borrowed distribution. The app, in beta for almost a year before its June 2013 release, stopped working within about a year.
03 / EVENT HISTORY
Events in the structured record
- Product launch
Pipe leaves beta in June 2013 as the first Facebook file-sharing app, transferring files up to 1GB over WebRTC.
- Operations ended
Pipe stops working; the startup ceases activity with no public shutdown statement.
04 / CONTEMPORARY REBUILD ASSESSMENT
Difficulty of rebuilding this project today
Material for this section is being gathered and checked. It will appear here once ready.
Overall assessment: Not completed
05 / CAUSAL CHAIN
How the factors connect
- 01
Requiring both sides to run your app turns every transfer into a coordination failure
- 02
Spooking rightsholders with 1GB music transfers is a legal bill you cannot afford
- 03
Building on Facebook's platform is building on borrowed distribution
- 04
Almost a year in beta burns the launch window: ship or die