License

Apache-2.0

Use it commercially, modify it, ship it inside your product, keep your changes private. No copyleft obligation, and an explicit patent grant.

Apache-2.0no CLAOSI approvedpatent grant

The short version

  • You can use it for anything, including commercially; modify it; distribute it; sublicense it; and keep your modifications to yourself.
  • You must include the licence and copyright notice, and state what you changed in files you modified.
  • You get a patent licence from every contributor, which terminates if you sue anyone over patents in this software.
  • You don't get a warranty, any liability cover, or the right to use the name to imply endorsement.

1. Why Apache-2.0 and not MIT

Versions 0.1 through 0.3 were MIT and remain MIT. That grant can't be withdrawn. From 0.4 onward we moved to Apache-2.0, for one reason: the explicit patent grant. Three organisations told us their legal review couldn't clear MIT for a tool doing inference, because MIT is silent on patents. Apache-2.0 says out loud that contributors licence their patents to users, and it says what happens if someone starts patent litigation.

We considered AGPL and rejected it. Copyleft on a tool people embed in internal workflows mostly produces legal review instead of contributions. And the thing we want back is patches, which people send when it's easy and withhold when they're compelled.

2. Contributions

There is no contributor licence agreement. You keep your copyright. By opening a pull request you licence that contribution under Apache-2.0, exactly as section 5 of the licence describes.

This is deliberate and it's the strongest guarantee on this site. Without a CLA we don't hold the rights that would let us relicense the project. About 40% of the code is contributed, so making Quire proprietary would require finding and getting agreement from hundreds of people. That's not a promise about our intentions; it's a structural fact about what we're able to do.

3. What "no warranty" actually means

Section 7 of the licence disclaims warranties, and we mean it literally and not as boilerplate. Quire produces answers from a language model. It can be wrong. Verification reduces how often, and it will never reduce it to zero.

Do not use output as legal, medical, financial or safety advice. A citation is evidence that a source says something, not proof the source is correct. If an answer is going to be relied on, a person reads the cited span first. This is the same standard we hold ourselves to.

4. Third-party components

31 runtime dependencies, all permissively licensed: MIT, BSD, Apache-2.0. No GPL or AGPL anywhere in the default dependency tree. CI checks it and fails the build if it changes. The full list with licences ships in the SBOM with every release, or run quire --sbom.

Model weights are not ours and are not covered by this licence. If you use Llama, Qwen, or any hosted model, that model's terms apply to your use of it and you should read them.

5. Trademark

The name Quire and the logo are not covered by the Apache licence . Section 6 excludes trademarks specifically. The policy is short:

  • Fine, no permission needed: saying your project uses Quire, writing tutorials, giving talks, naming a plugin quire-something, forking and keeping the name in the fork's history and attribution.
  • Ask first: naming a product or company Quire-something, using the logo as your own branding, or anything that suggests we built or endorsed your thing.
  • Not fine: distributing a modified build under the name Quire. Rename it. That's what the licence lets you do, and it keeps "Quire" meaning one specific thing.

If you're unsure, mail hello@quire.dev. We have never said no to anyone acting in good faith.

6. If we disappear

The licence survives us. Every release published is licensed permanently, forks are permitted without asking, and publishing keys are held by three parties including one outside the project so a security release is still possible. See governance.

7. Full text

The complete Apache License 2.0 is in LICENSE at the repository root and at apache.org/licenses/LICENSE-2.0. Where anything on this page differs from that text, that text governs. This page is a plain-language summary and has no legal force.


This is a demonstration site for a fictional project. The summary above is illustrative and is not legal advice. Apache-2.0 itself is a real licence; how it applies to your situation is a question for your own counsel.