S3 Payment Model and Prices

Balance

You can pay for resources using different types of funds: basic funds or bonuses.

Before you start using the storage, top up your balance.

Payment Model

S3 is paid according to the pay-as-you-go model — 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 funds are received, all data will be deleted without the possibility of recovery. If you use Object Lock, locked objects will also be deleted regardless of the lock type or mode.

To ensure there is always enough money in your balance, you can set up balance notifications and automatic top-ups.

Prices

Resource prices can be found at servercore.com.

The cost is influenced 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

The availability of storage classes depends on the region and pool where the bucket is located; for more details, see the S3 section of the Availability Matrix 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 charged separately — in consumption they are marked as old-swift.

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, money is deducted from your balance for the current storage volume. You can view the current data volume in your project in the control panel: in the top menu, click Products → S3 → Buckets section → view the volume above the list of buckets.

When calculating consumption per month:

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

The price for 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 charged. When versioning is enabled, all object versions are charged, except for versions with the Deleted tag.

Metadata of objects and buckets, including empty ones, take up storage space and are charged. Metadata size 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 → section Consumption. Data is presented as consumption and payment charts.

If repository 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 projects, resources, regions, and metrics, and sort 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 resources:

  • Bucket — by a specific bucket;

  • Requests to S3 via CP and Storage API — by outgoing traffic and requests performed in a specific project via the control panel or Object Storage API. This group displays consumption that is not related to a specific bucket, for example, cache clearing.

    For correct detailing of consumption by buckets and requests, we recommend working with S3 via S3 API and Object Storage API.

• for periods before December 1, 2025, consumption is displayed in the storage group and reflects the total consumption across all S3 resources in the project.

To export consumption and payment details in .csv format, click Download CSV and select how rows will be grouped in the export (by hours, days, weeks, months, or years).

Accounting documents

After money is deducted for S3 usage, you can request accounting documents.