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.

We are also a home for the people doing the building. The collective exists to give contributors the resources, the structure, and the latitude to build AI in the open, and to keep what they build in the hands of the people who use it.

Why This Matters

AI is quickly becoming the most personal piece of infrastructure most people have ever used. It is the place they think out loud, work through problems, and increasingly hand off real parts of their workflow. The systems people are coming to depend on are largely owned by a small number of companies whose incentives are not aligned with the people using them. That gap is structural, and it is unlikely to close on its own.

The Nano Collective exists because we think the alternative needs to be built deliberately, in the open, by people who care about getting it right.

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.

Building that alternative takes more than good intentions, so the collective is set up to make it practical. We want contributors to have the resources and the power to build AI in the open: shared conventions and tooling that lower the cost of starting something, a community that helps carry it once it ships, and a structure that keeps the work theirs. The shared project conventions, the docs you are reading, and the community fund described below all exist for the same reason. They are how we turn the mission into a place people can actually build under.

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 on your own hardware wherever possible. Sovereignty is a spectrum: on-device by default, with privacy-preserving bridges to external capability only when the task genuinely requires it, and never at the cost of your data.
• 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 coding agent in your terminal that runs on any model you choose.
• 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.

Where We Are Heading

Today, the collective ships developer tools and utilities. The longer arc is broader: a coherent stack of open, sovereign AI infrastructure. Local-first models and tooling at the core, privacy-preserving paths to external capability where it is genuinely needed, and an open ecosystem of specialist sub-agents and tools that any contributor can build, deploy, and have used across the projects we ship.

That last part is the point. The aim is not a fixed catalogue of tools we maintain, but a place where contributors can build the next piece of it and know it has somewhere to live. We are not announcing those pieces in detail yet. They will arrive when they are real. What is worth saying now is that the projects already shipping are deliberate steps toward that picture, not isolated experiments.

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 .

The collective is volunteer-led today, and is fiscally hosted by the Open Source Collective , meaning all incoming and outgoing funds are published transparently in real time. Sustainable contributor economics, ways for the people building this to be supported by the work itself, are something we are actively designing. The terms are written down in the Economics Charter, versioned publicly so that every change is dated, explained, and applies only to new work going forward. As commercial revenue comes online, a ring-fenced community fund will pay scoped bounties to OSS contributors: nothing retrospective, nothing open-ended, all agreed before work begins.

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. And if the thing you want to build does not exist yet, the collective is a place to start it rather than carry it alone.

The collective is still early. The contributors who show up now are the ones shaping what it becomes: the conventions, the tools, the direction, and the culture. If any of that sounds interesting, this is a good moment to get involved.

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.