Segal Buckets
Store datasets, model artifacts, checkpoints and application objects using an S3-compatible interface.
Engineering-led activation. Production access depends on an authorized provider account, a customer-specific service binding and confirmed availability.
How the service fits.
Regional bucket management and S3 data access. Object data access requires separately scoped storage credentials.
- 1
Create storage in the required region
- 2
Issue scoped credentials for the application
- 3
Apply lifecycle, retention and access policies
Service architecture
- Object names and permissions are independent of compute instances
- Applications use the endpoint and signing region supplied for the bucket
- Public access is an explicit configuration choice
Operating boundaries
- Object storage is not a mounted POSIX filesystem
- Data transfer, requests and retention can affect cost
- Replication and backup requirements must be selected explicitly
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: S3-compatible Object Storage. Provider specifications were reviewed on 24 October 2026; actual inventory and quota are checked separately.
Upstream technical reference