Skip to main content

AI Cloud Docs

AI Cloud gives teams one place to launch GPU-backed compute, application runtimes, developer workspaces, and inference endpoints. The product keeps tenant, project, access, billing, security, and runtime lifecycle behavior consistent across those surfaces.

This public portal is for users, tenant administrators, app builders, and API consumers. Engineering design, security evidence, deployment runbooks, and internal implementation details live in the protected engineering portal.

Five Documentation Paths

PathUse it for
LearnProduct model, capabilities, hierarchy, roles, onboarding, and user journeys.
Use AI CloudTask procedures for account security, compute, apps, storage, cost, connection, and cleanup.
AdministerProjects, members, service accounts, quota, spend, access review, and team handoff.
Build and AutomateApp packaging, CLI login, SDK/API authentication, project context, retries, and compatibility.
Reference and SupportCapability/runtime reference, troubleshooting, errors, evidence packet, and escalation ownership.

Start With Your Goal

I want to...Go to
Understand the basic product modelStart Here
See what the platform already supportsPlatform Capabilities
Follow a complete task-based user guideAI Cloud User Guide
Complete a first launch walkthroughQuickstart
Learn the tenant, project, runtime, and access modelConcepts
Understand hierarchy, ownership, and rolesResource Hierarchy And Roles
Sign in and prepare my accountUser Onboarding
Launch direct compute capacityLaunch Compute
Launch compute, apps, notebooks, or endpointsLaunch And Operate
Administer projects, members, service accounts, and spendTenant Administration
Package an app for AI CloudApp Developer Guide
Automate with CLI, SDKs, or APIsCLI And SDK Guide
Recover from a blocked stateTroubleshooting Playbook

Product Model

AI Cloud is organized around a few concepts that appear throughout the UI, CLI, and API.

ConceptMeaning
TenantA customer or organizational workspace.
ProjectA scoped place to run workloads, assign members, and attribute usage.
RuntimeA launched compute node, app, notebook, scheduler, or endpoint.
AppA packaged runtime experience that users can launch repeatedly.
AccessMembership, roles, SSH keys, API keys, service accounts, and sessions.
BillingBalance, entitlement, hourly burn, usage, and release cleanup posture.

Self-Service Readiness

The public guide is intended to answer four questions without an internal operator beside the reader:

  1. Where am I in the tenant/project/resource hierarchy?
  2. What role do I need for this action?
  3. What exact user or developer path should I follow?
  4. What evidence should I collect if the path is blocked?

What You Can Do

  • Launch GPU compute and app runtimes from a project.
  • Connect through the supported runtime surface: SSH, terminal, notebook, IDE, scheduler UI, application route, or API endpoint.
  • Manage your account security, keys, sessions, and project access.
  • Package apps so other users can launch a repeatable experience.
  • Automate workflows through the CLI, SDKs, and REST API contracts.

Main Walkthroughs

WalkthroughWhat it proves
AI Cloud User GuideFirst-day setup, account access, launch, connect, monitor, release, CLI, SDK, and troubleshooting.
Platform CapabilitiesUI, CLI, SDK, API, service-account, app, billing, storage, and support capability inventory.
QuickstartSign in, verify context, prepare account access, launch, connect, and release.
Resource Hierarchy And RolesTenant, project, billing group, resource ownership, roles, and access posture.
Launch ComputeDirect compute lifecycle from launch inputs to cleanup.
App Developer GuideRuntime-family choice, manifest shape, endpoints, readiness, and handoff.
CLI And SDK GuideConcrete CLI commands, REST examples, idempotency, and error handling.
Troubleshooting PlaybookBasic blocker matrix, owner routing, API errors, and escalation packets.

Before You Start

You need an AI Cloud account, access to a tenant, and at least one project. If the expected tenant or project is missing after sign-in, ask your tenant admin to confirm your membership and project role before launching work.

Public Documentation Scope

This site intentionally focuses on product usage and integration. It does not publish deployment runbooks, provider operations, internal security evidence, or implementation design details.