Founders who started as GitHub side projects
Company founders whose businesses trace back to an open-source repository they published before anyone was paying them to.
| # | Developer | Known for |
|---|---|---|
| 1 |
Guillermo Rauch
@rauchg
|
Built Socket.io as an open-source project, then founded Vercel around Next.js. |
| 2 |
Tobias Lütke
@tobi
|
Started as a Ruby on Rails contributor building an online snowboard shop, which became Shopify. |
| 3 |
Mitchell Hashimoto
@mitchellh
|
Vagrant and Terraform began as personal open-source tools before becoming HashiCorp’s core products. |
| 4 |
Amjad Masad
@amasad
|
Built an in-browser code runner as a side project that grew into Replit. |
| 5 |
Fabien Potencier
@fabpot
|
Created the Symfony framework, then built SensioLabs around supporting it commercially. |
| 6 |
Tom Preston-Werner
@mojombo
|
Created Jekyll and co-founded GitHub itself. |
| 7 |
Scott Chacon
@schacon
|
Co-founded GitHub and wrote Pro Git, still the most-cited reference on how Git actually works. |
| 8 |
David Heinemeier Hansson
@dhh
|
Extracted Ruby on Rails from Basecamp’s own codebase, then kept running the company it came from. |
There’s a common origin story hiding behind a number of well-known companies: a repository, published with no commercial intent, that solved the founder’s own problem well enough that other people wanted to use it too. Some of those repositories stayed open source forever. Others became the product a company was eventually built to support.
Neither path is more legitimate than the other, but both start in the same place - a public commit history that predates any funding.
The tool came first, the company came later
Mitchell Hashimoto built Vagrant to solve his own development-environment problem years before HashiCorp existed as a company. Fabien Potencier built Symfony to power his own agency’s projects before spinning out a business around it. In both cases, the open-source project wasn’t a marketing funnel for the company - the company was built to sustain something that already worked.
That ordering matters if you’re trying to learn from it: the project needs to be good enough to attract users on its own, with no company behind it yet, or there’s nothing later to build a business on top of.
GitHub’s own founders are on this list too
Tom Preston-Werner and Scott Chacon didn’t build a side project that became a company - they built the platform that this whole pattern now happens on top of. It’s a useful reminder that GitHub itself is a product of exactly the dynamic this list is describing: a handful of people scratching their own itch around Git in 2007, without much reason to believe it would become infrastructure for the entire industry.
What this means for your own profile
If a side project is going somewhere, the evidence tends to show up in the commit history long before there’s a pitch deck: sustained activity, real external users filing issues, and a maintainer who kept responding after the initial novelty wore off. None of that requires permission from anyone.
You can see what that early trajectory looks like on a showcase profile, or generate the same view for your own account.