Buckets

Quake AI concept: Containers

• Vultr calls the OpenStack Swift container equivalent a bucket, and the docs describe buckets as the primary organizational unit for storing and managing objects. The page explicitly frames Vultr Object Storage as S3-compatible rather than as a Swift container API. (Vultr Object Storage Subscription Limits)
• Buckets are globally unique within the Vultr Object Storage system, which is a different naming and namespace model than OpenStack Swift container names. The doc also says bucket names must be 3 to 63 characters long, with a stricter 3 to 53 character limit if archival storage may be enabled. (Vultr Object Storage Subscription Limits)
• Vultr imposes a per-subscription bucket quota of 100 buckets by default, with increases handled through support. OpenStack Swift container limits are not described on this Vultr page, so Vultr clearly exposes a subscription-level bucket quota in its object storage service. (Vultr Object Storage Subscription Limits)
• Vultr ties archive behavior to the bucket itself: archival storage is available only on Standard and Archive subscriptions, and a bucket becomes permanently ineligible for archival if versioning has ever been enabled. The page also states archived objects show as 0 bytes until restored, which is operational behavior not surfaced as Swift container behavior here. (Vultr Object Storage Subscription Limits)