Private-alpha managed infrastructure
Reach what you own.
Keep owning it.
Daemonet Cloud combines 1Man’s narrow control plane with explicitly selected DaemonGate storage. 1Man coordinates access, names, entitlements, and operations; participating gates hold only client-encrypted, erasure-coded fragments under a separate storage contract.
Invitation-gated private alpha. Capacity appears only while a fresh participating-network aggregate signed by a short-lived telemetry key under the pinned cold Seed’s aggregate-only certificate verifies. The current Daemon Cloud runtime is the shard-storage plane; generic entry routing, automatic Connection-mesh construction, Persona/Hosting/Pocket applications, and managed DaemonChalice recovery remain release-gated.
- 01Browser or native device proves its own key
- 02Owner-signed profile and service policy are verified
- 031Man returns short-lived control records, never object bytes
- 04An opted-in client encrypts and erasure-codes storage locally
- 05DaemonGates receive opaque fragments within explicit grants
1Man.dataPath = control · DaemonGate.dataPath = opaque fragments
FREEby default
KEYinstead of password identity
SHORTpasses and endpoint leases
DIRECTordinary application path
Cold-Seed-certified network aggregate
Capacity that fails closed.
The marketing server accepts one identifier-free exact aggregate only after its telemetry signature, pinned cold-Seed aggregate-only certificate, digest chain, freshness, and byte conservation verify. Individual Gate names, addresses, onions, shard locations, customers, and topology are not published.
Telemetry unavailableNo fresh verified measurementThe dashboard never substitutes zero for an unavailable feed.
What “live shard occupancy” means: actual filesystem blocks allocated to live encrypted erasure fragments and their authenticated records—not recoverable customer plaintext and not a guessed logical file size. Durable deletion markers are excluded from this counter but still reduce distributable capacity. Totals and counts are exact above the publication floor, not coarsened; comparing snapshots may reveal infrastructure changes. Backup, Persona, Hosting, Pocket Dimension, and any accounted Chalice allocations remain combined. The aggregate exposes no Chalice mode, unlock, key-share, placement, or per-object recovery state; network capacity is not proof that an individual Chalice is recoverable.
The managed control plane
1Man operates the introduction—not the relationship.
Use 1Man to attach infrastructure, enroll devices, prove names, obtain certificates, coordinate reachability, integrate entitlements, observe availability, and support migrations. It cannot approve your device, rewrite your profile, recover your identity, or receive object plaintext. DaemonGate fragment custody is a separate, explicit storage role—not an expansion of 1Man authority.
Universal enrollment
One-time encrypted ceremonies connect a fresh browser or thin client to an approval made by a device that already holds your authority.
Names and services
Portable Domain Deeds and owner-signed service manifests bind names, TLS keys, modes, policy, and replaceable endpoints.
Opaque shard custody
Participating DaemonGates accept only authorized encrypted fragments. Client-side encryption and erasure thresholds keep a single admitted gate below object reconstruction.
Native service authorization
Lock one app to the exact people and time you choose.
The access policy is embedded in the service owner’s signed manifest. 1Man can display and integrate it, but only a key explicitly named by the owner can issue the destination-verifiable pass.
First decides whether these members may communicate at all.
Then requires an allowlisted principal, a portable entitlement, or a timed trial.
Opens only the exact service port and DNS answer until the signed expiry.
WireGuard and origin HTTPS carry the application data without 1Man.
Named access
Authorize an exact profile member or Daemonet user from a start time through a hard expiry.
Portable entitlement
Accept an owner-selected issuer, resource, audience, and right. Finite uses are allocated atomically at the destination.
Timed trials
Offer X starts of Y minutes, or unlimited starts. Each accepted start receives a new bounded pass; counters survive retries.
Stable names, explicit surfaces
Domains describe responsibility.
Public marketing, managed control, developer infrastructure, explicit hub publication, and private profile DNS are different products and trust paths. A wildcard does not make them interchangeable.
daemonet.comcompany and open-source productdaemonet.cloudmanaged customer access and 1Man operationsadmin.daemonet.cloudcustomer browser portal; device-key enrollment is still requireddaemonet.iodeveloper docs, protocols, SDKs, and releaseshub.daemonet.ioexplicitly published ingress only; DaemonHub remains a candidate nameprivate.profile.daemonetprofile-owned private DNS; not a public Cloud account nameSchema-owner and invitation-administration tools are never served by the public portal. Verified public service publication still requires a portable Domain Deed backed by three independent DaemonGate witnesses. A one-gate pre-alpha may test coordination, but it cannot mint that proof.
Explicit custody boundaries
The managed roles stay narrow on purpose.
1Man is the control plane. Daemon Hub may carry traffic only for an owner-published service. Daemon Cloud storage may carry opaque fragments only after an explicit storage grant. Neither role is a quiet fallback for private access.
No cloud identity takeover
A portal session or conventional administrative record never becomes the user’s Daemonet identity.
No topology warehouse
Public capacity omits identifiers but reports exact above-floor totals and infrastructure counts. Consecutive deltas may reveal joins, departures, or capacity changes.
No 1Man document path
1Man does not receive object bytes. An opted-in DaemonGate stores only opaque encrypted fragments and is never assigned enough fragments to meet the reconstruction threshold.
No payment custody
A receive-only watcher observes settlement to the operator wallet and cannot sign, sweep, spend, or refund.
No privacy upsell
Paid capabilities buy managed operations and capacity—not a less exploitative privacy tier.
No quiet downgrade
If identity, entitlement, route, certificate, storage threshold, or transport proof fails, the operation stops visibly.