S3 Payment Model and Prices
Balance
You can pay for resources with different types of funds: main funds or bonuses.
Before you start using the storage, top up your balance.
Payment Model
S3 is billed on a pay-as-you-go basis — payment for consumed resources is deducted every hour.
As long as there are uploaded objects in S3, you will be charged for it; to stop being charged, delete all data.
Block resources if there is not enough money in the balance
If there is not enough money on your balance to pay for the resources consumed during the previous hour, S3 operation is suspended:
- data access (reading, modifying) is blocked;
- data storage continues to be charged.
Data will be stored for 30 calendar days. If no payment is received, all data will be permanently deleted. If you use Object Lock, locked objects will also be deleted regardless of the lock type and mode.
To ensure that there are always sufficient funds on the balance, you can configure balance notifications and automatic balance top-up.
Prices
Resource prices can be viewed at servercore.com.
The cost is affected by the storage class and resource consumption:
- number of API requests;
- outgoing traffic volume (GB);
- storage volume (MB/hour).
Storage Classes
The storage class affects the price of each resource:
- standard storage — suitable for storing and distributing frequently used data. Resource prices depend on consumption volume (except for API request prices);
- cold storage — suitable for storing rarely used data. Resource prices are fixed regardless of the consumption volume;
- glacier storage — suitable for storing data that is used very rarely. At the same time, the minimum object storage time is not limited. Resource prices are fixed regardless of the consumption volume.
The availability of storage classes depends on the region and pool where the bucket is located; for more information, see the S3 availability by location guide.
Number of API requests
API requests are sent during any data operations.
GET, HEAD, PUT, POST, and COPY requests are charged.
Requests to the Swift API (old) are billed separately — they are marked as old-swift in consumption.
DELETE requests and requests that returned an HTTP response with codes 403, 500, 501, 502, 503, and 504 are not charged.
Outgoing traffic volume
Traffic from the storage to the internet (viewing and downloading objects) is charged.
Traffic within Servercore and incoming traffic are not charged.
Storage volume
Funds for the current storage volume are deducted from your balance every hour. You can check the current data volume in your project in the control panel: in the top menu, click Products → S3 → Buckets section, and view the volume above the list of buckets.
When calculating consumption for the month:
- the storage volume consumed for each hour is summed (MB/hour);
- one month is considered to contain 730 hours.
The monthly storage volume price, which can be viewed on servercore.com, is calculated using the formula:
Price per 1 GB/month = Price per 1 MB/hour × 1,024 MB × 730 hours
If the storage volume is changed, the payment for standard storage for the hours after the change will correspond to the new volume.
When using segmented upload, object segments and the manifest file are billed. When versioning is enabled, all object versions are billed except for versions with the Deleted tag.
Metadata of objects and buckets, including empty ones, occupy storage space and are billed. The size of the metadata depends on the storage class:
- standard storage — 14 KB;
- cold storage — 24 KB;
- ice storage — 128 KB.
View consumption
You can view resource consumption in the control panel: in the top menu, click Products → S3 → the Consumption section. The data is presented as consumption and payment charts.
If storage objects are distributed via CDN, in the control panel in the top menu click Products → CDN → the Consumption section.
On the Consumed tab, you can view consumption by projects, resources, regions, and metrics, and sort the charts by the required time interval.
Resource consumption is displayed differently depending on the viewing period:
-
for periods after December 1, 2025, consumption is grouped by resource:
-
Bucket— on a particular bucket; -
Requests to S3 via CP and Storage API— by outgoing traffic and requests executed in a specific project via the control panel or Object Storage API. This group displays consumption that is not related to a specific bucket, such as cache clearing.For accurate consumption details by buckets and requests, it is recommended to work with S3 via S3 API and Object Storage API.
-
-
for periods prior to December 1, 2025, consumption is displayed in the
storagegroup and reflects total consumption across all S3 resources in the project.
To export consumption and payment details in .csv format, click Download CSV and choose how rows in the export should be grouped (by hours, days, weeks, months, years).
Accounting documents
After funds are deducted for S3 usage, you can obtain accounting documents.