Connect + Rendezvous
Help approved devices find one another, then return a signed route so the endpoints can establish their own Daemonet connection.
CONTROL PLANE · NO ORDINARY PAYLOADTemporary coordination is not topology custody.1Man Products
Managed plumbing with explicit authority.
Choose the operational services you need around Daemonet. Every product states whether it coordinates control information, carries bytes, preserves encrypted capacity, or verifies authority.
Working product journeys
Try one complete job at a time.
These are the public workflows available in the current build. Repository primitives and planned services stay out of the customer UI until they have a complete entry, proof, failure, and exit path.
LIVE · FREEStart a direct peer roomCreate or join, acknowledge the direct-peer boundary, then use chat, calls, files, or local tools as separate room tasks.→
PRIVATE ALPHACreate or check a claimGenerate an anonymous recovery identity, save it, and return later without a contact account.→
OWNER APPROVAL REQUIREDConnect this browserCreate a local key, approve the exact request in Daemonet, then install the returned browser card.→
PUBLIC EVIDENCEInspect Network UnlocksFind a feature, open its weakest gate, and see exactly what demand, support, capacity, trust, or readiness is missing.→
Access
Issue short-lived, device-bound proof for one service, action, approval, trial, or entitlement. The destination still applies its own policy.
PROOF · EXPIRY · REVOCATIONNo operator password can impersonate customer authority.Private DNS + verified names
Coordinate domain evidence, signed name authority, certificate operations, and origin-shielded routes without making DNS pretend to be transport.
WITNESS + PUBLICATION OPERATIONSThree independent witnesses remain a release gate.Entitlements
Verify access to builds, applications, files, streams, communities, APIs, and trials while the seller keeps the product relationship.
PORTABLE ACCESS EVIDENCEPayment observation remains separate from authorization.Relay bandwidth
Carry traffic only when direct communication is impossible, deliberately avoided, or insufficiently reliable—and only after the route is selected.
EXPLICIT BYTE-CARRYING ROLEDirect failure does not silently create a relay bill.Storage + recovery
Provide encrypted shards, availability, replication coordination, integrity checks, and recovery fragments without requiring plaintext.
EXPLICIT ENCRYPTED CAPACITYCustomers retain reconstruction and placement authority.Revocable capability links and resumable transfer, direct first.
Pairing, rotation, approval, and recovery around customer-held keys.
Authenticated event delivery without acquiring application state.
Scoped routes and machines that join a Daemonet rather than own it.
Finite recurring rights without a compulsory transaction percentage.
Credits for independently measured useful capacity after abuse controls exist.
Route contract
Rendezvous is not relay.
Relay is not Hub publication. Hub publication is not anonymous public hosting. DNS is not transport. An entitlement does not choose a route. Each byte-carrying mode must be selected, authorized, priced, and disclosed independently.
Ordinary path
1Man may authenticate, resolve, validate entitlement, and return a signed endpoint record. The client then connects to the customer host, which terminates HTTPS and serves the application.
Start with one managed burden