Open Saas Directory

Before you submit

Submission guidelines

Open SaaS Directory lists open-source SaaS projects and self-hosted alternatives that people can actually run. Every submission is reviewed by hand against the bar below — there's no paid placement and no guaranteed listing.

We list

What we’re looking for

  • Public, open-source repository. A public GitHub repo with a real license in the codebase — MIT, Apache-2.0, AGPL, and similar are all fine.
  • At least 50 GitHub stars. A rough signal that real people use it. We verify this automatically against the repo URL you submit.
  • Actually self-hostable. Clear install or deploy instructions — a Dockerfile, a docker-compose file, or documented setup — not a hosted-only product with code bolted on for appearances.
  • Solves a real SaaS-shaped problem. Analytics, CRM, email, project management, communication, developer tools — something people would otherwise pay a SaaS for.
  • Shipping and maintained. Installable today, with commits or releases within roughly the last year.
  • Honest about itself. Clear licensing, and, if it's open core, a clear line between the free self-hosted edition and any paid cloud tier.
We reject

What we reject

  • Closed or source-available only. No public repository, or a license that doesn't actually let you read, run, and modify the code.
  • Thin wrappers and reskins. A single API call behind a form, or a fork of an existing project with no meaningful changes.
  • Abandoned projects. No commits in years, broken install instructions, issues piling up with no response.
  • Below the star threshold. Repos under 50 stars don't yet have enough of a track record for us to verify — resubmit once they clear it.
  • Misleading listings. Fake or purchased stars, hidden pricing, or a README that doesn't match what the software actually does.
  • Not actually SaaS-shaped. General-purpose libraries, frameworks, or CLI tools with no product surface of their own.

Gray areas

  • Open core products — a genuinely useful self-hosted edition with a separately sold managed cloud tier — are welcome as long as the free edition stands on its own.
  • Fast-growing young projects under the star threshold are considered case by case if there's a strong signal of real traction — mention it in your submission.

Before you hit submit

  • A public GitHub repo URL with at least 50 stars.
  • One or two honest sentences on what it does and who it's for.
  • A README covering features, install/getting started, and tech stack — optional, but it helps review and readers alike.

Not a fit yet? Fix what's holding it back and resubmit — we re-review.

Submit a project