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.

	Price for storage	Price for API requests	Price for outgoing traffic
Standard storage	High	Low	Low
Cold storage	Medium	Medium	Medium
Glacier storage	Low	High	Medium

Storage class availability depends on the region and pool where the bucket is located; for more information, see the S3 section of the Product 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 Swift API (old) are billed separately — in consumption they are indicated with the old-swift label.

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

Every hour, funds are deducted from the balance for the current storage volume. You can check the current data volume in the project in the control panel: in the top menu, click Products → S3 → Buckets section → view the volume above the bucket list.

When calculating the consumption for a month:

• the storage volume consumed for each hour is summed (MB/hour);
• one month is considered to contain 730 hours.

The price for the storage volume per month, 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, occupies space in storage and is billed. The size of metadata depends on the storage class:

• for standard or cold storage — 4 KB;
• for cold storage — 128 KB.

View consumption

You can view resource consumption in the control panel: in the top menu, click Products → S3 → Consumption section. The data is presented in the form of consumption and payment graphs.

If storage objects are distributed via CDN, in the control panel, in the top menu, click Products → CDN → Consumption section.

On the Consumed tab, you can view consumption by project, resource, region, and metric, and filter the graphs by the desired time interval.

Resource consumption is displayed differently depending on the viewing period:

• for periods after December 1, 2025, consumption is grouped by resources:

  • Bucket — by a specific bucket;

  • Requests to S3 via CP and Storage API — by outgoing traffic and requests made in a specific project via the control panel or Object Storage API. The group displays consumption not related to a specific bucket, such as cache purging.

    For correct breakdown of consumption 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 storage group and reflects total consumption for all S3 resources in the project.

To export a breakdown of consumption and payments in .csv format, click Download CSV and select how the rows in the export will be grouped (by hours, days, weeks, months, years).

Accounting documents

After funds are deducted for using S3, you can obtain accounting documents.