Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex DataSphere
  • Getting started
  • Terraform reference
  • Audit Trails events
  • Access management
  • Pricing policy
  • Public materials
  • Release notes

In this article:

  • What goes into the cost of using DataSphere
  • Billing unit
  • DataSphere Notebook
  • Running jobs in DataSphere Jobs
  • DataSphere Inference
  • Using Yandex Data Processing clusters
  • Disk space usage
  • Prices for the Russia region
  • Unit cost
  • Computing resource
  • Storing data inside DataSphere
  • Outgoing traffic
  • Examples of cost calculation
  • DataSphere Notebook
  • DataSphere Inference

DataSphere pricing policy

Written by
Yandex Cloud
Updated at May 14, 2025
  • What goes into the cost of using DataSphere
    • Billing unit
    • DataSphere Notebook
    • Running jobs in DataSphere Jobs
    • DataSphere Inference
    • Using Yandex Data Processing clusters
    • Disk space usage
  • Prices for the Russia region
    • Unit cost
    • Computing resource
    • Storing data inside DataSphere
    • Outgoing traffic
  • Examples of cost calculation
    • DataSphere Notebook
    • DataSphere Inference

To estimate your service costs, see the pricing in this section.

Prices for service products are also available in the Price list.

What goes into the cost of using DataSphereWhat goes into the cost of using DataSphere

When using DataSphere, you pay for the use of computing resources: the computation and instance running time is charged per second.

Billing unitBilling unit

Pricing is based on a billing unit. The number of billing units spent on computation depends on:

  • Computing resource capacity.

  • Computation time.

    The computation time is rounded up to an integer of seconds.

One billing unit represents the cost of using one CPU core for one second. The number of units depends on the computing resource configuration.

DataSphere NotebookDataSphere Notebook

When performing computations and training models in DataSphere notebooks, you pay for the whole time the VM is used since the first computations are run in a notebook until the VM is released, regardless of whether any computations were performed after the first run. If you run computations using Yandex Data Processing clusters, they are charged separately.

You are separately charged for data storage in datasets and project storage expansion.

Running jobs in DataSphere JobsRunning jobs in DataSphere Jobs

When you run computations remotely using DataSphere Jobs, you pay for the computation time in the selected computing resource configuration. You also pay for storing data required to run jobs: their cache, logs, input data, and execution results.

DataSphere InferenceDataSphere Inference

When deploying models in DataSphere Inference, you pay for the uptime of each node instance: from its start to deletion.

You pay for additional node instance disks separately.

Using Yandex Data Processing clustersUsing Yandex Data Processing clusters

The cost of computations in Yandex Data Processing clusters includes:

  • Computing resources of the selected DataSphere configuration.
  • The Yandex Data Processing cluster's full lifetime duration according to the Yandex Data Processing pricing policy.

Learn more about integration with Yandex Data Processing.

Disk space usageDisk space usage

Each DataSphere project has a free-of-charge storage amount. If you increase the project size quota, the entire requested storage capacity exceeding 10 GB is paid for separately. For more information about pricing, see Quotas and limits in DataSphere.

You will be charged separately for data stored inside datasets and file storages.

If you need to store large amounts of data, you can use Yandex Object Storage. In which case you will pay for data storage according to the Object Storage pricing policy.

Model storage is charged separately. Its pricing depends on the model size that is calculated in GB and rounded up to an integer.

In all calculations: 1 GB = 230 bytes, 1 MB = 220 bytes.

The monthly prices are based on 720 hours per month.

Prices for the Russia regionPrices for the Russia region

Note

Prices for Yandex Cloud resources vary based on the region. For more information about the available regions, see Regions.

The currency you can use to pay for the resources depends on which legal entity you entered into agreement with. For more information on creating an account, see Registering an account in Yandex Cloud.

The prices of the configurations are valid for computations in DataSphere Notebook, DataSphere Jobs jobs, and the use of DataSphere Inference.

Unit costUnit cost

Number Price per 1 second of computations,
without VAT
One unit $0.0000108

Computing resourceComputing resource

Configuration Consumption in units
per second
of configuration operation
Price per hour
of computations,
without VAT
c1.4 (4 vCPUs, 0 GPU) 4 $0.155520
c1.8 (8 vCPUs, 0 GPU) 8 $0.311040
c1.32 (32 vCPUs, 0 GPU) 32 $1.244160
c1.80 (80 vCPUs, 0 GPU) 80 $3.110400
g1.1 (8 vCPUs, 1 GPU V100) 72 $2.799360
g1.2 (16 vCPUs, 2 GPU V100) 144 $5.598720
g1.4 (32 vCPUs, 4 GPU V100) 288 $11.197440
g2.1 (28 vCPUs, 1 GPU A100) 116 $4.510080
g2.2 (56 vCPUs, 2 GPU A100) 232 $9.020160
g2.4 (112 vCPUs, 4 GPU A100) 464 $18.040320
g2.8 (224 vCPUs, 8 GPU A100) 928 $36.080640
gt4.1 (4 vCPUs, 1 GPU T4) 36 $1.399680
gt4i.1 (8 vCPUs, 1 GPU T4i) 50 $1.944000

Storing data inside DataSphereStoring data inside DataSphere

Resource Price of 1 GB per month, without VAT
Project storage size, up to 10 GB Free of charge
Project storage size, over 10 GB $0.107195
Node instance disk $0.107195
Datasets $0.107195
File storage $0.123269
Model $0.107195
DataSphere Jobs data $0.107195

Outgoing trafficOutgoing traffic

When using the service, you pay for traffic from Yandex Cloud to the internet. Traffic between internal IP addresses of Yandex Cloud services and incoming internet traffic is free.

The first 100 GB of outgoing traffic per month are free of charge.

The minimum billing unit is 1 MB.

Resource category Price of 1 GB,
without VAT
Outgoing traffic, 100 GB or less per month Free
Outgoing traffic, over 100 GB per month $0.013770

Examples of cost calculationExamples of cost calculation

DataSphere NotebookDataSphere Notebook

Cost of using DataSphere with the following parameters:

  • Computing resources: g1.1 configuration with 8 CPUs and 1 GPU
  • VM usage time: 10 minutes

The cost of using the service will be:

72 × 600 = 43,200 units for VM usage
43,200 × $0.0000108 = $0.46656

Total: $0.46656, cost of using DataSphere.

Where:

  • 72: Number of units per g1.1 configuration.
  • 600: VM usage time in seconds.
  • $0.0000108: Cost per unit.

DataSphere InferenceDataSphere Inference

Cost of using DataSphere Inference with the following parameters:

  • Number of instances per node: 2.
  • Instance configuration: g1.1 with 8 CPUs and 1 GPU.
  • Node runtime: 2 days 3 hours 36 minutes.

Converting node runtime into seconds:

2 × (24 × 60 × 60) + 3 × (60 × 60) + 36 × 60 = 172,800 + 10,800 + 2,160 = 185,760

Where:

  • (24 × 60 × 60): Number of seconds in 24 hours.
  • (60 × 60): Number of seconds in 1 hour.
  • 60: Number of seconds in 1 minute.

The cost of using DataSphere Inference will be:

72 × 185,760 × 2 = 26,749,440 units for the node
26,749,440 × $0.0000108 = $288,893952

Total: $288,893952, cost of using DataSphere.

Where:

  • 72: Number of units per g1.1 configuration.
  • 185,760 : Node runtime in seconds.
  • 2: Number of instances per node.
  • $0.0000108: Cost per unit.

Was the article helpful?

Previous
Access management
Next
Public materials
© 2025 Direct Cursus Technology L.L.C.