Skip to Content
ProjectsProjects

Projects

The Nano Collective umbrellas a growing set of independent projects. Each has its own maintainers, roadmap, and release cadence, and they share a consistent approach to how they are structured, tested, released, and presented.

This is where the collective’s mission becomes concrete. It is a home where anyone can build AI in the open and have it land under a shared brand, a community, and a set of ready-made rails, rather than carry it alone.

There are two routes in. You can propose something new, covered in How a Project Comes to Life, or you can bring a project you are already maintaining, covered in Bringing an Existing Project.

Projects under the umbrella

  • Nanocoder : a coding agent in your terminal that runs on any model you choose.
  • Roster  (beta): an agent-run organisation, powered by GitHub. Each AI staff member is a private repo holding its charter, memory and decision log, woken by a scheduled workflow that runs any coding agent (Nanocoder included) and hands finished work back as pull requests. Site: roster.nanocollective.org .
  • Nanotune : tooling focused on fine-tuning and improving small, local models for practical use.
  • Sentinel  (alpha): an installable, Nanocoder-driven workflow that runs continuous, configurable security and code audits across the repositories in a GitHub organisation and files what it finds as issues.
  • Nanolist : a community-curated directory of AI tools, published at list.nanocollective.org . Every listing is a single JSON file reviewed by humans before it goes live, and visitors make zero third-party requests.
  • get-md : a fast, lightweight HTML, PDF, DOCX, and Markdown to Markdown converter optimised for LLM consumption.
  • json-up : a type-safe JSON migration tool with Zod schema validation.
  • prompt-scrub : a local-first tool that strips identifying content out of your prompts before they reach a cloud LLM.

Each project has its own dedicated documentation. The pages in this section cover the rules and conventions that apply across all Nano Collective projects, regardless of stack or domain.

In this section

  • How a Project Comes to Life: the path from “I have an idea” to “the project ships under the Nano Collective”. Stages, gates, status taxonomy, what you sign up for, what you get.
  • Bringing an Existing Project: the lighter route for moving an already-shipped project under the umbrella. Submission document, 14-day public review, recorded decision, migration.
  • Contributing: how to get involved with an existing project. Where to find work, how to submit, what to expect from review.
  • Creating a New Project: the conventions playbook that kicks in once a project is approved to build. Covers repo structure, licensing, CI, testing, documentation, and release.
  • Stack Suggestions: recommended tooling and conventions per language stack. The how that complements the what in the Creating a New Project guide.
  • Project Infrastructure: the shared CI, rulesets, release automation and review agent every project calls rather than reimplements. Start here for the wiring; a new repository reaches the same bar as Nanocoder in about twenty lines of configuration.

If you are starting something new under the Nano Collective, the How a Project Comes to Life page is the place to begin. If you have already built something and want to move it under the umbrella, start at Bringing an Existing Project. If you want to contribute to an existing project, the Contributing guide is.

IntroductionHow a Project Comes to Life