What we look for in a tool listing
A listing request gets a dedicated page, a category placement in the tools directory, and consideration for the relevant comparison pages once it's live — but not automatically, and not for anything closed-source or cloud-only. This site's scope is local AI specifically: a tool has to run inference (or a directly adjacent job — a vector database, a fine-tuning framework, a serving layer) on hardware the user controls, not through a hosted API. Include your license, supported platforms, and GitHub link in the submission; those three fields are what let us place the listing accurately rather than asking follow-up questions before it can go live.
What makes a strong content contribution
The guides and benchmarks that get published fastest are the ones with something specific and checkable in them: a real hardware configuration and the numbers it produced, a setup walkthrough for a platform combination we don't already cover, or a comparison built on tools you've actually run side by side rather than read about. General "why local AI matters" pieces are the hardest to place, not because the topic is uninteresting, but because the site already has editorial coverage of that angle across the learn section — a contribution earns a place faster by adding a data point or a workflow this site doesn't have yet.
Partnerships and sponsored coverage
Sponsored reviews and featured guides are labeled as such and held to the same standard as unpaid coverage: a sponsored comparison still has to say honestly where a competing tool wins, because a review that only flatters its subject isn't useful to a reader and isn't something we'll publish under our name regardless of the arrangement behind it. Rankings, comparison verdicts and benchmark conclusions are never for sale; see our editorial policy.
Internships at Neul Labs and Cognisoc
The internship tracks span AI engineering (working directly on Mullama, Llamafu, or ZigLLM), technical writing (guides, comparisons, and documentation for this site), open source development, and community management. Applying through the link above is the fastest path — mention which of the four tracks you're interested in and, for the engineering and writing tracks specifically, a link to relevant past work (a repository, a published article, or a technical blog) speeds up review considerably more than a general cover letter does.