Docs / Getting Started / Account Initialization and Identity Verification

Account Initialization and Identity Verification

Published · Last updated: May 2026 · 2 min read

Architecture Overview

Welcome to CloudAIPilot. Establishing your operational identity is the first step toward autonomous cloud orchestration. Because CloudAIPilot acts as an active control plane with deep execution capabilities across your infrastructure, we enforce strict identity verification, enterprise-grade session management, and advanced security protocols to protect your access at the perimeter.

Prerequisites for Orchestration

Before provisioning your control plane access, ensure you have:

  • A valid email address capable of receiving automated verification payloads.
  • (Optional) An active Google or GitHub account for federated Single Sign-On (SSO).

Registration Workflows

You can initialize your account via standard credential registration or federated identity providers.

Method A: Standard Credential Registration

  1. Navigate to the CloudAIPilot Registration Portal.
  2. Input your basic identity parameters (e.g., First Name, Last Name, and Email Address).
  3. Establish a secure Password. For cryptographic safety, the system enforces a strict minimum of 8 characters.
  4. Select Create account.
  5. CloudAIPilot will dispatch a secure verification payload to your inbox. Locate the email and follow the embedded link to verify your identity vector.
  6. Upon successful verification, you will be routed to the primary authentication gateway to establish your initial session.

Method B: Federated Identity (Google or GitHub SSO)

For accelerated onboarding, you may leverage an existing identity provider.

  1. On the registration portal, select Continue with Google or Continue with GitHub.
  2. Authenticate through the provider's secure OAuth flow.
  3. Your identity is automatically verified, bypassing the email payload requirement. Your CloudAIPilot session is initialized instantaneously.

Post-Quantum Cryptography (PQC) & Session Boundaries

CloudAIPilot is architected with Post-Quantum Cryptography (PQC) standards to protect your cloud infrastructure. Your Cloud Provider Access Tokens, database connection strings, and orchestration payloads are entirely quantum-safe.

However, note the technical boundary regarding your browser authentication session: modern web browsers restrict authentication cookies to a maximum size of 4 KB, which is currently insufficient for the large key sizes required by PQC algorithms. Therefore, your active login session utilizes industry-standard, high-entropy hashing (bcrypt/Argon2id) alongside short-lived, rotating secure tokens.

Troubleshooting Identity Verification

  • Symptom: The verification payload did not arrive in your inbox.

Resolution: Inspect your spam or promotional filtering rules. If the payload is unrecoverable after 5 minutes, return to the authentication gateway and request a new verification token.

  • Symptom: The verification link returns an expiration error.

Resolution: For operational security, verification links expire automatically after 24 hours. Attempt to authenticate with your unverified credentials to trigger the generation of a fresh verification payload.

Next Steps