The social media graveyard: private networks that died, and why

quick answer

Path, Peach, Ello, App.net, Google+, Friendster, Cocoon: the private network graveyard is well populated, and the causes rhyme. Almost none died of a bad idea or bad design. They died structurally, no business model, venture funding demanding impossible growth, or too few users to matter. [Path's story](/what-happened-to-path) is the clearest headstone, and the most instructive.

Every few years, someone launches a social network that promises to be different: smaller, kinder, private, ad-free, the antidote to whatever Facebook has most recently become. There is a burst of enthusiasm, a wave of hopeful sign-ups, a flurry of press. And then, usually, silence, and a year or two later, a shutdown notice.

This is the graveyard. It is worth walking through, partly because the stories are genuinely interesting, and partly because the pattern they form is the single most useful thing to understand about this category. The headstones do not say “bad idea”. They mostly say “no way to pay for the idea”.

I build in this category, so I have read these obituaries more carefully than most, looking for the thing that keeps killing good products. Here is what I found.

The graveyard

Friendster (2002 to the 2010s). One of the very first social networks, and for a moment the biggest. It buckled under technical problems and was overtaken by MySpace and then Facebook, eventually pivoting to gaming before disappearing. Cause of death: outcompeted, and unable to scale technically when it mattered.

Path (2010 to 2018). The beautiful private network with a hard friend limit, beloved and influential. It refused advertising but never built a working model, sold to Daum Kakao in 2015, and shut in 2018. Cause of death: no business model; the founding limit loosened under pressure until the idea dissolved. The full story is in what happened to Path.

Google+ (2011 to 2019). Google’s enormous, well-funded attempt at a social network, with its clever Circles feature for sharing with specific groups. It never won real engagement, was dogged by a real-names controversy, and was shut after data-exposure bugs. Cause of death: built by committee, never loved, no genuine reason to exist beyond competing with Facebook.

App.net (2012 to 2017). The most interesting failure for our purposes: a paid, ad-free social network and developer platform, funded by user subscriptions rather than advertising. It had the right instinct about who should pay, and it still died, because it never reached the scale of users that a network needs to be useful. Cause of death: right model, too small a network.

Ello (2014 onward). The “anti-Facebook”, launched with a manifesto against ads and data harvesting, briefly flooded with sign-ups during a Facebook backlash. It pivoted towards artists and creators and faded into dormancy. Cause of death: a manifesto is not a product; the hype arrived before the reasons to stay did.

Peach (2016). A charming, quirky app from a Vine co-founder, with playful “magic word” commands. It went viral for a few weeks among tech early-adopters and emptied out almost as fast. Cause of death: novelty without depth; fun to try, no reason to return.

Vero (2015 onward). Promised a subscription model and a chronological, algorithm-free feed, then kept extending “free for life” rather than charging, which meant the model that was supposed to fund it never switched on. It technically still operates. Cause of death: a business model announced but never enforced.

Cocoon (2019 to the early 2020s). A small, private app for close groups, built by former Facebook people, quietly shut down. Cause of death: never reached enough users to matter, in a market where the incumbents owned the network.

The pattern under the headstones

Read those causes of death together and they sort into a small number of structural failures.

No business model at all. Path, Ello, Peach. Ad-free as an instinct, with nothing put in its place, so the running costs and the investors’ expectations eventually forced compromise or closure.

The wrong business model, demanded by funding. Networks that took large venture investment needed enormous growth to justify it, which pushed them towards the very engagement tactics they were founded to avoid, hollowing out the original promise.

The cold-start problem. App.net and Cocoon had reasonable models or reasonable ideas, but a social network is useless without the people, and they never got enough of them. A private network has this problem acutely: you cannot enjoy it alone.

Novelty without depth. Peach, and arguably Ello, were fun to try and offered no reason to stay, so the viral wave receded and took the userbase with it.

Notice what is almost never the cause: a bad idea, or bad design. Path was gorgeously designed. App.net had the funding model broadly right. These were not stupid products. They were structurally underpowered for the thing they were trying to do.

What the graveyard teaches a new network

Three lessons, learned from other people’s headstones.

First, the business model is not a thing to defer; it is the foundation, and “we’ll figure out revenue later” is written on half these graves. Second, the model has to be one that does not require betraying the product, which in practice means being paid by the users rather than by advertisers, so that growth and engagement stop being existential. Third, you have to solve the cold-start problem honestly, by getting whole circles of people in together rather than hoping individuals trickle in, because a private network is only ever as good as the people already in it.

Where 142 stands

142 is built directly against these failures. It is subscription-funded from day one, £3.99 a month or £29.99 a year, with no free tier, because the most common cause of death in this graveyard is the absence of a model. Its cap of 142 connections is hard and cannot be sold up, because the second most common cause is a founding principle loosened under commercial pressure, exactly what happened to Path. And it is designed to be adopted by circles of friends together, because the third is the cold-start problem, which kills private networks fastest of all. None of this guarantees survival. It just means we have read the headstones. The fuller argument is in our guide to private social networks.

Summary

The social media graveyard is full of good ideas that died of structural causes: Path, Peach, Ello, App.net, Google+, Friendster, Cocoon and more. Walk the headstones and the pattern is clear. The killers are an absent business model, a venture model that demands self-defeating growth, the cold-start problem of too few users, and novelty with no depth, almost never a bad idea or poor design. A new private network’s job is to learn from the dead: build a real model that does not require betraying the product, hold the founding principles against commercial pressure, and gather whole circles rather than stray individuals. The graves are a warning, and a fairly precise one.

frequently asked questions

Why do private social networks keep failing?

Usually for structural rather than creative reasons: no business model, a venture-funded model that demands growth they cannot reach, or the cold-start problem of never gathering enough users to be useful. The ideas and designs are often good; the economics underneath them are not.

What was the most successful failed social network?

By love and influence, Path: beautifully designed, genuinely beloved, and the originator of the hard friend limit, yet ultimately unable to fund itself. Google+ was the best-funded failure, and App.net the most instructive, because it had the paid model broadly right and still could not reach scale.

Did any private network use a subscription model?

Yes. App.net charged users directly and was ad-free, which was the right instinct about who should pay; it failed on scale, not on principle. Vero promised subscriptions but kept extending free access, so its model never actually switched on. The lesson is that the model has to be real and enforced.

What is the cold-start problem?

It is the difficulty a new network faces in being useful before it has users, since the value comes from the people on it. It is especially acute for private networks, which you cannot enjoy alone, and it is why getting whole friend groups to join together matters more than attracting scattered individuals.

Will 142 end up in the graveyard too?

There are no guarantees in this category. What 142 has done is build against the most common causes of death: a real subscription model rather than no model, a hard unsellable cap rather than a principle that erodes, and a circle-based approach to the cold-start problem. Reading the headstones is not immunity, but it beats ignoring them.

What happens to my data when a social network shuts down?

Usually you get a short window to export it before the servers go dark, after which it is gone, as Path's 2018 closure showed. It is a strong argument for choosing services that build proper data export in from the start, which European data law obliges 142 to do.

142 is social media for your real friends.
join the waitlist
© 2026 142 Social Limited