1,432 places to submit your product

Submit your tool product, website, owner, and category information.

Adapt your privacy-first web utility to Sandstorm's grain model, package and sign the SPK, add complete metadata and tests, then publish it for review.

Upload your original research-backed guide and reference relevant tools naturally in the document.

Create generic defensive Sigma rules for privacy-leak, credential-exposure, or scam-related log patterns, validate them, cite legitimate references, and submit a PR.

Build a genuine SMath plugin or reusable worksheet resource and register it for the public Extensions Manager gallery.

Register your tool and complete the product, company, and category fields.

Join with a transparent identity and answer relevant IT/privacy questions from direct experience; mention your resource only when it materially completes a specific answer.

Create an account and submit your tool for a dedicated startup profile and category placement.

Suggest one mature your tool utility through the official Codeberg issue path only if it is an easy-to-use, privacy-respecting replacement for a clearly identified invasive service.

Contribute a substantive accessibility role template, translation or toolkit improvement with useful source attribution.

Create your truthful /founder profile or content page and add the website link where allowed.

Create and verify an account, then submit your tool or individual qualifying tools.

Create a secure Docker Compose-based your tool self-hosted deployment, test it against TrueNAS app tooling and submit it to the official community catalog with useful documentation/resources.

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

Submit a validated manifest for an installable Windows release with PackageUrl, PublisherUrl and support metadata.

Build an XWiki extension for a useful privacy, accessibility or link-audit workflow, release it as a valid XAR/JAR and publish or import it into the official extension repository.

Submit your tool only if its AI functionality is material, with correct category, URL, pricing and product facts.

Propose a vendor-neutral, reproducible cloud-native security tutorial or case study, then write it in Markdown and submit the draft by pull request after community discussion.

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

Publish a detailed hardware or IoT project that genuinely uses your tool, with code, parts, instructions and an external tutorial link where useful.

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

Submit your polished landing/tool UI with clean screenshots and design credits.

Publish a clinical-data de-identification or quality tool with source, installation steps, dependencies, documentation, and tests.

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

Contribute a generalized privacy-by-design pattern derived from your tool experience, with problem, context, forces, and solution.

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

Create a developer portfolio and publish your original build story or project showcase.

Submit your 100-plus-word startup story for editorial consideration.

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

Create your profile and add genuinely useful homepage, privacy-tool and accessibility-tool links.

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.

Apply only after your tool becomes a legally registered nonprofit with software central to scalable public impact.

Prepare and test a policy-compliant ebuild for your stable CLI, including accurate HOMEPAGE and source metadata, then work with a Gentoo developer or proxy maintainer for repository inclusion.

Port your functional desktop or CLI utility to Haiku, write and test a compliant recipe, then submit a feature-branch pull request to HaikuPorts.

Submit a licensed computational neuroscience model with code ZIP, publication citation, overview, contributors, and tags.

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.

Register only after your tool launches a genuine open repository for reusable privacy/security research outputs.

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.

Submit your tool with the verification badge or use the no-badge paid option.

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