cr.sa-saopaulo-1.basaltic.cloud for Docker and OCI clients.
Image references include the account handle:
cr.sa-saopaulo-1.basaltic.cloud/my-account/api:v1. The management API uses
registry.sa-saopaulo-1.basaltic.sh.
Use the repository’s returned uri rather than assembling it yourself.
Repositories, images, and tags
A repository has an immutable name, optional deletion protection, and mutable or immutable tags. An image digest identifies exact manifest bytes. A tag is a name pointing to a manifest and can move unless tag immutability prevents it. Multi-platform manifests, signatures, and other OCI artifacts share this model. Deleting a tag removes that pointer. Deleting a digest removes its manifest and all tags pointing to it. Shared layers are deduplicated across repositories in the same account; deleting an image does not immediately reclaim every byte it references. Cleanup removes layers that are no longer referenced.Authentication
The REST API under/v1 uses a platform bearer token and X-Account-Id, as
explained in Authentication. Container clients use /v2 and
a separate short-lived registry credential obtained from
POST /v1/authorization-token. A registry credential cannot call the control
plane. Its per-repository access is determined by IAM and resource policies.
Create a repository
Choose a name, tag settings, and deletion protection.
Push and pull images
Authenticate a container client and deploy by digest.
Lifecycle policies
Preview cleanup rules before installing them.
Encryption
Choose platform encryption or a customer-managed KMS key.
Pull-through cache
Cache upstream images under an account-owned prefix.
Permissions
Separate image consumers, publishers, and administrators.