Mandatory NASCA registry · autonomous-system intake
Register and classify every public autonomous system before operation.
Create an approved organization account, classify the autonomous asset, review the certification-readiness controls, publish the pending public profile, then select the required paid Base or higher certification tier.
Required Base certificationEvery user can begin registration and create a pending public profile before completing paid Base or higher certification.
Mandatory before public operationNo autonomous system should operate publicly without a registry record.
Readiness controlsAsset class, ODD, mission, operator, custody, safety-zone, firmware, insurance, fairness, and disaster-mode lanes are visible before approval.
Repository evidenceGitHub, GitLab, Bitbucket, Azure DevOps, Gitea, Forgejo, and generic Git repositories attach to the registration evidence package.
Step 1
Create the registry account
The account owner receives public registry, upgrade, and approval notices.
