Licensing

reliquary-tc is licensed under the Apache License, Version 2.0 (Apache-2.0; see LICENSE and NOTICE). It is a permissive licence: you can run, modify, host and redistribute the software, including in closed-source and commercial products, without publishing your changes.

What Apache-2.0 asks of you

The obligations apply when you redistribute the software or a derivative of it (§4). Running it, including running a modified copy as a hosted service, does not trigger them. When you do redistribute:

Give recipients a copy of the licence.
Mark files you changed with a prominent notice that you changed them.
Keep the copyright, patent, trademark and attribution notices from the source.
Pass along the attribution notices in the NOTICE file, if your distribution includes one.

The licence also carries an express patent grant from each contributor (§3), which ends for anyone who sues claiming the software infringes a patent. It grants no trademark rights (§6): the project’s names and logos are not licensed by it.

Full text: apache.org/licenses/LICENSE-2.0.

Earlier releases stay AGPL-3.0

Releases up to and including 1.34.x were published under the GNU Affero General Public License v3.0 only (AGPL-3.0-only), and a licence that has been granted cannot be taken back. If you use one of those releases, its AGPL terms still govern that copy, including §13’s duty to offer source to remote users of a modified version. Upgrading to a release made after the switch puts you under Apache-2.0.

Common questions

“Do my vault notes fall under the licence?” No. The licence covers this software, not the content of your Obsidian vault. Your notes stay yours.
“Does calling the server from my agent put my agent under Apache-2.0?” No. An agent that calls reliquary-tc’s MCP tools is using a service. It does not incorporate the server’s source.
“What about the TC Bridge plugin?” It is part of this repository and under the same licence. Read packages/plugin/package.json to confirm what the current copy declares.
“What do third-party components bundle in?” Each keeps its own licence. For what may be bundled, fetched or user-installed for the inference runtimes and models, see Vendor runtime and model licensing.

Contributing

Contributions are accepted under the Developer Certificate of Origin and are licensed to the project and its users under Apache-2.0 (§5 of the licence). Sign-off details are in CONTRIBUTING.md § License and Sign-off (DCO).