Segal Instances
GPU compute with a defined machine shape, operating-system image and private network.
Engineering-led activation. Production access depends on an authorized provider account, a customer-specific service binding and confirmed availability.
How the service fits.
Regional flavors, images, SSH keys and instance lifecycle. Stock and quota are checked in the bound customer project.
- 1
Select a regional GPU flavor and compatible image
- 2
Launch into the customer’s isolated cloud project
- 3
Track provider-reported state before exposing a usable machine
Service architecture
- GPU count and memory come from the selected flavor
- SSH access is bound to an approved public key
- Persistent data lives on explicitly attached storage
Operating boundaries
- GPU availability and quota are regional
- Stopping a VM does not imply that every attached resource stops billing
- GPU telemetry requires an installed agent; it is not inferred from uptime
Deployment & support
Segal provides the branded service experience and coordinates configuration, support and commercial scope. The infrastructure service is supplied through OVHcloud; provider eligibility and applicable service terms must be confirmed before activation.
Upstream service: Public Cloud GPU instances. Provider specifications were reviewed on 24 October 2026; actual inventory and quota are checked separately.
Upstream technical reference