Internal Team Onboarding designed
Use this page when a team needs to understand GPUaaS without reading the raw GitHub documentation tree. Each path starts with the portal pages that explain the product in plain language, then routes to deeper technical or governance content.
What Internal Teams Should Understand Early
GPUaaS is not only a product team surface. It is also:
- a shared-platform foundation for later products;
- an IAM and billing model with explicit organization, department, and project semantics;
- a runtime-access platform with separate terminal, browser, API, and operator surfaces;
- an evidence-driven release and operations model.
If a team reads this portal and still thinks GPUaaS is only “rent a GPU and SSH into it,” the onboarding path is too shallow.
Common Starting Point
Everyone should read these first:
Use Start Here when the reader's role is unclear. Use this page when the audience is known and the goal is team onboarding.
Persona Routes
| Persona | First-read path | Decision points | Next-action pages |
|---|---|---|---|
| Product stakeholder | Product Team Handoff, Product Strategy, Competitive Context | Product scope, buyer/user fit, current maturity, launch path, active queue, and roadmap pressure | Journeys and v3 IA, Portal Roadmap, External Product Path |
| Architecture reviewer | Architecture, System Overview, Platform Foundation | Runtime topology, ownership boundaries, shared-service direction, and v3 route migration | Domain Ownership, API Domain Authoring, Shared Services |
| Security reviewer | Security & Production Readiness, Current Controls, Release Evidence | Implemented controls, production gaps, evidence expectations, and publication risk | Security Controls, Gaps Roadmap, External Security Path |
| Platform operator | Operations Team Guide, Operators, Day-2 Operations | Release, incident, node, observability, billing, or evidence workflow | Release Operations, Incident Workflow, Billing Diagnostics |
| App developer | Build on GPUaaS, App Developer Onboarding, Developer APIs | App boundary, credentials, manifest, runtime lifecycle, promotion, and API contract needs | Quickstart, Manifest Model, SDK Evidence Path |
| Internal developer | Developer Team Guide, Developer Implementation Map, Developer APIs | Contracts, architecture, app boundary, route ownership, state/sequence/data model expectations | Build on GPUaaS, Governance & Agents |
| IAM / Identity | IAM and Identity Team Guide, Shared Platform Builders, Security & Production Readiness | Federation boundary, platform IAM ownership, MFA posture, scope/service-account model | Developer API Auth, Architecture Review Pack |
| Infra / Environment owner | Infrastructure and Environment Guide, Operators, Security & Production Readiness | Environment profiles, deploy/readiness posture, DNS/TLS, edge naming, and production-like baselines | Production Baseline, Release Operations |
| IAM / Infra / Token-factory builder | Shared Platform Builders, Platform Foundation, Product Onboarding | How another platform/service/product should reuse shared services instead of reimplementing them | Shared Services, Production Baseline, Developer API Auth |
| Agent/coordinator | Governance & Agents, Evidence-First Execution, Change Control | Claim scope, source authority, review route, evidence packet, and completion gate | Governance Model, Portal Source Of Truth, Discovery Index |
Reader Map
Team Paths
| Team | Start here | What they should understand |
|---|---|---|
| Product | Product Team Handoff, Current State and Roadmap, Competitive Context | Product scope, personas, launch and billing journeys, implemented state, active queue, market positioning, and roadmap pressure |
| Architecture | Architecture Review Pack, System Overview, Platform Foundation | Control-plane shape, domain ownership, shared services, maps/guards/facades sequence, and open decisions |
| Development | Developer Team Guide, Developer APIs, System Overview | Contract-first implementation, API/event rules, error/idempotency model, code boundaries, and Definition of Done expectations |
| CISO / Security | Security & Production Readiness, Current Controls, Release Evidence | Current security controls, production gaps, release evidence, policy posture, and where operating separation still needs enforcement |
| Operations | Operations Team Guide, Operators, Day-2 Operations | How releases, incidents, node fleet, billing, terminal access, evidence, and runbooks are managed |
| Infrastructure | Infrastructure and Environment Guide, Day-2 Operations, Release Operations | Required platform controls, reserve capacity, WAF/TLS/secrets/certs, observability, backup/restore, and rollout rings |
| IAM / Token factory / shared-platform builders | IAM and Identity Team Guide, Shared Platform Builders, Platform Foundation | How shared identity, onboarding, policy, evidence, and environment contracts should be reused across products and teams |
| App developers | Build on GPUaaS, App SDK Overview, SDK Evidence Path, Developer APIs | App boundary, manifest model, SDK workflow, auth/access, artifact trust, promotion, API contracts, and evidence expectations |
| Governance / agent coordinators | Governance & Agents, Governance Model, Evidence-First Execution | How work is queued, reviewed, evidenced, guarded, and promoted |
Remaining Team-Path Work
| Work area | Current route | Follow-up task |
|---|---|---|
| Current source refresh | This page links the current section routes; detailed updates happen in the owning section pages | DOCS-PORTAL-CURRENT-CONTENT-REFRESH-001 |
| Visual walkthroughs | Reader map is Mermaid; richer workflow diagrams belong in page-specific sections | DOCS-PORTAL-DIAGRAMS-FLOWS-001 |
| Publication split | This page remains internal until filtered publication tracks exist | DOCS-PORTAL-PUBLICATION-TRACKS-001 |
What The Portal Should Answer
| Question | Portal answer |
|---|---|
| What is GPUaaS? | Platform Overview |
| What have we built? | Platform Overview, Product Strategy |
| What is implemented now and what is next? | Current State and Roadmap |
| How does it work technically? | System Overview |
| What should ARB/JAD reviewers read? | Architecture Review Pack |
| How does a user interact with it? | User Interactions |
| How do operators run it? | Day-2 Operations |
| What is the security/readiness posture? | Security & Production Readiness |
| How do developers build on it? | Build on GPUaaS |
| How do internal developers ship against it? | Developer Team Guide |
| How should IAM, security, infra, and ops teams engage with it? | IAM and Identity Team Guide, Security and CISO Team Guide, Infrastructure and Environment Guide, Operations Team Guide |
| How does the team govern changes? | Governance Model |
| How do we compare to adjacent products? | Competitive Context |