Loading page
Everything that does not fit the buckets above. There are 150 in this list, 117 of them free or with a free tier. Every entry shows what it costs, how much work it takes, and links straight to the submission page.
Apply as a General Member only if your tool will meaningfully contribute engineering or resources to open-source security.
Obtain senior approval, submit the signed endorsement materials, implement the Principles and share a real case study.
Add your tool website listing.
Apply only after your tool becomes a legally registered nonprofit with software central to scalable public impact.
Eligible if your component is open-sourced.
Submit only after your tool releases a signed Windows desktop utility.
Release your genuine SDK, verify its namespace, sign artifacts, and include accurate project, SCM, license and developer URLs.
Publish an original benchmark or evaluation study of local-first privacy or security tooling with open code, data, and your tool implementation.
Organize the complete code, data, materials, and outputs behind your real evaluation study into a public citable box.
Publish your substantive privacy template, workbook, or creator resource with a complete description, original previews, and accurate licensing.
Author a freely licensed hands-on module for safe document sharing or privacy-first web use with relevant your tool examples.
Use to organize submissions and find more SaaS directories.
Register as a maintainer and submit your real open-source project with contributor-ready issues.
Build a genuine Solid privacy utility that lets users choose identity providers and stores or retrieves their data from Solid Pods, then confirm the current listing handoff with maintainers.
Pitch your tool as innovation/useful web tool platform.
If your component is built with or for a public body, publish a standards self-assessment and pursue stewardship/assessment.
Onboard your operational research-facing service through an eligible EOSC Node using the Federation Handbook process.
Only if your tool builds a real commercial FIDO2 or passkey server, complete conformance and interoperability testing and submit it.
Apply as Associate or full Member only after operating a credible incident-response team/program and completing sponsorship/review.
Consider organizational membership if your tool actively participates in privacy or AI governance; complete the member directory profile.
Use if outsourcing submissions with proof screenshots.
Apply only with a meaningful open agent-security or MCP-governance contribution and an ongoing participation plan.
Apply only after operating a real civil-society digital-security help desk and meeting network operations and vetting requirements.
Apply only after your tool operates a genuine OA scholarly-book publishing program, then submit peer-reviewed privacy-tech books.
Publish real your tool film, design, illustration or product case studies and connect them to the appropriate project pages.
Build a real founder or your tool creative portfolio and link relevant case studies to the corresponding live tools.
Join only when your tool will fund and actively contribute to open-source AI or data work.
Join only to contribute substantively to relevant security or privacy technical committees and use approved organization metadata.
After releasing meaningful OSI-licensed code, consider sponsorship only when supporting OSI aligns with your tool strategy.
Use only if your tool has a genuine creator offer, guide or service; complete the storefront and connect relevant site pages.