1,432 places to submit your product

Apply through the official Linux Foundation enrollment if your tool will genuinely implement or contribute to C2PA standards.

Apply as an eligible Indian software or ITeS exporter with company, GST, IEC/DGFT and RCMC evidence as requested.

Propose a concrete funded or in-kind your tool anti-scam, privacy or cyber-safety collaboration through Become a Partner.

Build a Nova extension that runs your tool privacy and code-safety checks from the editor.

Build a Sketch plugin for accessibility, metadata cleanup, or sensitive-placeholder detection.

Build a destination or function that sends only explicitly selected and sanitized events to your tool for PII or schema checks.

Join as the founder, create one your tool project page, and share genuine shipped improvements with links only when useful.

Publish useful browser extension linking your tool.

Package your commercetools Connector and request certification and public Marketplace listing.

After publishing a mature security policy and VDP, contact the Secretariat to apply as a signatory to all four principles.

Submit a working AI feature with accurate categorization, pricing, description, and screenshots for quality review.

Apply as an eligible Member or Partner and contribute resources or expertise to real cyber-capacity-building working groups.

Build a Homey app only if your tool adds a genuine IoT privacy or local-device workflow; package, test, validate, and submit it for certification.

Start privately, mature the process, then publish your program indexed in Intigriti's public directory.

Publish a Max package for media metadata inspection, audio privacy, or accessibility analysis.

Create a founder blog that shares compact product lessons and full tutorials linking to your relevant page when useful.

Build a working Miro app for board accessibility, privacy, or export auditing; establish real users and demand before applying through the partner route.

Host your maintained open-source component with complete README, homepage/source metadata, releases and optional pages.sr.ht docs.

Submit only your specific AI tool with the official site and contact email, not the platform as a generic tools directory.

Email the directory team to request your profile for its genuine accessibility tools.

Consider only after your tool has a substantial AI feature and the directory offers business value beyond a link.

Consider only after your tool becomes a substantive cloud or AI security vendor and can participate in CSA programs.

Onboard your operational research-facing service through an eligible EOSC Node using the Federation Handbook process.

Onboard only when your tool is a mature, live and independently valuable service for the European research community, under a legal or hosting entity.

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.

If your tool ships an OpenID Provider or Relying Party, pass the suite, publish evidence, sign the declaration and submit the implementation.

Use if outsourcing submissions with proof screenshots.

Submit only AI-specific your tool modules.