1Man/Early access

Invitation-gated private alpha

Join without telling us who you are.

Your browser creates a recovery identity locally. 1Man stores only its public keys, an opaque claim identifier, status, and an optional DaemonChat name. Keep the phrase and return to check whether access was granted.

We cannot email you because we never ask who you are. We cannot reset the recovery phrase either.

Anonymous launch registry

Claim a place without creating a conventional account.

Your browser creates signing and encryption keys. 1Man receives only their public halves and an optional DaemonChat name. Return with the phrase to check pending, approved, or declined status.

Checking launch policy…Registration and payment gates fail closed until verified.
01

Create an anonymous claim

Choose an optional DaemonChat name, then let this browser generate the identity.

WHAT 1MAN RECEIVESPublic keys, opaque claim ID, status, and optional nameNo email, phone number, password, or recovery phrase.

What private alpha is for

One real user. Several hostile real-world workflows.

The first invitation is meant to test the entire lifecycle on the founder’s own Arch Linux and Ubuntu infrastructure—not manufacture a signup number. Every connection records the selected mode and the reason for any failure.

NETWORKS

Change the path

Ethernet, Wi-Fi, separate LANs, phone hotspot, suspend, resume, router restart, and endpoint restart.

REMOTE DESKTOP

Use Remmina

Measure input responsiveness, clipboard, resolution changes, reconnect, and long-running session behavior.

STREAMING

Stream a game

Measure latency, jitter, packet loss, and whether the final route is genuinely direct.

STORAGE

Mount a network drive

Browse directories, transfer large files, interrupt the route, resume safely, and remount.

CONTROL OUTAGE

Remove the portal

After introduction, stop 1Man and prove established endpoint relationships do not acquire a central application fallback.

REVOCATION

Kill access

Revoke the device and demonstrate that prior invitation possession cannot restore its authority.

Economic proof

Record bytes handled by coordination separately from bytes transferred directly. A large streaming or file session must not become a matching 1Man bandwidth bill unless an explicit relay product was selected.

Invitation lifecycle

The token opens enrollment. It never becomes identity.

A single-use, hashed-at-rest, expiring invitation authorizes one enrollment attempt. The joining device generates its own credential, obtains owner approval, and reconnects with that credential. The bearer token can then be discarded or revoked.

Receive a grant

Return with the recovery phrase and decrypt the invitation locally if the claim was approved.

Generate device keys

The joining device creates its permanent key material and never uploads the private half.

Obtain owner approval

An existing Daemonet authority approves the exact new key and its bounded permissions.

Discard the token

Future sessions authenticate with device authority. The handwritten token has no continuing access power.

Keep the recovery phrase

We cannot contact you, reset it, or recognize you without it.