My Experience
StackShare is less of a “startup directory” and more of a developer decision layer — people come to see what tools real companies and developers use, compare alternatives, and read community pros/cons and stack decisions.
It’s especially strong for dev tools because discovery often happens through:
- browsing company stacks,
- “X vs Y” comparisons,
- “X alternatives” pages,
- and trending/category lists.
StackShare has been operated as part of FOSSA since 2024, and the platform continues to be actively updated.
Submission Process
-
Check if your tool already exists
- Search StackShare for your tool name.
- If the tool page already exists, click “Claim this tool”.
-
Claim + verify (free)
- Verify via email on your official domain or GitHub repo permissions (for OSS tools).
- Once verified, you can edit your description, categories, links, logo, and images.
-
If your tool isn’t listed yet
- Use the “List a Tool” flow from the Tools area/homepage (you may be asked to sign in).
- Provide the basics: name, website, category/layer, and (if applicable) GitHub/docs links.
- New listings may go through a short approval/review step.
-
Optimize your listing
- Add: Website + Docs, and a GitHub repo if relevant.
- Upload a crisp logo and a clear hero/screenshot.
- Pick the most specific category (this matters for discovery).
Tips for Success
- Write for developers, not marketers. One-sentence clarity beats hype.
- Get verified ASAP. Verification is free and helps trust; verified tools can also get preference when ranking scores are similar.
- Drive real stack additions. Trending is driven by stack additions, with recent adds weighted more.
- Seed authentic “why we chose it” content. Encourage users to write stack decisions and pros/cons (don’t spam).
- Own your “Alternatives” positioning. Make sure your category is correct so you appear in relevant comparison and alternatives pages.
- Keep it current. Update the description and links when you ship major features or rebrand.