Platform guide
For the team that operates a Saptiva AI installation on its own infrastructure (on-prem). It describes what the platform needs, what the operator receives, and what each party is responsible for; Saptiva AI performs the installation together with the Client's operator.
What each person sees
Members only need HTTPS to four names under the base domain (Requirements). The operator also has access to the dashboard, the alerts, and the image registry.
Who does what
| Activity | Saptiva AI | Client operator |
|---|---|---|
| Provide the cluster, storage, GPUs, network, and certificates | Yes | |
| Preflight check and gap report | Yes | Fixes what is reported |
| Mirror images to the internal registry | Yes | Provides the registry and the space |
| Install and upgrade the platform | Yes | Agrees on the window, runs the prior backup |
| Daily backup and recovery drill | Defines the procedure and runs the drill | Runs and safeguards the backups |
| Handle infrastructure alerts (GPU, storage, certificates) | Supports | Yes |
| Handle platform alerts (component down) | Yes | Escalates |
| Client onboarding, quotas, and menus | Yes | Requests |
| Manage members, SSO, and credentials for each Client | The Client administrator (Administration) |
Chapters
- Requirements: hardware, network, domains, certificates, image registry, and internet egress.
- Installation and Air-gapped installation.
- Upgrade and backup.
- Observability: metrics, dashboards, and alerts that the Client receives.
- Security: isolation between Clients, secrets, retention, and auditing.