Submit your open source tool to directories: after checkout we prioritize SourceForge plus discovery and launch directories where OSS projects find users, contributors, and cleaner listing profiles.
What you receive after checkout — no vanity metrics, just deliverables.
Operational proof from how we deliver today. Customer quotes will be added only when verified.
Directories in catalog
16
Package sizes
25–150
Intake turnaround
1 business day
Revision pass
1 per fixable rejection
Per-directory status
Each target is tracked as queued, submitted, live, or needs attention — not marked done in bulk.
Listing URLs when live
The outcome report includes direct links to live listings so you can verify coverage yourself.
Follow-up notes
When a directory rejects or asks for changes, we note why and whether a revision resubmit is possible.
FAQ
Is this the same as Submit Developer Tool to Directories?
Related but narrower. Developer-tool campaigns emphasize B2B review sites and general software catalogs. This open-source path centers SourceForge hosting/discovery and alternatives/launch communities where OSS projects are commonly listed.
Do I need a public repo before you submit?
Yes. Listings work best with a public repository or download page, clear license, short project description, and screenshots or docs. Placeholder waitlists without code usually get rejected.
Is SourceForge the only open-source directory in this set?
SourceForge is the core OSS catalog here. AlternativeTo, Product Hunt, Indie Hackers, and SaaSHub add discovery and launch coverage around the project—not substitute SourceForge hosting.
What happens after I pay for an open-source campaign?
We email an OSS checklist within one business day: repo or project URL, license, short description, logo, and screenshots. You send assets once; we submit and report listing status.