Open source, not open season
Clausery is free software — free to use, read, modify and self-host — but the Clausery name and logos are trademarks, and anyone offering a modified version over a network has to publish their changes. Here is how that works.
Code license: GNU AGPLv3
Everything in this repository — the document engine, UI, templates and public site — is published under the GNU Affero General Public License, version 3, or (at your option) any later version. That is the same license WordPress, Nextcloud, GitLab Community Edition, Mastodon and many other network software products use. You can read the full legal text in LICENSE.
What that means in practice:
- Use it: run Clausery for yourself, your team or your company, for free.
- Study it: read every line of code, including the parts that assemble the .docx and the parts that verify license keys. There are no obfuscated binaries.
- Modify it: patch it, add templates, translate it, run it on your own domain for your team.
- Redistribute it: give copies to other people, publicly or commercially, AS LONG AS you keep the AGPLv3 license on the copy and publish the corresponding source code of your version.
- Run a modified version for others over a network? Section 13 of the AGPL requires you to offer your users the complete corresponding source code of your modified version at no charge, from the same service. That is the clause that stops a competitor taking the code, rebranding it and selling it as a closed SaaS without giving anything back.
Trademarks: what the AGPL does NOT cover
The AGPL covers code. It does not grant permission to use the Clausery word mark, the logo/app icon, marketing copy, screenshots, social accounts or domain. Those are reserved to the project. They are the part that tells users they are on the real tool, not a clone.
The full policy is in TRADEMARKS.md. In short: name your fork something else, swap the logo for your own, and add a one-line credit ("Built on Clausery (AGPL-3.0) · view source") in your footer and in your app's sidebar. Nominative references ("our tool is built on Clausery", "forked from Clausery") are fine.
What the "Made with Clausery" line is for
Documents made from free library templates on the Free plan end with one small line, "Made with Clausery · getclausery.github.io". That line is how people who receive a free invoice find the tool — the equivalent of a WordPress "Powered by" line — and it doubles as the attribution that lets the free tier exist. Pro, Team, Enterprise and commercial-license deployments remove it from documents.
Commercial licenses
We sell commercial licenses to teams who want to:
- White-label Clausery inside a closed product or intranet without the AGPL source-offer obligation;
- Embed the editor in a paid SaaS under their own brand;
- Deploy a heavily-modified internal version without publishing their customisations;
- Use the logo or product screenshots in marketing.
Commercial licenses fund new templates, maintenance and the perpetual free public release of the core product. Email getclausery@gmail.com via the contact page with how many users and what you are building — most small teams get a flat quote back quickly.
Contributing
Pull requests are welcome. See CONTRIBUTING.md for how to set up. By opening a PR you agree your contribution is licensed under the same AGPL-3.0-or-later; no CLA required.
Security
Report security issues privately via GitHub's private advisory reporting or by email, as described in SECURITY.md and security.txt. Do not open a public issue for a security vulnerability.
Why AGPL instead of MIT or BSD?
Clausery is a client-side product that competes with paid SaaS tools. A permissive license (MIT, BSD, Apache) would allow competitors to take the code, rebrand it, close the improvements and sell it as their own — which has happened to many MIT-licensed developer tools. The AGPL keeps the code free and keeps improvements free while still allowing commercial use through a paid dual-license, which is the model used by other developer-focused open-source companies (Ghost, Grafana Labs' AGPL components, Element/Matrix, Plausible, Mastodon, GitLab CE). It is the OSI-approved license that matches how Clausery is actually used: over the network.
The software is provided "as is" without warranty, as described in the terms of service.