Omega Cloud -- Client Intake Form (DRAFT)

Please complete every section and return it through your account contact. We use these answers to build your environment right the first time; missing answers are the most common cause of onboarding delay.

1. Organization

• Organization name: __
• Short name (lowercase, letters/digits/hyphen only -- this becomes the prefix on your cloud accounts and resources, e.g. acme): __

2. Credential custodians (exactly two)

Credentials are handed over out-of-band (never email or ticket text) to the two people named here. Custodian 2 is your recovery path if custodian 1 is unavailable -- account password resets require a request from a named custodian.

3. Authorized requesters

Who may request quota changes, password resets, or other operator actions on your behalf (custodians are included automatically):

4. Capacity request (initial quota)

Quotas can be raised later by request; they are your capacity envelope, not a hard commitment.

5. Network ranges

Private address range(s) you want your cloud networks to use (RFC1918, e.g. 10.x.x.0/24). IMPORTANT: choose ranges that do NOT overlap your on-premises or VPN networks if you ever plan to connect them to this environment.

• Primary range: __
• Additional ranges (optional): __

6. Workload profile

• Kubernetes needed? (yes/no) -- if yes: expected cluster count and node sizing:

  ---

• Expected load balancer count: __
• Storage expectations (databases, backups, large media, etc.):

  ---

7. Optional

• SSH public key to import for your team (otherwise we generate one and hand it to your custodians): __