GLOBALATLAS
Object storage: access model, capacity planning and recovery considerations before choosing a configuration.
GLOBALATLAS
Choose a location and resource class. Open a configuration to calculate your order.
London · All locations
All prices in USD · 2 configurations · updated 08/11/2026 · Taxes and optional services excluded
London · United Kingdom
Additional storage / GB / month: $0.07
Outbound / GB: $0.014
Archive / GB / month: $0.0084
1,000 GB included
Additional storage and outbound traffic billed separately
Listed tariff · capacity checked before payment
Choose configurationLondon · United Kingdom
Additional storage / GB / month: $0.14
Outbound / GB: $0.014
Archive / GB / month: $0.0084
1,000 GB included
Additional storage and outbound traffic billed separately
Listed tariff · capacity checked before payment
Choose configurationOBJECT STORAGE
Datasets, media, archives and application assets — stored as objects addressed by a key. A natural fit when the application works with files through an API.
Group objects into logical containers and let the application request the data it needs. This is not a directly attached operating-system disk.
Organize source files and prepared datasets by stable keys. Plan data transfer to the compute region.
Keep images, exports and attachments separate from the application server. Define access rules for each use case.
Estimate capacity growth and retrieval needs. Retention, object versioning and lifecycle support depend on the selected service.
An object, a key, an API
A volume connected to your server
Block storageShared paths, coordinated access
File storageThe specific endpoint, API compatibility, access credentials and transfer rates must be confirmed with the selected configuration before production use.
No. A working copy can be overwritten or deleted. A recovery strategy needs separate copies, retention rules and a tested restore procedure.