Object Storage

Quake AI concept: S3 Compatibility

• Vultr documents its object storage as "S3-compatible APIs" and points users to an "S3 Compatibility Matrix," which frames compatibility as a bounded support surface rather than OpenStack Swift's native API behavior with optional S3 middleware. The canonical object storage page does not expose a Swift-style account/container API in the docs, only bucket-oriented management language. Vultr Object Storage Setup and Management
• Vultr's docs describe bucket-level management and credential regeneration for "S3-compatible buckets," which differs from OpenStack Swift's account/container model. The page language is focused on buckets and access credentials, not Swift containers or per-container ACL primitives. Vultr Object Storage Setup and Management
• The limits page gives Vultr Object Storage a default cap of 100 buckets per subscription, with increases handled by support. OpenStack Swift does not document a fixed bucket quota in the same way on the canonical Swift S3 middleware concept page, so this is a provider-side subscription limit rather than a Swift-native compatibility trait. Vultr Object Storage Subscription Limits
• Vultr explicitly limits Archival Storage to Standard and Archive subscriptions, and buckets over 53 characters cannot enable archival; if versioning is ever enabled, that bucket becomes permanently ineligible for archival. Those policy constraints are specific to Vultr's object storage product and are not part of the generic OpenStack Swift S3 compatibility surface. Vultr Object Storage Subscription Limits