What GPUaaS Already Proves as a Platform implemented
This page exists because the portal can otherwise make GPUaaS look smaller than it is. The repo already proves more than "users can launch GPUs."
It proves a reusable AI platform foundation that other products can build on.
The Core Claim
GPUaaS is the first product on a shared platform with reusable authority for:
- IAM and scoped authorization;
- billing, metering, and immutable financial custody;
- audit and release/UAT/security evidence;
- registry and onboarding contracts for later products;
- repeatable runtime-access surfaces;
- repeatable promotion across environment profiles.
Platform Strengths
| Strength | What already exists | Why it matters |
|---|---|---|
| Shared-platform split | explicit shared / platform / products layer model | future products do not have to fork core services |
| App SDK proof | shipped Slurm and RKE2 reference controllers on the platform path | proves the composition model with working controllers, not only a manifest story |
| Hierarchical IAM | organization, department, project, principal, resource model | authz and billing attribution stay coherent |
| Runtime surface model | terminal, browser app, API app, metrics, operator tools | access is modeled intentionally instead of bolted on |
| Immutable money path | metered usage -> rating -> ledger -> derived balance | financial correctness is defendable |
| Evidence-first release posture | release, UAT, security, rollback, and runtime proof models | promotion can be justified by evidence, not memory |
| Config-driven deployment ladder | kind -> dev -> demo -> staging -> prod model | production is a profile, not a hand-built exception |
| Enforced architecture guards | boundary reports and CI gate modes protect the layer split | platform architecture is executable, not only documented |
Why This Is Different From A Typical Internal Control Plane
The important point is not just that these capabilities exist. It is that they exist as reusable boundaries, not product-local tricks.
What Product, Security, And Ops Can Reliably Say Today
| Audience | Strong claim the portal should support |
|---|---|
| Product | GPUaaS is proving the platform model that later products will reuse |
| Architecture | the repo already separates technical primitives, platform authority, and product semantics |
| Security | audit, evidence, immutable billing, and promotion custody are first-class concerns |
| Operations | environment promotion and runtime access are modeled as repeatable operating surfaces |
Where To Go Next
| If you want to see... | Open this |
|---|---|
| shipped evidence and hard proof | Platform Proof Points |
| platform/product split | Platform Shared Services |
| code/package ownership | Code Structure And Layer Model |
| runtime surface families | Workload Access and Runtime Surfaces |
| hierarchy and scoped authority | Tenant, Department, Project, And Resource Hierarchy |
| promotion and production shape | Production Deployment Model |
| second-product coding surface | Platform Contracts for Builders |
Canonical sources