Loading page
General tool and software catalogues with real search traffic. There are 210 in this list, 190 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.
Create software vendor listing.
Choose the free listing or purchase your dedicated product page.
Request access, then publish your rich research-software page with source, getting-started URL, DOI, contributors, and research mentions.
Submit B2B software listing.
Archive your genuine public source repository and add its resulting SWHID permalink to release and citation metadata.
Add your tool if accepted; create company stack.
Add your tool as a SaaS or online service with its official URL.
Register as your tool vendor and add its software/service profile.
If your tool ships a real tool that reads, validates, generates, visualizes, or otherwise supports AsyncAPI documents, add the required .asyncapi-tool metadata file and submit it for the public tools dashboard.
Answer real end-user software or privacy questions in depth and reference your specific page only when it materially completes the answer.
If your component is open source and genuinely targeted at public administration, add valid publiccode.yml metadata so the catalogue crawler can discover it.
Build a generic DHIS2 health-data de-identification or permission-audit app and submit it to App Hub for core-team review.
Discuss your substantive -backed research-software quality task or resource with the Editorial Board, then contribute through its approved workflow.
Contact them to have your Windows or Mac software added to the catalogue.
Send your Windows or Mac software for review via their submission or contact page.
Release your genuinely free-software desktop or self-hosted component with free documentation and transparent downloads, then submit a custom directory entry.
Deposit your research-level open-source component or related preprint/report with accurate project and source links.
If your tool ships a macOS CLI or desktop helper, create a maintained tap with a real release, version, checksum, and official homepage metadata.
Archive your authentic release, manual or research artifact with accurate metadata and official source URL.
If your tool releases a suitable open-source Android app, request inclusion with public source, tagged APK releases, Fastlane metadata and website links.
Package a complete computational privacy or accessibility learning module and submit its reusable artifact plus Markdown paper.
Add your Mac app and keep version updates current so users get notified.
Submit your Windows utility with a PAD file or download link for editorial review.
Submit your tool product, website, owner, and category information.
Submit only your substantive free-software component that runs primarily on free systems and needs authentic Savannah project hosting and collaboration.
Submit freeware or shareware for Windows via their author submission page.
Register your tool and complete the product, company, and category fields.
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.
Ask the TechSpot team to add your app to the downloads section, with version notes.
Build your Trello Power-Up, register it, sign the developer agreement, and submit it.
Request a free listing with your tool logo, name, slogan, short description, website and best-fit category.
Register a real bioimage privacy, de-identification, or analysis tool with accurate scientific functions, documentation, and maintainers.
List your tool with live URL, icon, screenshots, category and an optional repository/demo video.
Submit your public open-source repository and product description after a reusable component is released.
Create your public repository and distribute real signed DEB, RPM, npm, Maven, Helm or other supported packages with accurate metadata.
Contact the curator with your maintained self-hostable edition, repository, documentation and project website.
List software in relevant category.
Create software listing/vendor profile.
Release one standalone your tool utility as open source, ad-free and local-first, then submit via GitHub.