Runbooks
Operational runbooks for ScaiLabs partners and operators.
Product documentation tells you what a single product does. Runbooks cover procedures that span several products end to end — the sequences you follow to get real work done across the platform, in the order that actually works.
Available runbooks#
| Runbook | Audience | What it covers |
|---|---|---|
| Provisioning a New Tenant (ScaiKey → ScaiGrid) | Partners: resellers, MSPs, ISPs | Onboarding an end customer: tenant and first Tenant Admin in ScaiKey, matching tenant in ScaiGrid, model entitlement and a scoped API key |
Conventions used here#
- Every runbook states its audience and outcome at the top.
- Shell variables (
$SCAIKEY,$TENANT_ID, …) are defined in each runbook's Conventions section — set them once and the commands are copy-pasteable. - Steps are ordered by dependency. Where order matters for a non-obvious reason, the runbook says why.
- Each runbook ends with rollback and deprovisioning, so a procedure you start can always be safely undone.