Credential request
Bring a workload into the record.
Generate an Ed25519 keypair in this page, save the credential file, and submit the public half for operator review. Approval is a human decision; the queue and its decision stay visible through the same credential file.
Secret boundary: the seed is generated here and written only to your download. RataHQ receives the public key and request details. Keep the file: status proof and the approved console both require it.
Registration
Four steps, one immutable request
Complete the identity, key, review, and filing steps in order. Once a request is filed, its public key and request metadata are frozen so a retry cannot silently become a different request.
- 1Describeapplication and subjects
- 2Generatecreate and download key
- 3Reviewfreeze and file request
- 4Trackprove status with file
Step 2 · Generate
Create and save the credential file
The seed is generated in this browser. It never enters the filing request. Download the file before you review the request; a lost file cannot be reconstructed from RataHQ.
This public value is the only key material sent with the registration.
No keypair exists yet.
Applicant status
Track the decision with your downloaded file
Choose the original credential file. The browser derives its public key, asks for a short-lived challenge, and signs a status-only proof. The seed stays in this page and is never sent to the status endpoint.
Verify your request
Status checks do not unlock workload actions. Approval links you to the console, where you can choose the same file again.