DaemonetOpen system · Cordine Labs
Daemonet/Licensing

Public licensing contract · effective 16 July 2026

Open code.
Governed trust.

Daemonet and the reusable 1Man implementation are open software. 1Man charges for operating the system well—not for permission to inspect it, self-host it, build on it, or create a compatible provider that competes directly with 1Man.

Daemonet license map 1Man license map

This page is a plain-language map. The included license texts control. It is not a substitute for legal advice about a particular distribution or deployment.

USEpersonal or commercial
HOSTyourself or for others
MODIFYkeep the source open
COMPETEwithout private permission

The software

One copyleft contract for Daemonet and 1Man.

Repository-authored software in both projects is licensed under the GNU Affero General Public License, version 3 only: AGPL-3.0-only. That includes the protocol runtime, clients, tests, public-site implementation, managed control plane, naming and dynamic-DNS code, entitlement services, scripts, container definitions, and reusable deployment automation unless a file carries another notice.

You may use, copy, change, redistribute, sell, self-host, and provide managed service under that license. If you modify the software and let users interact with it over a network, AGPL section 13 requires an offer of Corresponding Source to those users.

THE BUSINESS MODEL

A capable operator can reproduce the technical result with open components. Customers choose 1Man for secure operation, availability, support, accountable work, and earned trust.

People pay for the work—not permission.

Open software is not open custody

Publish the machinery.
Protect the people using it.

The software license does not turn private keys, credentials, user content, customer topology, live databases, deployment secrets, incident material, or operational records into public artifacts merely because open software processes them.

Third-party libraries and imported assets keep their own licenses. Nearby notices control for those materials. The exact AGPL definition of Corresponding Source sets the software boundary.

PUBLISH

Reusable implementation

  • Protocol and record formats
  • Reference clients and hosts
  • 1Man application and service code
  • Dynamic DNS and entitlement machinery
  • Build, test, and reusable deployment tools
PROTECT

Private operational custody

  • User keys, identity, content, and relationships
  • Credentials and live secret material
  • Customer databases and topology
  • Private incident investigations
  • Still-effective sensitive abuse signals

Specifications and public content

Make the mission usable, teachable, and portable.

Repository-authored documentation, specifications, diagrams, and marketing prose are additionally offered under Creative Commons Attribution-ShareAlike 4.0. That makes it practical to quote, translate, teach, and republish the public architecture while preserving attribution and the same freedoms for adaptations.

Executable code and code samples remain AGPL-3.0-only unless their file says otherwise. A released version keeps the rights already granted to its recipients even if a future policy changes.

Trademark and compatibility

Fork the technology.
Do not counterfeit the trust.

Open copyright licenses do not let an independent fork or provider claim to be official Daemonet or 1Man. Truthful phrases such as “compatible with Daemonet,” “built with Daemonet,” and “based on Daemonet” remain welcome.

Modified public distributions should use a distinct primary identity. Official and certified claims require the applicable public criteria and permission. Trademark stewardship cannot be used to block protocol implementation, self-hosting, commercial service, or honest competition.

THE ANTI-CAPTURE RULE

Could another competent company build and sell a compatible managed service without asking 1Man for technical permission?

The answer remains yes.

Inspect the actual terms

The summary is public.
The legal text ships with the source.

Review both implementations, their license maps, and the separate official-brand policy before distributing or operating a modified version.

Read AGPL-3.0-only Trademark policyPublic mission