Terms

Opplet is meant to be read, used, and forked. These terms set out the few conditions on that — deliberately minimal, because the project’s whole purpose is to give things away rather than fence them off.

Using this site

You are welcome to read, share, and link to anything on opplet.com. The site is provided as-is, as a working demonstration and a set of documents. We make no warranty that it is complete, current, or fit for any particular purpose — it is a prototype shown openly, not a product sold with guarantees.

The blueprint, and the software it runs

There are two different things here, under two different sets of rights, and the distinction matters if you intend to fork.

Opplet’s own work — this site, its templates, its configuration, and the way the zones are composed into a working enclave — is the blueprint. It is released under AGPL. That license, once set, is what grants you the right to clone or fork opplet and build your own enclave from it.

The software opplet deploys — Moodle, HestiaCP, GitLab, n8n, ERPNext, and the rest — is not ours and is not covered by opplet’s license. Each package carries its own license, set by its own authors, and your use of it is governed by that license, not by these terms. Some are permissively licensed; at least one (n8n) is source-available with commercial-use restrictions rather than fully open-source. If you fork opplet and deploy these tools yourself, you take on the responsibility of honoring each one’s terms directly. Opplet points at them; it does not relicense them.

Forking and your own enclave

When you stand up your own enclave from opplet’s blueprint, it is yours and your responsibility. Opplet provides the design and the documentation, not a warranty of operation. What you run, how you secure it, and how you comply with the laws and obligations of your own jurisdiction is on you. Sovereignty means holding the keys; it also means holding the responsibility that comes with them.

Liability

opplet.com and the opplet blueprint are provided without warranty of any kind. To the fullest extent permitted by law, the project and its contributors are not liable for any damages arising from the use of this site, the blueprint, or any enclave deployed from it.

Governing terms

These terms are governed by the laws of the Commonwealth of Virginia, USA. Any dispute will be handled under that jurisdiction.

This is a draft scaffold in the project’s own voice, not legal advice. The license and jurisdiction must be confirmed by the Board, and the whole document reviewed by qualified counsel, before it is relied upon.