Fast NoSQL database with open APIs for any scale
Quickly and easily develop apps at any scale with Azure Cosmos DB, a fully managed and serverless distributed database supporting NoSQL and relational workloads. Get guaranteed speed and availability for NoSQL data, automatic and instant scalability, and support for open source PostgreSQL, MongoDB, and Cassandra. Azure Cosmos DB offers cost-effective pricing models for apps of any size, from dev/test to production.
Explore pricing options
Apply filters to customize pricing options to your needs.
Prices are estimates only and are not intended as actual price quotes. Actual pricing may vary depending on the type of agreement entered with Microsoft, date of purchase, and the currency exchange rate. Prices are calculated based on US dollars and converted using London closing spot rates that are captured in the two business days prior to the last business day of the previous month end. If the two business days prior to the end of the month autumn on a bank holiday in major markets, the rate setting day is generally the day immediately preceding the two business days. This rate applies to all transactions during the forthcoming month. Sign in to the Azure pricing calculator to see pricing based on your current programme/offer with Microsoft. Contact an Azure sales specialist for more information on pricing or to request a price quote. See frequently asked questions about Azure pricing.
US government entities are eligible to purchase Azure Government services from a licensing solution provider with no upfront financial commitment or directly through a pay-as-you-go online subscription.
Important—The price in R$ is merely a reference; this is an international transaction and the final price is subject to exchange rates and the inclusion of IOF taxes. An eNF will not be issued.
US government entities are eligible to purchase Azure Government services from a licensing solution provider with no upfront financial commitment or directly through a pay-as-you-go online subscription.
Important—The price in R$ is merely a reference; this is an international transaction and the final price is subject to exchange rates and the inclusion of IOF taxes. An eNF will not be issued.
Azure Cosmos DB pricing model
Azure Cosmos DB bills for three different types of usage: compute, storage and bandwidth. The tabs below describe each compute pricing model in greater detail with its accompanying storage and bandwidth pricing models.
Once a compute pricing model and API are chosen, they cannot be changed.
Compute Pricing:
Request Unit (throughput): Azure Cosmos DB bills using Request Units (RU) measured per second (RU/s). Request Units are a proxy for compute, memory and IO used to process database operations and are billed across all selected Azure regions for your Azure Cosmos DB account.
Options for throughput include: Standard Provisioned throughput, Autoscale provisioned throughput and Serverless.
Applicable APIs: NoSQL, MongoDB (RU), Cassandra, Gremlin, and Table.
vCore: Azure Cosmos DB bills for vCores (compute and memory) per node to process database operations and are billed on the size and number of nodes provisioned.
Available APIs: PostgreSQL and MongoDB (vCore).
Storage Pricing:
Consumed Storage: Azure Cosmos DB bills for consumed storage rounded up to the next GB per container/collection/table/graph per region. Consumed storage includes all transactional and analytical data and indexes, and backups.
Applicable APIs: NoSQL, MongoDB (RU), Cassandra, Gremlin, and Table.
Disk Storage: Azure Cosmos DB bills for disks provisioned for each node by storage size.
Applicable APIs: PostgreSQL and MongoDB (vCore).
Bandwidth Pricing:
Data Egress: Azure bills for data that egresses the Azure cloud or transits the Azure WAN across regions or availability zones.
Applicable APIs: All.
Azure Cosmos DB for PostgreSQL provides horizontal scale-out capability to hundreds of nodes and is best for high performance workloads that require:
- Dynamic scalability without the cost of manual sharding with low application re-architecture required
- Transactional and analytical queries to run on the same database
Learn more about Azure Cosmos DB for PostgreSQL
Single node
Single node size (compute and memory)
Single node offers a cost-effective option for dev/test and growing workloads to get started with Azure Cosmos DB for PostgreSQL on a single node and be scale-out ready.
| vCore/Node | Memory (Gib)/Node | Price/Node | 1 year reserved* | 3 year reserved* |
|---|---|---|---|---|
| 1 (Burstable) | 2 GiB | $- | N/A | N/A |
| 2 | 8 GiB | $- |
$-
|
$-
|
| 2 (Burstable) | 4 GiB | $- | N/A | N/A |
| 4 | 16 GiB | $- |
$-
|
$-
|
| 8 | 32 GiB | $- |
$-
|
$-
|
| 16 | 64 GiB | $- |
$-
|
$-
|
| 32 | 128 GiB | $- |
$-
|
$-
|
| 64 | 256 GiB | $- |
$-
|
$-
|
Single node storage – General purpose storage
You can configure storage for Azure Cosmos DB for PostgreSQL single node to be 128 GiB, 256 GiB, 512 GiB, 1024 GiB, or 2048 GiB. 1024 GiB and 2048 GiB storage is supported only with 8 vCore or greater compute. Storage is charged per GiB of storage you provision.
| Price | |
|---|---|
| 128 GiB | $-/month |
| 256 GiB | $-/month |
| 512 GiB | $-/month |
| 1,024 GiB | $-/month |
| 2,048 GiB | $-/month |
Multi-node
Worker node size (compute and memory)
Each Azure Cosmos DB for PostgreSQL multi-node cluster starts at 2 worker nodes. As your workload grows, you can add more vCores (logical CPUs) and memory to your worker nodes—and you can scale out your Postgres cluster by adding more worker nodes.
| vCore/Node | Memory (Gib)/Node | Price/Node | 1 year reserved* | 3 year reserved* |
|---|---|---|---|---|
| 4 | 32 GiB | $- |
$-
|
$-
|
| 8 | 64 GiB | $- |
$-
|
$-
|
| 16 | 128 GiB | $- |
$-
|
$-
|
| 32 | 256 GiB | $- |
$-
|
$-
|
| 64 | 512 GiB | $- |
$-
|
$-
|
| 96 | 672 GiB | $- |
$-
|
$-
|
| 104 | 672 GiB | $- |
$-
|
$-
|
Co-ordinator size (compute and memory)
Each Azure Cosmos DB for PostgreSQL multi-node cluster has 1 co-ordinator. As the performance needs of your workload grow, you can add more vCores (logical CPUs) and memory to your co-ordinator.
| vCore* | Memory (Gib) | Price | 1 year reserved** | 3 year reserved** |
|---|---|---|---|---|
| 4 | 16 GiB | $- |
$-
|
$-
|
| 8 | 32 GiB | $- |
$-
|
$-
|
| 16 | 64 GiB | $- |
$-
|
$-
|
| 32 | 128 GiB | $- |
$-
|
$-
|
| 64 | 256 GiB | $- |
$-
|
$-
|
| 96 | 384 GiB | $- |
$-
|
$-
|
Storage per node – General purpose storage
You can configure storage for Azure Cosmos DB for PostgreSQL worker nodes to be 0.5 TiB, 1 TiB, 2 TiB, 4 TiB, 8 TiB, or 16 TiB per node. You can configure coordinator nodes to be 128 GiB, 256 GiB, 0.5 TiB, 1 TiB, 2 TiB, 4 TiB, 8 TiB, or 16 TiB. General purpose storage is charged per GiB of storage you provision.
| Storage | Price |
|---|---|
| 128 GiB (co-ordinator only) | $-/month |
| 256 GiB (co-ordinator only) | $-/month |
| 0.5 TiB | $-/month |
| 0.5 TiB | $-/month |
| 1.0 TiB | $-/month |
| 1.0 TiB | $-/month |
| 2.0 TiB | $-/month |
| 2.0 TiB | $-/month |
| 4.0 TiB | $-/month |
| 4.0 TiB | $-/month |
| 8.0 TiB | $-/month |
| 8.0 TiB | $-/month |
| 16.0 TiB | $-/month |
| 16.0 TiB | $-/month |
| 32.0 TiB | $-/month |
| 32.0 TiB | $-/month |
The following is the same for single and multi-node clusters
High availability
High availability (HA) avoids database downtime by maintaining standby replicas of every node in a cluster. If a node goes down, Hyperscale switches incoming connections from the failed node to its standby. Failover happens within a few minutes, and promoted nodes always have fresh data through PostgreSQL synchronous streaming replication and the same connection string. Enabling HA for your Azure Cosmos DB for PostgreSQL cluster effectively creates another set of nodes and thus doubles the cluster price.Back up Storage
Back up storage is the storage associated with automated backups of your Azure Cosmos DB for PostgreSQL cluster. There is no additional charge for backup storage for up to 100% of your total provisioned storage on a given node. Additional consumption of backup storage will be charged in GiB/month starting June 1, 2024.
| Price | |
|---|---|
| Locally Redundant (1 GiB) | $-/month |
Bandwidth
Azure Networking bills for data that egresses the Azure cloud to a destination on the internet or transits the Azure WAN between regions, see Azure Networking Bandwidth Pricing.
Try Azure Cosmos DB for free
There are a variety of ways for you to get started free with Azure Cosmos DB.
| 30 days free. Run a non-production Azure Cosmos DB database for a limited time. | Get Started: Enjoy a time-limited Azure Cosmos DB experience free of charge and without an Azure subscription. You can renew any number of times. |
| Azure Cosmos DB free tier. Develop and test applications or run small production workloads, free within the Azure environment. | Get Started: Enable free tier on a new account to receive 1,000 RU/s provisioned throughput and 25 GBs storage free each month for the life of one Azure Cosmos DB account per Azure subscription. |
| Azure free account. New to Azure? Develop and test a pre-production application with Azure Cosmos DB and other Azure services. | Get Started: Try Azure Cosmos DB and other Azure services as a part of a 12-month Azure free account. Get $200 credit for 30 days and enjoy 400 RU/s of provisioned throughput and 25 GBs of storage per month free. New Azure free accounts can also enable the Azure Cosmos DB free tier to gain additional free provisioned throughput and storage. |
| Azure Cosmos DB local emulator. Test applications from your local machine without creating an Azure subscription or incurring any cost. | Get Started: Download the free Azure Cosmos DB emulator from your local Windows or Linux machine. Once you are satisfied with your database, you can deploy it by pointing to an Azure Cosmos DB instance in the cloud. |
Azure pricing and purchasing options
Connect with us directly
Get a walkthrough of Azure pricing. Understand pricing for your cloud solution, learn about cost optimisation and request a custom proposal.
Talk to a sales specialistSee ways to purchase
Purchase Azure services through the Azure website, a Microsoft representative or an Azure partner.
Explore your optionsAdditional resources
Azure Cosmos DB
Learn more about Azure Cosmos DB features and capabilities.
Pricing calculator
Estimate your expected monthly costs for using any combination of Azure products.
SLA
Review the Service Level Agreement for Azure Cosmos DB.
Documentation
Review technical tutorials, videos and more Azure Cosmos DB resources.
Frequently asked questions
-
Request units are the currency for database operations in Azure Cosmos DB. Each operation - writes, updates, reads and queries - consumes CPU, memory and IOPs resources. These resources incur charges which are expressed in request units (RU). Provisioned throughput is the total throughput capacity for database operations and is set as request units per second (RU/s). To learn more please visit request units in Azure Cosmos DB page.
-
You are billed by the hour for the provisioned throughput, expressed in request units per second (U/s), that you set for your database or container.
Standard provisioned throughput for an individual container:
If you create an Azure Cosmos DB database account in East US 2 with two containers with standard provisioned throughput of 500 RU/s and 700 RU/s, respectively, you would have a total provisioned throughput of 1,200 RU/s. You would thus be charged 12 x $- = $-/hour.
If your throughput needs changed and you have increased each container’s capacity by 500 RU/s while also creating a new container using 20,000 RU/s, your overall provisioned capacity would be 22,200 RU/s (1000 RU/s + 1200 RU/s + 20,000RU/s). Your bill would then change to: $- x 222 = $-/hour.
In a month of 720 hours, if for 500 hours provisioned throughput was 1,200 RU/s and for the remaining 220 hours provisioned throughput was 22,200 RU/s, your monthly bill will show: 500 x $-/hour + 220 x $-/hour = $-/month.
Provisioned throughput for a database (a set of containers):
If you create an account in East US 2 with two Cosmos DB databases (with a set of collections under each) with provisioned throughput of 50K RU/s and 70K RU/s, respectively, you would have a total provisioned throughput of 120K RU/s. You would thus be charged 1200 x $- = $-/hour.
If your throughput needs changed and you increased each database’s provisioned throughput by 10K RU/s each, your overall provisioned capacity would be 140K RU/s (60K RU/s + 80K RU/s). Your bill would then change to: 1400 * $- = $-/hour.
In a month of 720 hours, if for 500 hours provisioned throughput was 120K RU/s and for the remaining 220 hours provisioned throughput was 140K RU/s, your monthly bill will show: 500 x $-/hour + 220 x $-/hour = $- + $- = $-/month.
-
With autoscale (previously "autopilot"), you set a maximum provisioned throughput limit in RU/s that your database or container can scale to. You are then billed by the hour for RU/s of provisioned throughput used, starting at 400 request units per second (RU/s) or 10% of your maximum. For example, if you set a maximum of 8,000 RU/s Azure Cosmos DB will automatically scale between 800 - 8,000 RU/s based on actual usage.
-
When enabled on a new Azure Cosmos DB account, free tier gives the first 1,000 RU/s and 25 GB of storage for free for the lifetime of the account. Additionally, when using shared throughput databases, you can create up to 25 containers that share 1,000 RU/s at the database level (max. 5 shared databases per free tier account). You can have a maximum of one free tier account per Azure subscription and must opt in when creating the account.
-
In free tier accounts, you will receive the first 400 RU/s provisioned throughput and 5 GB of storage free each month. Any provisioned throughput and storage beyond 400 RU/s and 5 GB will be billed at the regular Azure Cosmos DB rates. The 400 RU/s applies to standard provisioned throughput, autoscale provisioned throughput and multi-region writes (multi-master). Free tier is not applicable to serverless.
The free tier discount is applied at the account level. For example, if in one month, an account had a total of 400 RU/s and three regions, with 5 GB in each region, the account would be billed for 800 RU/s (400 RU/s x 3 regions – 400 RU/s) and 10 GB of storage (5 GB x 3 regions – 5 GB) for each hour in the month. If the regions have different rates for RU/s and storage, the discount will reflect the rates of the region the account was created in.
-
When you choose to make an Azure Cosmos DB account (with databases and containers) span across geographic regions, you are billed for the throughput and storage for each container in every region and the data transfer between regions. As an example, let us assume you have a container in West US provisioned with throughput 10K RU/s and store 1TB of data this month. Let us assume you add 3 regions: East US, North Europe and East Asia, each with the same storage and throughput. Your total monthly bill will be (assuming 31 days in a month):
Item Usage (Month) Rate Monthly Cost Throughput bill for container in West US 10K RU/s * 24 * 31 $- per 100 RU/s per hour $- Throughput bill for 3 additional regions - East US, North Europe and East Asia 3 * 10K RU/s * 24 * 31 $- per 100 RU/s per hour $- Storage bill for container in West US 1 TB $-/GB $- Storage bill for 3 additional regions - East US, North Europe and East Asia 3 * 1TB $-/GB $- Total $- Let us also assume that you egress 100GB of data every month from the container in West US to replicate data into East US, North Europe and East Asia. You are billed for egress as per data transfer rates.
-
When you choose to operate containers that span across multiple geographic regions, you are billed for the provisioned throughput and storage for each container in every region and the data transfer between regions. You will be billed for the provisioned throughput.
-
Storage capacity is billed in units of the maximum hourly amount of data stored, in GB, over a monthly period. For example, if you utilised 100 GB of storage for half of the month and 50 GB for the second half of the month, you would be billed for an equivalent of 75 GB of storage during that month.
-
You are billed for each hour the container or database exists, regardless of usage or if the container or database is active for less than an hour. For example, if you create a container or database and delete it 5 minutes later, your bill will reflect a 1 hour.
-
You are charged for the maximum provisioned throughput for any given hour.
For instance, if you increase provisioned throughput at 9:30 AM from 400 RU/s to 1000 RU/s and then lower provisioned throughput at 10:45 AM back to 400 RU/s, you will be charged for two hours of 1000 RU/s.
If you increase provisioned throughput for a container or a set of containers at 9:30 AM from 100K RU/s to 200K RU/s and then lower provisioned throughput at 10:45 AM back to 100K RU/s, you will be charged for two hours of 200K RU/s.
-
You can scale up or scale down the provisioned throughput (i.e., Request Units per second) for each container or a database by using the Azure Portal, one of the supported SDKs, ARM template, PowerShell, Azure CLI or the REST API.
-
Azure Cosmos DB reserved capacity helps you save money by offering a discount if you prepay for one year or three years of provisioned throughput. Reserved capacity provides a billing discount and does not affect the runtime state of your resources. You can buy a reserved capacity for Azure Cosmos DB in the Azure portal. To learn more about reserved capacity, read the Azure Cosmos DB documentation.
Talk to a sales specialist for a walk-through of Azure pricing. Understand pricing for your cloud solution.
Get free cloud services and a $200 credit to explore Azure for 30 days.