1,432 places to submit your product

Submit a specific live AI-powered your tool route with a clear short and long description and its canonical URL.

Build an Automation 360 bot or package for your document, privacy, or evidence workflow and submit dependencies plus a working demonstration.

Build a real Heroku add-on or qualifying open-source buildpack and progress it through the partner release stages.

Package your deployable self-hosted architecture for IBM Cloud, complete Partner Center onboarding, and request public catalog approval.

Package a supported OCI-hosted or deployable your tool edition, or a genuine Oracle integration, and create a documented publisher listing.

Submit novel privacy-technology research plus a reproducibility artifact that links to its public implementation.

Package your supported self-hosted edition or integration for RHEL or OpenShift and complete Red Hat Partner Validation for a catalog page.

Submit your tool with logo, pricing model, concise tagline and a unique product description.

Develop your real SAP-integrated solution, onboard it through SAP Solution Hub, and provide website, technical, support, and commercial information.

Build and document a real Adalo component library for your workflow and apply for marketplace publication.

Offer your tool as a documented SaaS or BYOL deployment for Alibaba Cloud customers with clear privacy controls and support.

Sponsor your tool’s strongest browser or JavaScript-based developer utility with copy tailored to working JS developers.

Run a clearly disclosed campaign for your tool’s developer and security tools across relevant Changelog podcasts or newsletters.

Use a real writer or designer identity, add authored your tool work as a properly credited clip or case study, and include the personal website link in the profile.

Publish a reusable Defold privacy-safe logging, security, or build-audit tool.

After your tool has a genuinely open-source, well-documented public-interest component, complete the eligibility assessment and nominate that specific component.

Build a genuine FIWARE-powered privacy, consent, data-space, or civic-safety solution, document its architecture and data models, then submit it for expert validation.

Create a GDevelop extension for safe local storage, consent UX, or secret-free analytics configuration.

Build your public OAuth integration, gain qualifying installs, then submit setup docs plus support, privacy, and terms URLs.

Open-source your reusable research-focused component, archive it with a persistent identifier, and submit a software metapaper with project/code links.

Obtain senior approval, submit the signed endorsement materials, implement the Principles and share a real case study.

Build a genuine Salesforce package or API solution for selected-record privacy or document checks and complete its company and listing profile.

Submit a mature macOS, iOS, or web companion app that provides your privacy workflow and links to its official product documentation.

Build a Shopware admin extension for privacy and accessibility checks on selected catalog content, media, and exports.

Build a SketchUp extension for model metadata sanitization or accessibility-ready export checks.

Build a Stripe app that sends selected non-sensitive invoice or export data to your clearly scoped audit and publish complete documentation.

Place your targeted campaign in TLDR Dev, InfoSec, AI, Tech, Product, or Founders with a focused landing page.

Build your VTEX IO storefront or admin privacy utility, define billing, and submit it for homologation.

Publish a secure one-click self-hosted your tool image or cloud-init deployment with documentation and support.

Build a production-grade Camel component for your tool APIs and propose it upstream with generated component docs and tests.

Submit your -related astronomy utility only after it has been used in research submitted to or published by a refereed journal.

Create a tested Bioconda recipe for a genuinely biomedical or bioinformatics your tool utility, with accurate homepage/source metadata, and submit it through the official review workflow.

Contribute a documented bioimaging privacy or de-identification model, application integration, or other qualifying resource linked to your tool.

Publish a documented social, ecological, or computational model with source, narrative documentation, contributors, and reproducibility metadata.

Open-source a relevant geoscience model or component, complete the model questionnaire, and provide its code archive for CSDMS testing.

Build a Cytoscape 3 app for a genuine graph privacy, provenance or network-audit workflow, provide website/source metadata and submit its first release for administrator approval.

Create a policy-compliant Debian package for your stable useful CLI, file the appropriate intent-to-package request, include accurate upstream metadata and secure a Debian sponsor for upload.

Create and thoroughly test a FreeBSD port for your stable CLI or desktop utility, include its canonical project website in WWW metadata and submit the patch through FreeBSD Bugzilla.

Build a tested Galaxy wrapper for your medical-data privacy or de-identification workflow and publish it in the main ToolShed.

Develop a stable ioBroker adapter for your credible privacy/security API, publish the npm package, test it with users and request inclusion in the official latest repository.