Build Apps
AI Cloud lets app teams package runtime experiences without rebuilding platform identity, billing, audit, project context, policy, routing, and lifecycle infrastructure.
Start with App Developer Guide when you need concrete manifest shape, endpoint patterns, readiness checks, and handoff artifacts.
Builder Path
For the first runnable handoff, follow App Developer Guide > Runnable Handoff Path. That path starts from project context and service-account setup, then proves a runtime launch, route/API access, credential rotation or disable, and cleanup.
Runtime Families
| Family | Examples | First proof |
|---|---|---|
| Scheduler apps | Slurm, RKE2, OpenClaw, batch controllers | Job submission, scheduler UI or route, cleanup |
| Compose apps | Container stacks and services | Declared ports, health, logs, route |
| Notebook and IDE apps | Jupyter, VS Code, terminal workspaces | Browser route, workspace persistence, stop/release |
| Inference endpoints | vLLM, OpenAI-compatible APIs, model serving | Model health, endpoint route, auth boundary |
Manifest Responsibilities
An app manifest should describe:
- runtime family;
- launch inputs;
- image or artifact reference;
- required resources;
- health checks;
- ports and routes;
- storage needs;
- connect actions;
- release and cleanup expectations.
Implemented Today Versus Target Direction
| Area | Current public posture |
|---|---|
| Curated app catalog | Available for platform-curated runtimes. |
| Launchable app manifests | Used by curated/reference app paths and SDK fixtures. |
| Third-party self-service manifest registration | Target workflow; use platform-assisted onboarding today. |
| Runtime operation APIs | Available through the product API surface for supported app/runtime operations. |
| App SDK package and validation | Developing around manifest fixtures and contract tests; public self-service workflow will expand over time. |
| Builder handoff flow | Documented through service account, app runtime, route/API, credential lifecycle, and cleanup. |
Platform Contracts
App builders should rely on AI Cloud for:
- tenant and project context;
- user and service-account identity;
- billing and usage attribution;
- policy, quota, and entitlement checks;
- audit and evidence;
- status and lifecycle surfaces;
- route publication where supported.
App builders remain responsible for:
- app image or artifact quality;
- app health semantics;
- app-specific secrets and data handling;
- user-facing runtime behavior;
- compatibility with the selected runtime family.
Promotion Checklist
Before an app is promoted for users:
- Launch works in a clean project.
- Status transitions are understandable.
- Connect action lands on the expected surface.
- Health and logs expose useful failure information.
- Release and cleanup work without manual operator steps.
- Billing, quota, and storage behavior are documented.
- Support can diagnose failures using correlation IDs.
Next
Use App Developer Guide for app packaging and CLI And SDK Guide for auth, idempotency, events, error handling, and integration examples.