Editor’s note: This article was originally published in 2007 as a review of Vox, the blogging platform built by Six Apart. Vox shut down in 2010. This updated version looks at what Vox was trying to build and why it didn’t work.
In 2007, Vox looked like it might finally be the thing that unified two worlds bloggers were trying to navigate simultaneously: the personal publishing platform and the social network. Six Apart — the company behind Movable Type and TypePad, and briefly the owner of LiveJournal — had spent years closer to the infrastructure of blogging than almost anyone else. Vox was their attempt to distill that knowledge into something friendlier, more social, and more private than anything else on the market.
It was a genuinely interesting product. And it failed within three years.
Understanding why Vox failed, and what it was actually trying to do, matters more now than it did at the time. Because the problems it set out to solve — how do you combine easy publishing with meaningful community? how do you give people real privacy controls without killing discoverability? how do you make blogging feel as effortless as social media? — are the same problems that every major publishing platform is still grappling with in 2026.
What Vox was actually building
To understand Vox, you have to understand the specific problem Six Apart founder Mena Trott was trying to solve when she announced the platform at the DEMO conference in late 2005 under the codename “Project Comet.” The premise was that blogs, as they existed, were optimized for broadcasting to strangers. They were public by default, open to comment from anyone, and demanded a certain kind of performed confidence from their authors. That worked well for professional bloggers and journalists. It worked less well for the person who wanted to share photos of their kids with twelve people they actually knew.
Vox was designed to close that gap. The mechanics were more sophisticated than they first appeared. Content on Vox could be published at four levels: to everyone, to your “neighborhood” (people you’d connected with on the platform), to your friends, or just to yourself. Posts could mix media from multiple external services — YouTube, Flickr, Photobucket, Amazon — in ways that felt genuinely integrated rather than bolted on. The question-of-the-day feature gave reluctant new bloggers a prompt to write against. The entire UI was built around reducing the friction between having something to say and actually saying it.
These were real innovations in 2006. The granular privacy controls in particular were ahead of what Facebook was offering at the time, and they addressed a genuine concern that had kept many people away from blogging entirely: the fear that everything they wrote would be public and permanent. Vox offered a way to write for your people without writing for everyone.
Why the mechanics weren’t enough
The problem wasn’t the feature set. It was the timing, and a fundamental tension in the product’s design that Six Apart never fully resolved.
Vox launched in October 2006. Facebook opened its registration to the general public in September of the same year. The two products were aimed at overlapping audiences — people who wanted to share personal content with a defined circle — but Facebook’s approach to that problem was radically lower friction. You didn’t need to write a post. You could upload a photo, post a status update, tag a friend. The cognitive load of maintaining a Vox blog, even a simple one, was categorically higher than the cognitive load of posting on Facebook. And because Facebook was already where many people’s actual social graphs lived, convincing someone to rebuild that network on Vox was a significant ask.
The deeper problem was what might be called the audience collapse. A platform that helps you share privately with people you care about only works if the people you care about are on it. Vox’s neighborhood and friends features were genuinely useful once you had a network there. Building that network in the first place was the hard part, and Six Apart never cracked it. The result was a product that was excellent in theory and often sparse in practice.
By 2008, Six Apart’s development resources had shifted almost entirely to a relaunched TypePad. Vox’s spam management deteriorated. The product that had been designed for intimacy started to feel abandoned. When the shutdown announcement came in September 2010, most active users had already drifted away. The migration options were poor — URL redirects went to homepage rather than individual posts, stripping years of search value from writers who’d built an audience there.
The same ambitions, better executed
What Vox was trying to build didn’t die with the platform. It just took a decade and a different set of founders to figure out the right architecture for it.
Substack, which launched in 2017 and has grown into the dominant independent publishing platform of the current era, solves the distribution problem that killed Vox by routing around it entirely. Rather than asking writers to rebuild their social graph inside a new platform, Substack delivers content directly to email inboxes. Your readers don’t need to be Substack users. They need an email address. That single architectural decision — email as the delivery layer, not a proprietary social graph — eliminated the cold-start problem that made Vox so difficult to populate.
The social layer came later, and more carefully. Substack Notes, launched in 2023, functions as a discovery feed inside the platform. Unlike Vox’s neighborhood system, which required bilateral connections, Notes is designed primarily for discovery rather than intimacy. The algorithm prioritizes restacks and replies from people a reader already subscribes to, which means the network effects compound from existing relationships rather than depending on building new ones from scratch. According to Substack’s own data, 32 million new subscribers came from within the app in a recent three-month period — a sign that the in-platform discovery loop is working in ways Vox’s never did.
Ghost, the open-source platform that has attracted serious independent publishers since its 2013 launch, takes the opposite approach. Where Substack leans into network effects and platform lock-in, Ghost bets on ownership and portability. Your content, your subscriber list, your Stripe account — all of it remains yours. There’s no proprietary social graph to abandon if the company changes direction or shuts down. For writers who remember what happened to their Vox archives in 2010, that portability isn’t an abstract principle. It’s a hard-won priority.
The privacy question, revisited
One area where Vox’s thinking was genuinely prescient — and where current platforms are still catching up — was privacy controls. Vox understood in 2006 that not everything a person wants to write is meant for public consumption, and that the binary choice between “publish” and “don’t publish” was too crude for how people actually think about sharing.
Current platforms handle this mostly through paywalls rather than true privacy tiers. On Substack, content is either free or paid-only. Ghost offers similar gating. Neither replicates Vox’s idea of publishing to a defined social circle without requiring anyone to pay. The closest analogy in 2026 is probably the paid subscriber tier used as a proxy for “people I trust enough to share this with” — which works financially but misses something Vox understood about the social texture of selective disclosure.
The irony is that the platform that eventually solved this most elegantly was Facebook, which by 2010 had developed granular audience controls for posts that were essentially what Vox had been offering four years earlier. The difference was that Facebook had already won the social graph.
What this means for publishers choosing a platform today
The Vox story contains a practical lesson that remains relevant for anyone choosing where to build their publishing presence now. Platform features matter less than platform architecture. Vox had good features. What it lacked was a durable distribution mechanism, a sustainable business model, and — critically — a way for users to retain their audience if the platform disappeared.
Ghost’s open-source structure addresses the third problem directly: if Ghost the company ceased to exist tomorrow, you could continue running your publication on the same software indefinitely. Substack addresses the second problem through its revenue-share model, aligning the platform’s financial incentives with its writers’ success. Neither platform requires you to rebuild a social graph from scratch, which was the decisive flaw in Vox’s design.
The question worth asking before committing to any platform isn’t “what features does this offer today?” It’s “what do I own, and what happens if this company makes a decision I don’t like, or stops existing altogether?” Vox users who asked that question in 2006 would have made different choices. Many of them lost years of writing when the answer became clear.
The problem was never the product
Vox was a thoughtful, well-designed platform that arrived at a moment when one competitor had already captured its target audience and its parent company was stretched too thin to give it the development resources it needed to compete. That’s not a failure of vision. It’s a failure of circumstances — the kind that leaves a useful record for the people who come after.
The blogging platforms that have succeeded where Vox couldn’t didn’t solve a different problem. They solved the same problem with better timing, better business models, and a clearer-eyed understanding of where their users’ existing habits already lived. Email wasn’t glamorous. It wasn’t novel. But in 2017, it turned out to be exactly the right infrastructure for what writers had been trying to build since Mena Trott stood on a stage in 2005 and described a quieter, more private kind of blogging.
Vox never found its moment. The idea behind it has never stopped being relevant.
