Machine Authorization
See all 5 articles in Machine Authorization →
Machine authorization covers the credential and admission mechanisms that gate who and what can act on the platform — pairing a device onto the WireGuard mesh, issuing and rotating the Ed25519 capability tokens services use to authenticate to each other, enrolling a compute node into a fleet, and authenticating a signed binary download. These are genuinely separate mechanisms, not one system under different names; each guide states plainly where its own mechanism's real limits are, including where no revocation or un-pairing command exists today.
Pairing and tokens
3 articles- Pair a new device
Pairs an unpaired os-console device onto the PPN mesh: read the pairing code from the startup screen, have an administrator approve it, and confirm network admission.
- Issue a capability token
Issues an Ed25519-signed pairing token from service-content over plain HTTP, registers it with the receiving peer, and covers the separate X-Foundry-Capability request header.
- Rotate keys and capability tokens
Replaces a service-content credential within the real system's limits: tokens expire on a fixed 24-hour clock, overlap is unavoidable, and no mechanism cuts a live token short.
Fleet enrollment
1 article- Enroll a PPN node
Enrolls a machine into a PPN compute fleet by setting service-vm-host's three required environment variables, running it under systemd, and confirming the node in the controller listing.
Software distribution
1 article- Authenticate binary downloads
Authenticates a release from software.pointsav.com: confirm the on-chain order, follow the download link that mints an Ed25519 token, and understand where verification actually happens.
Each guide carries its own prerequisites, verification steps, and rollback procedure; this page doesn't repeat them. Day-to-day operation of a running deployment is in Platform Tasks.
See also
- Platform Tasks — the remaining day-to-day operational guides
- Security and Trust — the identity and permissions model these mechanisms participate in
- Self-Hosting — deploying the appliances these credentials authenticate against