1,432 places to submit your product

Join a working group and contribute a substantive building-block specification, use case, reference implementation or new proposal.

After releasing your real CLI or native app, submit a tested formula or cask with its canonical homepage.

Join an approved organization and publish a documented humanitarian privacy/safety dataset with licence and responsible-access settings.

After your tool has a stable, commonly used JSON or YAML configuration format, contribute its accurate schema and test fixtures so editors can provide validation, completion, and tooltips.

Apply with your concrete privacy, security or user-autonomy FOSS work package, milestones, budget and public repository.

Use ORCID to publish genuine research stages—problem, method, data or analysis—with contextual your tool code/data links.

Create a maintained Omeka S module for collection metadata privacy, accessibility or link auditing, package it correctly and register the add-on with project and author links.

Create a rigorous structured comparison of published privacy, redaction, or accessibility studies and include your tool only when supported by research.

Create a public reproducibility project for your tool research, datasets, test methods, or privacy benchmarks and link the genuine project/site.

Create a public case-study portfolio and add your tool with screenshots, live demo and build rationale.

After your tool has eligible ReliefWeb content, request publishing access and submit humanitarian reports or training from verified owned URLs.

Create your reproducible evaluation project with code, data connectors, environment, narrative, and a public session launcher.

Create a reproducible Tale containing your evaluation's data, code, environment, outputs, and narrative, then publish through a supported repository.

Launch your properly scoped vulnerability disclosure or public bug-bounty program.

Launch your defensive vulnerability disclosure or public bug-bounty program with managed researcher access.

Publish a Canadian-ready, openly licensed privacy or digital-citizenship textbook and use Contribute → Suggest a Textbook.

Launch your real educational podcast, complete its public site, and cite relevant tools and sources in useful show notes.

Publish a polished original guide, research brief, or accessibility zine as a public document, with useful references and your relevant link inside the editorial content.

Create an authentic your tool or founder design portfolio with substantive case studies and contextual links to shipped tools.

Create your complete product case study and add the canonical URL naturally within project text or a linked image.

Pitch an original evidence-backed privacy, scam, or cyber advisory based on genuine your tool research.

Publish a mature open-source interoperability or public-administration solution with documentation, releases, licence, and owner metadata.

Create a founder portfolio with original your tool launch notes or product case studies and use an external-link page for the canonical website.

Build your free mobile mini-site with brand story, key collections, demos and contact links.

Submit useful your tool-related talks to relevant CFPs or run a genuine community CFP with a public event page.

Submit an educational, non-sales session on privacy-safe tooling or accessible creator workflows when the next CFP opens.

Claim a builder profile and add your tool as a shipped project using its live public URL.

Use pretalx for your genuine community conference or submit relevant talks to events that use the platform.

Submit a reusable open-source React component extracted from your tool with repository, demo, setup docs and screenshots.

Document your real implementation of a named RDA recommendation with challenge, measurable outcome, lessons, and supporting resources.

Pitch original your tool security research, a defensible dataset or timely threat analysis.

Create a public privacy-tool research library with credible standards, papers, and references, including only genuinely relevant your tool documentation.

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

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

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

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

Create a portfolio for genuine your tool product/design work and use each project's external URL field for the matching live page.

Create a founder or product-design portfolio with your original case study and add the canonical site as an external menu link.

Create a legitimate free or paid your tool resource or software product and publish it on a branded hosted storefront.

Apply only with a validated open-source privacy or anti-surveillance project that directly helps users facing repressive censorship or surveillance.