Loading page
Everything that does not fit the buckets above. There are 150 in this list, 117 of them free or with a free tier. Every entry shows what it costs, how much work it takes, and links straight to the submission page.
Deploy your maintained MCP server from GitHub, Docker, npm, or PyPI, verify maintainer ownership, and switch it public only after production testing.
Publish a genuinely reusable privacy or accessibility lesson on your tool, give it a stable URL and open license, then add its educational metadata to MERLOT.
Create your original interactive privacy or accessibility guide and add relevant external actions to cited live tools.
Request an audit for your mature open-source security component, providing maintainer contacts, architecture, threat model, scope, tests, and a remediation commitment.
Create or import your genuine show, keep it public, set its official Website field and publish useful episodes.
Propose a text-based, interactive course on web privacy, security headers, local-first tools, or accessible frontend testing, with practical code exercises and clear outcomes.
Publish your real episode and add contextual links to resources actually discussed in its show notes.
Propose a genuinely open-source, privacy-preserving your tool component with a public roadmap, Indian community benefit, budget, milestones, and maintenance plan.
Create your real Airflow provider with hooks/operators and documentation metadata, publish it, then add it to Airflow’s Ecosystem page by PR.
Recommend your official API with its documentation URL, concise Markdown description, category, and technical details.
When your tool exposes a stable public API, host an official OpenAPI definition at a permanent URL and submit it with accurate ownership, category, logo, and metadata.
After open-sourcing a maintained component, submit the TOML project file and website through GitHub PR.
Offer a substantial free privacy checklist, accessibility workbook, or safety template from a branded storefront and link your tool only as supporting documentation.
Host a genuine public accessibility learning or testing event and submit its dates, description and your tool event URL.
Search for and claim your real podcast, then keep its RSS-supplied website and episode metadata accurate.
Audit every your tool subdomain, stage HSTS safely, then submit the base domain only after long-term HTTPS readiness is proven.
Submit your real podcast RSS feed whose show website and episode notes naturally reference relevant tools.
Implement a scoped open-source compliance or security-assurance program, self-certify honestly, then request your tool Community of Conformance listing.
Submit your genuine podcast RSS feed or Apple Podcasts URL with accurate show-website and episode metadata.
Submit your real public podcast RSS feed whose metadata and episode notes reference the official site naturally.
Submit your tool MCP repository or public server URL, preferably after publishing it to the official MCP Registry.
First pass PWA checks, then submit the installable HTTPS app with manifest, service worker, offline behavior, icons, and screenshots.
Publish an open-source Sensu check/handler for your tool, create GitHub releases and bonsai.yml, then register it with description and tags.
Create a useful StackStorm integration or automation pack for your workflow, then submit it through the official Exchange Incubator pull-request process.
Submit and verify one genuine your tool podcast feed for distribution on Amazon Music and Audible.
Build a Bitrise Step that runs your tool secret, privacy, or accessibility checks on explicitly chosen build artifacts.
Add or claim your real podcast in Creator Studio and complete channel, site and episode metadata.
Create a defensive parser, scenario, or collection for your real -supported log source, document and test it, then submit it to CrowdSec Hub.
Create a TypeScript or Go module that runs your tool web audits in CI and returns machine-readable JSON/SARIF with useful pass/fail thresholds, then publish it to Daggerverse.
Submit your tool through the official reviewed product form.
Run the website and email tests, fix IPv6, DNSSEC, HTTPS, security headers, DMARC/DKIM/SPF, STARTTLS/DANE, and RPKI gaps, then retain a 100% score.
Create a genuine JavaScript SDK or demo on GitHub Pages and request an appropriate js.org subdomain that links to its official your tool documentation.
Contribute your provider bundle with useful privacy or security components and provider documentation links.
Submit your maintained desktop or CLI utility only after it runs natively on a modern Linux distribution and has a public OSI-approved license and repository.
Build and teach a live, project-based cohort on creating local-first privacy tools or accessible web utilities, supported by a substantive public syllabus and real instructor profile.
Upload your original audio explainer and place relevant resource links naturally in the show description.
Share your openly licensed digital-safety lesson pack or Moodle activity and curate it into an educator-focused collection.
Create a useful quickstart for monitoring your real deployment, with instrumentation instructions, a working data source, dashboards, alerts, documentation, and a GitHub contribution.
Publish a machine-readable privacy, accessibility, or scam-pattern dataset or API and complete its evidence-based public certificate.
Build a functional OPA/Rego privacy-policy integration or developer tool, document it, then add its ecosystem entry and logo through the official docs repository.