We couldn’t be more excited to announce that StackShare is now one million developers strong! Over 1M developers, engineers, CTOs, VPEs, architects, and founders have joined StackShare and created a profile showing off the tools & technologies they know and love. We want to thank each and every developer that made this possible. To see when you joined the StackShare community, log in to your account and head over to your user profile and you'll see a new banner:
Click the blue tweet link on your profile to share what number developer you were and your experiences by tagging us @stackshareio.
To commemorate this milestone, we’ve put together a timeline of StackShare’s history below that describes how this all began and how StackShare has evolved over the years.
StackShare began as a simple concept: see what other developers and companies are using so you can figure out what you should use, since there are so many tools out there. That’s still the core of what StackShare is, but it’s much more. StackShare is now:
- The best place to have focused tech stack discussions with over 20,000 discussions, 30,000+ tools and technologies listed, 150,000+ company tech stacks shared, and 400,000+ votes.
- The standard way for developers and companies to share what tech stack they use.
- The best place to keep up with the latest and greatest developer tools. Last year alone, we analyzed 8M+ data points for our annual roundup of the year’s top developer tools.
- The best way to understand what tech stacks are being used inside your company via Private StackShare.
The future of StackShare
TLDR - similar to GitHub’s business model, StackShare is free to use publicly while private StackShare is a paid service (which you can use for free) with tons of additional functionality (automatically mapping out tech stacks via Git integration, tech stack reporting and alerts, SSO, and more).
One thing many community members have asked over the years is “how does StackShare make money?” Up until last year, the answer was that we primarily made money from native ads (no outside networks or retargeting). Developer-focused companies like Datadog, Segment, CircleCI, LaunchDarkly, and others pay to spread the word about their products to the StackShare community on tool profiles, comparisons, and stack profiles. We also launched a premium recruiting profile for companies to list open job postings and we also have a paid API offering. So our business model resembled LinkedIn’s in the early stages, with multiple revenue streams.
Then in late 2019 we started getting requests from engineers and architects that work at large companies that have hundreds of developers and thousands of different codebases. The requests seemed straightforward enough: they wanted a private version of StackShare that would allow them to map out their tech stacks and help their engineering teams collaborate internally.
So we started down a path to build a private version of StackShare and eventually launched a free tier of Private StackShare on the GitHub Marketplace late last year during GitHub’s Annual Universe Conference. Fast forward to today, and we’ve built Private StackShare into an enterprise-grade SaaS offering that hundreds of companies are now using to collaborate on tech stacks internally.
Just like every dev team now has a code collaboration solution, we believe that every dev team in the world should have a tech stack collaboration solution. Every dev team should know what tech stacks they’re using (open source and SaaS, down to the package versions), why they were chosen, and who knows how to use them internally. And all of that should be automatically updated as developers ship code and it should be built into your current workflows (GitHub, Slack, etc).
For individual developers, Private StackShare helps you:
- Get back to coding faster by easily letting you see who to ask about which tools (e.g. see every dev across your company that knows how to use Kafka)
- Discover new libraries and tools being used inside your company by teammates on other eng teams (e.g. a new React router package was added by a teammate on another team)
- Build up your internal tech resume and show off which tools you know to your teammates and be the go-to contact for specific technologies (e.g. anytime a project related to Amazon RDS is spun up, the team knows to get your advice)
- Build internal communities by finding developers using the same technologies
If you haven’t tried Private StackShare yet, go ahead and give it a shot for free! stackshare.io/private.
Thank you again to every single community member that has shared your stack, upvoted, commented, posted, and spread the word about StackShare over the years. This milestone was only possible because you chose to join StackShare.