Terms of Service — Hostether

Last Updated: April 23, 2026

Welcome to Hostether. By accessing or using our sovereign infrastructure services, you agree to be bound by these Terms of Service, which incorporate the Sovereign Commerce Canon (ORC-SPEC-2026-031) by reference.

1. The Sovereign Relationship

Hostether does not “rent” space to you as a tenant. We provide the cryptographic and physical substrate for you to materialize your own Hosting Account (𝓗). You are the root administrator of your materialization.

2. The 90/10 Doctrine

• Open Component (90%): The software stack utilized (including but not limited to Coolify, Zitadel, and Caddy) is licensed under their respective open-source licenses (Apache 2.0, MIT, AGPL-3.0).
• Proprietary Reserve (10%): The underlying hardware-attested entropy streams, the Certified Entropic Record (CER) generation secrets, and the specific mesh orchestration logic are proprietary assets held in trust by the Lubimiv Family Trust.

3. Thermodynamic Constraints

Usage of the service is bound by the Landauer Floor Invariant. Any attempt to manipulate the reported energy dissipation or forge Certified Entropic Records will result in the immediate nullification of your authority vectors ($V \to 0$).

4. Ledgric Unity

All billing is reconciled through the PaiID.Cc ledger. You agree that your Hosting Account is anchored to a unique primitive_id which serves as the authoritative record of your commercial existence within the ecosystem.

Privacy Policy — Hostether

1. Identity-First Privacy

Hostether is built on the AuthO.iD framework. We do not “collect” your data; we provide a vault where you store your own data.

2. No Data Arbitrage

Hostether will never sell, trade, or monetize your usage patterns. Our revenue is derived strictly from the materialization of your Hosting Account.

3. Certified Entropic Records (CERs)

Metadata regarding your resource consumption is recorded as a CER. These records are used for billing reconciliation and thermodynamic auditing. CERs are cryptographically hashed and anchored to your primitive_id.