Getting Started

Create an Account

Preparation steps for organizations, access setup, and account provisioning.

Coming Soon

Development Preview

Public StrataGateway account registration is not yet generally available. The onboarding system is being developed alongside the StrataGateway platform. Account provisioning, email verification, organization creation, billing setup, and API credential issuance will be documented here once publicly available.

Jump to article

Overview

A StrataGateway account is the top‑level container for identity, access control, billing, and ownership of infrastructure resources. It provides a single point of control for all platform services — compute, networking, storage, security, and developer tooling.

Public StrataGateway account registration is not yet generally available. This documentation describes the intended onboarding and account‑setup model so developers can understand what to expect as access becomes available.

Availability

Public self‑service account registration is Coming Soon. The onboarding system is being prepared alongside the StrataGateway platform. No production accounts can be created today.

Development Preview

The onboarding system is being developed alongside the StrataGateway platform. Account provisioning, email verification, organization creation, billing setup, and API credential issuance are not yet publicly available.

No wait‑list numbers, launch dates, or beta invitations are published at this time.

Before You Begin

When registration opens, have the following ready:

  • A valid email address you control
  • Your legal name or organization name
  • A secure password you have not used elsewhere
  • Access to the email inbox for verification

Additional compliance or KYC steps may be required for certain organization types; details will be published before general availability.

Account Model

The intended account hierarchy separates identity, billing, and resource grouping:

User

Human identity; authenticates via email/SSO and owns credentials.

Organization

Billing and ownership boundary; groups projects and manages billing.

Project

Logical grouping of resources (instances, networks, volumes).

The exact hierarchy is still being finalized; the documentation will be updated before general availability.

Registration Flow

The intended self‑service onboarding sequence:

  1. 1

    Step 1: Start registration on the StrataGateway website

  2. 2

    Step 2: Enter email, name, and organization name

  3. 3

    Step 3: Verify email address via a one‑time link

  4. 4

    Step 4: Create organization (or select existing) and set billing details

  5. 5

    Step 5: Configure account security (password, future MFA, recovery options)

  6. 6

    Step 6: Receive API credentials and access the control plane

  7. 7

    Step 7: Proceed to first infrastructure workflow (e.g., Quick Start)

The flow above is planned. No public registration endpoint exists today.

Email and Identity

The primary email address is the root of account identity. It is used for:

  • Account creation and email verification
  • Security notifications (login alerts, credential changes)
  • Billing and invoice delivery
  • Service status and incident notifications
  • Account recovery and password reset

Email verification will be required before the account becomes active. Verification links expire after a short period for security.

Organizations and Ownership

An organization groups projects, centralizes billing, and defines the trust boundary for team collaboration. The account owner is the initial organization administrator.

Only the organization owner can manage billing and invite/remove members.
Projects belong to an organization; resources inherit the organization's policies.
Ownership transfer and organization deletion will be supported before GA.
Multiple organizations per user are planned for agency / multi‑tenant scenarios.

Account Security

Planned security controls for account protection:

Multi‑factor authentication (MFA)

Planned

TOTP, WebAuthn, recovery codes

Password policy

Planned

Minimum length, breach check, rotation reminders

Session management

Planned

Device list, revocation, inactivity timeout

API token scopes

Planned

Granular scopes, expiration, rotation

Audit log

Planned

Immutable log of security‑relevant actions

Recovery options

Planned

Backup codes, secondary email, admin recovery

Billing Preparation

Account creation and billing are related but distinct. Billing profiles will be attached to organizations after account creation.

No payment method is required to create an account (Coming Soon).
Billing profiles support credit cards and invoiced billing (Planned).
Usage is metered per‑resource; invoices are generated monthly (Planned).
Budgets, alerts, and cost allocation tags are planned for future releases.

Team Access

Team collaboration features are under design. The following concepts are being evaluated:

  • Invite members by email; assign roles per project or organization.
  • Role‑based access control (RBAC) with least‑privilege defaults.
  • Audit trail of membership changes.
  • Service accounts for CI/CD pipelines.

Team and role management details remain under development. The model will be finalized before general availability.

First Login

When the platform becomes available, the first sign‑in will guide you through:

  1. 1

    Account overview dashboard – resource summary, billing snapshot, health status

  2. 2

    Onboarding checklist – security setup, first project creation, SSH key upload

  3. 3

    Quick Start link – deploy your first compute instance

  4. 4

    Security center – MFA enrollment, API token creation, SSH key upload

Account Lifecycle

Accounts progress through a defined lifecycle:

Lifecycle

Lifecycletext
Created
→ Email verification
→ Active (organization ready)
→ Active + billing attached
→ Suspended (policy violation / non‑payment)
→ Closed (data retention window)
→ Deleted

Exact retention periods and suspension policies will be published before GA.

Security Recommendations

Independent of platform features, follow these practices:

  • Use a unique, high‑entropy password (or a password manager)
  • Enable multi‑factor authentication as soon as it becomes available
  • Store API tokens and SSH keys in a secret manager, never in source control
  • Rotate credentials periodically and revoke unused tokens
  • Limit team invitations to the minimum required roles
  • Regularly audit API keys and SSH keys

Current Limitations

The following capabilities are not yet available:

  • Public self‑service account registration
  • Production‑grade billing and invoicing
  • Multi‑factor authentication enforcement
  • Organization/team RBAC
  • API token management UI
  • Custom domain / SSO integration
  • Data residency / region selection at account level

Documentation reflects the intended design direction; actual availability will be announced via the Changelog andService Status pages.

Was this page helpful?