How to launch an open-source project
An open-source project needs a different launch from a SaaS: the repository is the product page, stars and recent commits are the social proof, and contributors matter as much as users. This guide covers the preparation and the places that treat open-source launches well.
Before you launch an open-source project: the repository is the product page
When you launch an open-source project, most visitors go straight to the repository. They decide in seconds whether it is worth a star, a try or a contribution, so prepare it the way you would prepare a landing page.
- A README that says in the first two lines what the project does and who it is for, followed by a one-command install or a hosted demo.
- A license file with an OSI-approved license (MIT, Apache-2.0, GPL, AGPL, BSD, MPL…). Without one, people legally cannot use your code, and launch platforms that verify open source will not count it.
- A screenshot or short GIF near the top of the README.
- Recent commits and a tagged release, so visitors can see the project is alive.
- Issue templates and a CONTRIBUTING file with a few “good first issue” labels for people who want to help.
- A project website or docs page if you have one; otherwise the repository URL is your launch URL.
Where to launch an open-source project
Launch platforms that show repository data
On ProductPerch, add your GitHub URL when you submit. We read stars, forks, license, primary language and the last push date from the public GitHub API (cached for 6 hours) and show them on your product page and in lists. Projects with a public, non-archived repository and an OSI-approved license can use the 3 free launch slots we keep for open source every day, and get a dofollow link without placing a badge. DevHunt focuses on developer tools, runs weekly launches, asks voters to sign in with GitHub or Google, and is itself open source.
Directories of open-source alternatives
If your project replaces a known SaaS, list it where people search for alternatives. OpenAlternative’s tool pages show GitHub stars with their 30-day change, last commit, repository age, license and whether the project can be self-hosted. Note that its outbound links were nofollow when we checked, so list there for readers, not links.
Developer communities
Share the project where developers who have your problem already talk, and follow each community’s rules about self-promotion. Explain why you built it and what is still missing; people are more willing to try and contribute to a project whose author asks for feedback than to one that is presented as finished.
Launch week
Pick one main launch day and stay online for it. Answer every comment and issue, merge small fixes quickly, and tag a release when you fix something people reported. Stars on launch day matter less than what people find when they come back a week later: an active issue tracker and recent commits.
After the launch
Add the launch badge you earned to your README; ProductPerch has badges for Featured on, Launching today and the daily top 3. Keep a short changelog so later visitors can see momentum. If your project also has a hosted version, the SaaS launch plan covers the paid side.
Ready? Submit your repository or browse open-source launches.
Sources
- DevHunt FAQ (read 11 Oct 2026)
- OpenAlternative tool page (Plausible) (read 11 Oct 2026)
- Open Source Initiative: approved licenses (reference)
- GitHub REST API: repositories (reference for the fields we read)
We run ProductPerch, which appears in these comparisons; we are not affiliated with the other platforms. Prices and rules change: tell us about anything out of date at contact@productperch.com.
More launch guides · Today’s launches on ProductPerch · Submit your product free