Before AWS existed, one company ran the servers for Twitter, LinkedIn, and Facebook's entire app ecosystem.
They owned Node.js, invented containers 8 years before Docker, and Peter Thiel even backed them.
Then something happened...
In 2004, a cancer researcher turned entrepreneur named Jason Hoffman started a cloud company called Joyent.
While Amazon was still figuring out AWS, Joyent was already hosting the internet's hottest startups.
Their client list would make your jaw drop.
Twitter's early infrastructure ran on Joyent servers.
LinkedIn scaled on Joyent.
When Facebook opened to third-party apps in 2007, Joyent partnered with Dell to host them all.
But that's not even the craziest part.
Thousands of Facebook apps (and their millions of users) ran on Joyent's cloud.
Some accounts suggest Joyent even helped power Facebook's chat feature.
They were literally everywhere. Just invisible.
And they had technology that wouldn't exist anywhere else for 8 years.
Joyent built their own operating system called SmartOS. It used "container virtualization" via Solaris Zones.
This was in 2005.
Docker didn't exist until 2013.
But here's why being 8 years early was actually their biggest curse.
Their containers were so efficient that one Joyent server could handle what took multiple Amazon EC2 instances.
Industry experts called it "way better than AWS."
But they made one technical choice that would haunt them forever.
They built it on Solaris. Developers wanted Linux.
While Joyent was fighting this compatibility battle, they made a hire in 2010 that should have changed everything.
They brought in the creator of something you probably use every day.
Ryan Dahl. Creator of Node.js.
Joyent became the steward of what would become one of the world's most important developer platforms.
Today NASA uses Node.js. Netflix uses it. LinkedIn, Uber, PayPal all use it.
Yet somehow, owning Node.js wasn't enough.
Because Jeff Bezos had a philosophy.
"Your margin is my opportunity."
AWS slashed prices constantly. They opened data centers globally. They spent billions.
Joyent tried to match Amazon's pricing. But they were fighting a company with infinite money.
And Amazon understood something about developers that Joyent completely missed.
Amazon built an empire on developer evangelism.
Free tiers for startups. Massive documentation. Global conferences like re:Invent. One-stop shop for everything.
Joyent stayed niche. Elite, but niche.
Then they made the decision that sealed their fate.
Joyent chased big enterprise and telecom customers like Telefonica.
Amazon chased everyone. Every startup. Every developer. Every student learning to code.
By 2010, "cloud" meant AWS. Joyent was already forgotten.
The acquisition offer that came next was insulting.
2016: Samsung acquires Joyent for ~$125 million.
For context, AWS was worth $100+ billion by then.
The company that invented containers and owned Node.js sold for pocket change.
But Samsung's ownership made things even worse.
Under Samsung, Joyent limped along for three more years.
2019: They shut down their public cloud entirely.
The company that once powered Twitter started helping customers migrate to AWS.
The irony gets worse when you see what their technology spawned.
Joyent's DNA is everywhere. Every Node.js application. Every Docker container. Every Kubernetes cluster.
They invented the future of cloud computing. They just couldn't sell it.
Want to know the real gut punch?
Samsung paid $125 million for technology that influenced over $1 trillion in market value.
AWS is worth $100B today. Docker hit $2 billion. The Node.js ecosystem generates billions annually.
Joyent captured none of it.
The lesson?
In tech, being first doesn't matter. Being best doesn't matter.
Scale matters. Distribution matters. Pricing matters. Ecosystem matters.
Joyent had the technology to change the world.
Amazon had everything else.
Thanks for making it to the end!
I'm Alex, co-founder at ColdIQ. Built a $6M ARR business in under 2 years.
We're a remote team across 10 countries, helping 400+ businesses scale through outbound systems.
RT the first tweet if you found this thread valuable.
Follow me @itsalexvacca for more threads on outbound and GTM strategy, AI-powered sales systems, and how to build profitable businesses that don't depend on you.
I share what worked (and what didn't) in real time.
You know those AI apps that always work? They all use JSON prompts.
Started using the same format for my AI prompts and my outputs became shockingly consistent.
Here's exactly how to write JSON prompts (with code, screenshots, real examples):
What you'll learn in this thread:
→ What JSON is & why LLMs love it
→ Basic JSON prompt structure
→ API modes that guarantee valid output
→ Templates for extraction, generation, analysis
→ Production patterns & error handling
→ Real automation examples
Let's start:
JSON = JavaScript Object Notation
It's just data with labels. Think of it like a form where every field has a name.
Why it works: LLMs are trained on millions of JSON files from APIs and code. It's their native language.