Anyone can participate
- Self-host the supporting services
- Fork and improve the software
- Build products on the protocol
- Operate a compatible provider
- Compete directly with 1Man
The Daemonet Public Mission · our operating compact
Daemonet exists to make secure, private, self-custodied digital infrastructure available as a public commons. 1Man exists to make that infrastructure easy, reliable, and sustainable—not to turn permission into the product.
This is a public product compact. It states the tests our technology, services, and governance are expected to pass; it does not pretend every institutional safeguard is already complete.
Our mission
The protocols, reference implementations, and core capabilities developed through Daemonet are intended to remain available for anyone to use, study, host, extend, and build upon. Participation should not require commercial permission from Daemonet, Cordine Labs, or 1Man.
People and organizations should retain custody of their identities, keys, relationships, applications, and data. A provider may perform a useful, bounded job without quietly becoming the owner of the entire relationship.
Daemonet makes the technology a public right.
1Man makes that technology easy, reliable, secure, and sustainable.
Open technology · governed trust
Daemonet can steward official branding, compatibility rules, and trusted marks so that insecure, deceptive, or incompatible software cannot casually present itself as an official build.
That stewardship must protect users. It must never become technical permission to implement the protocol, operate compatible infrastructure, sell a competing service, or leave the official provider.
Could another competent company build a fully compatible managed Daemonet service without asking 1Man for technical permission?
The answer must remain yes.The role of 1Man
1Man is Cordine Labs’ optional managed operations and integration service built on Daemonet. It earns revenue by doing difficult work people and organizations may not want to operate themselves: secure deployment, availability, migrations, coordination, monitoring, support, recovery tooling, and accountable service.
A capable user must still be able to produce the underlying result with open Daemonet components. The paid product is professional operation and assurance—not an intentionally crippled commons.
1Man should be influential because it ships useful work, operates reliably, publishes clear standards, funds security, and listens to real deployments—not because it owns a switch that everyone else depends on.
DaemonPay enables commerce
DaemonPay is intended to prove that value changed hands and that a precise right was granted. It does not require Daemonet or 1Man to wedge itself permanently between a buyer and seller.
1Man may charge fixed, subscription, or usage-based fees for infrastructure it actually operates. It does not take a compulsory percentage of the merchant’s transaction. Bitcoin, on-ramp, and other providers may still charge the separate fees a merchant explicitly chooses.
Our commitments
These are release and business constraints, not decoration. When a convenient implementation conflicts with one of them, the implementation needs to change or the conflict needs to be made public.
Daemonet and every managed role remain opt-in.
Users retain control of identities, keys, relationships, applications, and data.
Collect and retain only what a selected technical responsibility requires.
Keep core protocols and reference implementations openly available.
Let anyone build and operate a compatible Daemonet service.
1Man competes through trust, quality, security, reliability, and execution.
Paid development should leave lasting reusable value in the open ecosystem.
DaemonPay imposes no compulsory percentage platform tax.
Neither Daemonet nor 1Man sells user data or private relationships.
Make the promise structural
The compact should survive financial pressure, leadership changes, succession, acquisition pressure, and disagreement. Daemonet and 1Man now publish one AGPL-3.0-only software contract, an additional CC-BY-SA-4.0 documentation license, and an initial provider-neutral trademark and compatibility policy.
Formal governance, conflict procedures, organizational separation, succession planning, independent representation, and certification criteria still need published institutional form. The released licenses make existing public rights durable; this is not a claim that intent has already become an irreversible legal guarantee for every future version or governance decision.
Published open terms let compatible systems exist without private permission.
The initial policy protects official claims without suppressing honest competitors.
Published boundaries between commons stewardship and 1Man’s commercial interests remain required.
A mission designed to outlive any founder, operator, executive, or board.
The public-right test
Read the technical model, inspect the code, or choose managed operation without surrendering the underlying system.