The Nano Collective crossed 100,000 total downloads across its open-source AI tooling: Nanocoder, Nanotune, get-md, and json-up. The number felt big enough to mark, and small enough to be honest about what it represents.
What this number is, and what it isn't
A download is a low-friction signal. It does not tell us anything about who installed, what they did with the tool, or whether they kept it. Across four packages, 100,000 of them is still useful information: it tells us that the work is being found, that the install path is working, and that people are willing to put the collective's tooling on their machines.
What it does not tell us is that the model is finished, or that the audience is locked in. It tells us the direction is landing. That is worth pausing on.
What the collective builds
For anyone encountering the Nano Collective for the first time: it is a community-led group of developers, designers, and maintainers building open-source AI tools for the people who use them. We build not for profit, but for the community.
The packages in scope for this milestone:
- Nanocoder, a coding agent in your terminal that runs on any model you choose. The flagship project, and the one that has driven the largest share of installs.
- Nanotune, tooling focused on fine-tuning and improving small, local models for practical use.
- 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.
Everything the collective ships is open. You can audit the code, fork it, contribute to it, or simply run it without an account or a third-party dependency. The Economics Charter locks in how the collective operates: no investors, no profit-taking, no extraction. Funds cover infrastructure costs and contributor bounties only, and the Open Collective ledger publishes every incoming and outgoing payment in real time.
Why this is a different shape of milestone
The tooling landscape for AI-assisted development has grown rapidly, and a large share of it routes data and prompts through proprietary platforms. That model is a choice, not an inevitability. Local-first, open-source tooling exists as an alternative: one where your code and your queries stay on your hardware, where the behaviour is auditable, and where the community shapes the direction rather than a product team at a company with an IPO to plan.
100,000 downloads across four packages is a sign that this model resonates beyond the early-adopter circle. It is developers and teams making a practical choice: they want tools that work this way. That is the part of the milestone that matters to us, more than the number itself.
What this milestone does not claim
It does not mean the collective is large. The core team is small, the contributor pool is modest, and there is a long backlog of work that is under-resourced. It does not mean the tools are finished. Each project has open issues that have been waiting for someone to pick them up. It does not mean the operating model is solved. Governance, contributor compensation, and project stewardship all have open questions that the collective is working through in public.
What it does mean is that the work has reached a community large enough to be self-sustaining in spirit: there are enough people using the tools, and enough people willing to push back on direction, that the collective can keep going without an outside funder deciding its priorities. That is the milestone.
What's next
The work continues, and the priorities for each project live in their own public roadmaps:
- Nanocoder, broader model support, deeper terminal integration, expanded skill system.
- Nanotune, better defaults for small-model fine-tuning, broader evaluation tooling.
- get-md, additional input formats, improved handling of edge cases in real-world documents.
- json-up, schema-diff ergonomics, expanded migration primitive coverage.
If you want to contribute, whether through code, docs, design, feedback, or sponsorship, every project has a CONTRIBUTING.md and open issues tagged for contribution. The collective's governance and contributor resources are documented at docs.nanocollective.org.
If the work is useful to you and you'd like to support it financially, see Support the Collective.
Thanks
Thanks to everyone who has downloaded a package, opened an issue, reviewed a PR, written a doc, shared a project with a colleague, or simply given one of these tools a try. The number belongs to the community that produced it. We are grateful, and we are not going to waste it.