Introduction to the Nano Collective
The Nano Collective 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. Everything we produce is open, transparent, and shaped by the people who rely on it.
Our Mission
The Nano Collective exists to make powerful AI tools more open, trustworthy, and accessible to everyone. We build privacy-first, local-first software that respects the people using it, keeps them in control of their own workflows, and avoids the lock-in, opacity, and short-term incentives that define too much of the AI ecosystem today.
We believe the future of AI should not belong only to large platforms, closed systems, or companies that can change the rules overnight. That is why we build in the open, share our work under permissive licenses, and create tools shaped by real community needs.
What We Stand For
Three values sit at the centre of every project we ship:
- Privacy-Respecting — Your data stays on your machine. Our tools respect your privacy and keep you in control of your own workflows.
- Local-First — We favour tools that run locally and offline wherever possible. No cloud required, no data leaves your machine unless you say so.
- Open for All — Built by the community, for the community. Open source and transparent from day one. No closed source features, no paid tiers gating the useful bits.
These values are not marketing — they are the filter we apply when deciding what to build, how to build it, and who gets to shape it.
What We Build
The collective builds a range of AI tools and developer utilities. Some projects currently under the Nano Collective umbrella include:
- Nanocoder — A local-first CLI coding agent with multi-provider AI support.
- Nanotune — Tooling focused on fine-tuning and improving small, local models for practical use.
- get-md — A fast, lightweight HTML to Markdown converter optimised for LLM consumption.
- json-up — A type-safe JSON migration tool with Zod schema validation.
Projects under the Nano Collective run independently — each has its own maintainers, roadmap, and release cadence — but they share a consistent approach to how they are structured, tested, released, and presented. That consistency is deliberate: it makes the collective legible from the outside, lowers the barrier for contributors moving between projects, and ensures every tool we ship meets a shared bar for quality and openness.
If you are creating a new project under the collective, read the Creating a New Project guide. It walks through the conventions every Nano Collective repository should follow — from repo structure and CI, to licensing, testing, documentation, and release.
How We Operate
The Nano Collective is a volunteer community. Contributors range from seasoned maintainers to first-time open-source contributors, and we welcome both. We coordinate primarily through:
- GitHub — Source of truth for all projects, issues, discussions, and PRs. Find us at github.com/Nano-Collective .
- Discord — Real-time discussion, questions, and coordination. Join here .
Getting Involved
Whether you want to contribute code, improve documentation, design something better, or simply spread the word — we would love your help. There is no application process. Find a project that interests you, read its CONTRIBUTING.md, and open an issue or PR.
Contributions we value (not exhaustive):
- Code — new features, bug fixes, provider integrations, performance work
- Documentation — guides, examples, references, translations
- Design — visual identity, UX improvements, brand assets
- Community — answering questions, triaging issues, welcoming new contributors
- Advocacy — writing, speaking, or sharing the work
A Note on This Documentation
This docs site is primarily operational. It exists to give the collective a shared reference for how we work — the conventions, expectations, and playbooks that keep our projects consistent and legible. It is published openly because transparency is one of the values we hold ourselves to, but its main audience is the people contributing to and maintaining Nano Collective projects.
If something here is unclear, outdated, or wrong, open an issue or a PR on the docs repository . These docs are meant to be iterated on.