1,432 places to submit your product

Build your functional Joomla integration and submit a complete listing with an approved download route.

Create your working public integration or reusable Mastra template with repository and documentation for review and cross-listing.

Create a useful npe2 napari plugin for image privacy, metadata inspection or scientific redaction, publish it correctly on PyPI and let the official hub index its project metadata.

Build a stable open-source RabbitMQ plugin for your legitimate security/privacy workflow and ask the RabbitMQ team to list it.

Build your tool actions as a Raycast extension and publish through the official GitHub PR workflow.

Publish a substantial open-source Backstage plugin that integrates your tool privacy/security checks, then request inclusion if the directory does not discover it.

Build a maintained Silverstripe CMS module for your useful privacy, accessibility or URL-audit workflow, publish it with correct Composer metadata and submit it to the public directory.

Build a functional privacy, accessibility or security add-on, publish it on Packagist and create its Marketplace product page.

Build and upload a genuinely useful Vim privacy or secret-checking plugin with your tool documentation and a relevant project link.

Build a WebThings adapter, notifier, or interface extension for local privacy or device-risk controls, follow the add-on APIs, test on Gateway 2.x, and publish it to the directory.

Join the vendor program and package your tool as a legitimate one-click app or supported SaaS add-on with documentation and website links.

Use Become a Vendor to publish your tool business-software profile.

Build a production-ready PrestaShop module or theme and submit its technical package, product page and support links.

Create a scoped ServiceNow application that performs your real workflow for selected records or attachments and submit it through the Store.

Publish useful browser extension linking your tool.

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

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.

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

Build table functions that import, normalize and query your tool report JSON or NDJSON with typed findings, then submit the extension descriptor for central build and distribution.

Publish design asset or privacy checklist template.

Build a maintained OctoPrint plugin for your credible -related workflow such as privacy-safe print logs or metadata checks, then register it through the official repository pull request.

Implement a genuine OpenFeature provider, hook or integration around your configuration or audit-health use case, publish it and add it to the ecosystem documentation.

Build Make app/integration for workflows.

Post useful no-code tutorial/resource.

Publish dev utility extension linking your tool docs.

Build Zapier integration if your tool exposes API/workflows.

Pitch lifetime/free deal if your tool has paid tier later.

Build your maintained Kong integration or plugin, then pursue the technology-partner path for possible Plugin Hub inclusion.

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