Pricing plans that grow with you. From prototype to Enterprise.
80GB of storage
20 million read/write
Build and deploy on AWS
Intuitive Data API based on Mongoose – supports GraphQL, REST JSON, etc
Hybrid-Vector Search for maximum accuracy for agents/AI apps
Scale automatically as your app grows
Build and deploy on AWS, Azure or Google Cloud
Multi-region databases
Secure private networking
Chat and community support
Option to upgrade to 24x7 Enterprise Support (requires prepaid commitment)Volume discounts with annual commits
Health checks for optimal sizing and performance
Provisioned capacity consumption model
Access to AI partner credits
24x7 enterprise support
Option to add Premium Support for 15-minute response times and other premium features
Enterprise | |||
|---|---|---|---|
| Support Type | 24x7 | ||
| Support Goals | |||
| Low Response Time | 24 hours | ||
| Normal Response Time | 24 hours | ||
| High Response Time | 4 hours | ||
| Urgent Response Time | 1 hour | ||
Please contact us for enhanced support needs, migrations or other help you might need.
| USAGE | BILLING UNIT | METERING DETAILS |
|---|---|---|
Read requests | A “Read Request Unit” (RRU) is the unit of measure for billing database reads. It is based on the payload of each read query response. | A read request that returns up to 4KB of data is considered one RRU. If the request returns more than 4KB of data, additional RRUs are required. If the read request involves an ALLOW FILTERING query the data is measured prior to in-memory filtering. |
Write requests | A “Write Request Unit” (WRU) is the unit of measure for billing database writes. It is based on the payload size of each write request. | A write request with up to 1KB of data or a DELETE request are each considered one WRU. If the request has more than 1KB of data, additional WRUs are required. A write index SAI is considered as a write request. The write index SAI size (and the number of WRUs required) is based on the size of each indexed column (not the size of the index), regardless of the column type. Note: Writes in a multi-region configuration are billed for each region written to. |
Storage | “Data Storage” means all data stored into the Database including the data, indexes and metadata. | Storage is calculated based on logical storage consumption. Data Storage is measured in GB per month, using the maximum data stored in the given month for the usage calculation. You are not billed extra for standard backups of your data (It is included in the base storage costs). |
Data Transfer | “Data Transfer” means the transfer of Customer Data out of the database. Billable units and pricing vary depending on whether the Data Transfer occurs within the same region of a cloud provider network (“Data Transfer - Same Region”), across regions within the same cloud provider network (“Data Transfer - Cross Region Within Cloud Provider Network”), or leaves the cloud provider network over the internet (“Data Transfer - Internet”). | Data Transfer charges are measured in GB. |
OPTIONAL FEATURES | DESCRIPTION | METERING DETAILS |
Private Endpoint | Creating a “Private Endpoint” allows users to securely connect applications and third party SaaS offerings to Astra DB. | Users are billed at a fixed rate per hour plus data transfer charges per GB. Data transfer charges using private endpoints are for the transfer of Customer Data into and out of the database. Cloud providers will also bill for use of private endpoint capabilities. |
Vector Dimensions | Vector dimensions are the number of elements in a vector. | Users are billed an incremental metering rate for reads and writes per million vector dimensions, over and above non-vector read and write rates. The vector dimension rate is specified in the metering unit rates table below. |
Multi-Region | “Multi-Region” means replicating the database between multiple cloud regions enabling users to write to and read from multiple regions. | Additional charges include network egress between regions which is billed per GB. This cost is based on the source region. Users will also incur a one-time data transfer charge to replicate all data to the newly added region. |
| Standard | Americas | EMEA | APAC |
|---|---|---|---|
Write Request Units (per 1M) | $0.62 | $0.74 | $0.71 |
Read Request Units (per 1M) | $0.37 | $0.41 | $0.41 |
Data Storage (GB/month) | $0.25 | $0.25 | $0.26 |
Data Transfer (GB) - Same Region | $0.02 | $0.02 | $0.02 |
Data Transfer (GB) - Cross Region Within Cloud Provider Network | $0.05 | $0.05 | $0.13 |
Data Transfer (GB) - Internet | $0.11 | $0.11 | $0.15 |
Private Endpoint ($0.01/hr and data transfer charge of $0.01/GB ingress and egress) | |||
Vector Dimension Read & Writes (per 1M) | $0.04 | $0.04 | $0.04 |
Please note that DataStax may charge a higher rate for a specific region (by cloud provider) than what is shown in the pricing table. |
Multi-regional databases follow the same principles of single regional databases in terms of charging for reads, writes, data transfer and storage. There are additional charges for multi-region databases which are outlined below and we also highlight which of the Metering Details you can reference to get more details. Find Metering Details and their associated Rates here.
Reads are only charged for the region in which the read was done.
Writes are performed to every region which has been deployed with associated charges (see Write Requests).
Data is replicated to each region deployed and storage is charged for each region (see Storage).
Data Transfer is charged for transfer of data between regions and the rate depends on the kind of data replication implemented (see Data Transfer).
Astra Serverless is the underlying architecture under all Astra DB solutions. This provides for a cloud native, microservices based architecture that supports a provisioned capacity pricing model.
More mature enterprises also have other considerations and it’s worth bearing these in mind when choosing which consumption model best suits your needs when using Astra DB.
If you have workloads that have any of the following characteristics you may also want to consider the Provisioned Capacity consumption model. This is the preferred consumption model of more mature workloads that have either
Strict performance needs and your traffic profile meets any of the following criteria:
Or workloads with
For these kinds of workloads, we recommend talking to our team about the benefits of Provisioned Capacity.
You deploy a database in the AWS US East (North Virginia) region. For a period of 15 days, you see activity resulting in 2,000,000 reads and 1,000,000 writes to your database each day. However, on day 16 your application traffic spikes to 6,000,000 reads and 3,000,000 writes until the end of the month. Astra DB scales to deliver a seamless experience to your users, with no manual intervention. Likewise your database starts at 4 GB and grows to a total of 5 GB by month end. Your pricing is based on writes and reads plus the peak storage and actual data transfer used in the month. Each write is 1KB of data and each read is 4KB of data. The following table summarizes your total bill of $86.25 for the month excluding enterprise support.
| Timeframe (Day of Month) |
Day 1-15 | Day 16-30 | Monthly Operations |
|---|---|---|---|
| Total Writes | 15,000,000 writes (1,000,000 writes x 15 days) | 45,000,000 writes (3,000,000 writes x 15 days) | 60,000,000 writes |
| Total Reads | 30,000,000 reads (2,000,000 reads x 15 days) | 90,000,000 reads (6,000,000 reads x 15 days) | 120,000,000 reads |
| Total Storage | 4 GB | 5 GB | 5 GB (maximum size) |
| Same Region Data Transfer | 40 GB | 130 GB | 170 GB |
|
Write Charges |
$9.30 ($0.62 per million * 15 million writes) |
$27.90 ($0.62 per million * 45 million writes) |
$37.20 ($0.62 per million * 60 million writes) |
|
Read Charges |
$11.10 ($0.37 per million * 30 million reads) |
$33.30 ($0.37 per million * 90 million reads) |
$44.40 ($0.37 per million * 120 million reads) |
|
Same Region Data Transfer Charges |
$0.80 ($0.02 * 40GBs) |
$2.60 ($0.02 * 130 GBs) |
$3.40 ($0.02 * 170 GBs) |
|
Data Storage Charges |
$1.25 (5 GB Max x $0.25) |
||
| Total Costs |
$86.25 |
||
This example builds upon Example 1 and demonstrates Astra DB charges using multiple regions for one month. In addition to your Astra DB deployment in North Virginia (NA), you also deploy Astra DB in the Ireland (EMEA) region. In EMEA, you have 30M writes originating from that location along with 60M reads in that region. With the additional activity, your database size reaches 8GBs.
With this multi-region example, all data written in the first region will also be replicated to the second region and visa versa. This will result in additional write charges. In addition, the data written between regions will also drive additional data transfer charges between the two regions.
In North America, the user will see a total of 90M writes on his monthly bill (60M originating in NA, 30M replicated from EMEA). Similarly, the user will also see a total of 90M writes for EMEA (30M originating in EMEA, 60M replicated from NA). The replicated writes will also drive cross region data transfer as well as a higher volume of same region data transfer across availability zones.
| Operations | NA | EMEA |
|---|---|---|
| Writes - Million | 60M + 30M | 30M + 60M |
| Reads - Million | 120M | 60M |
| Same Region Data Transfer | 258 GB (172 GB primary + 86 GB replicas) | 258 GB (86 GB primary + 172 GB replicas) |
| Ongoing Cross Region Data Transfer | 60 GB | 30 GB |
| Storage | 8 GB | 8 GB |
| Write Charges | $122.40 = (90 * $0.62) + (90 * $0.74) | |
| Read Charges | $69.00 = (120 * $.37) + (60 * $.41) | |
| Same Region Data Transfer Charges | $10.32 = (258 * $0.02) + (258 * $.02) | |
| Ongoing Cross Region Data Transfer Charge |
$4.50 = (60 * $0.05) + (30 * $0.05) |
|
| Data Storage Charges |
$4.00 = (8 * 0.25) + (8 * 0.25) |
|
| Total Costs* |
$210.22 |
*Customers migrating existing data into Astra DB will also incur an initial data load charge based on the number of write units along with same region data transfer charges. For multi-region, they will also incur a similar write charge to the second region along with associated data transfer costs within the same regions and across the regions.
Here is a list of the most frequent questions we get about pricing.
1 Astra DB service credit is valued at $1. For example, if you have 100 Astra DB service credits, you have $100 worth of credits that can be used for Astra cloud services.
The Astra DB service credit list price is $1. Discounts are available if you purchase an annual commitment.
No, the Astra DB service credits will burn down as they are consumed. We will help you size your app(s) but the actual usage is based on the categories mentioned above and may vary from the estimated usage numbers.
Yes, the Astra DB service credits (associated with Enterprise plans) expire 365 days after the plan start date. However, upon renewal (and excluding any applicable promotional offers) you may extend the expiry date for 3 months by paying a 10% fee on the amount paid for the remaining Astra DB service credits to be extended.
We have built-in volume discounts with deeper discounts for annual commits. Contact us.
No, this is totally in your control — your database, your choice. We are available on Amazon Web Services, Google Cloud, and Microsoft Azure.
Yes, for AWS, Google Cloud, and Azure, 100% of the Astra DB subscription cost will count towards the committed spend.
This information is publicly available and can be found on our uptime system status page.
Chat and community support are included for free with the Astra DB free plan.
Chat and community support are included for free with the Astra DB Pay As You Go plan, which can be upgraded to 24x7 Enterprise support with unlimited tickets for a fee.
24x7 Enterprise support is available for the Astra DB Enterprise plan, which is priced as a percentage of monthly Astra usage.
Customers with Enterprise support can purchase the Premium Support add-on for 15 minute (versus 1 hour) urgent response times and access to a Named Engineer/Technical Account Manager.
You receive your invoice via email once a month. You will be able to see your consumption in the Astra console.
You can pay for Astra DB via credit card, through your preferred cloud marketplace, or purchase Astra DB service credits via a direct contract with DataStax.
If you run out of credits, your database may be temporarily paused until you resolve your payment issue. If you are on an Enterprise plan, you will be notified and will have 30 days to resolve your payment issue or your database may be suspended.
You will be notified and will have 30 days to resolve your payment issue or your database may be suspended.
Unlimited apps, data sources, and connections
Access to all top AI tools via a single API – OpenAI, Unstructured, NVIDIA AI, Hugging Face, and more
Intuitive drag-and-drop UI for rapid development
Open-source framework with mass adoption – 50K+ GitHub Stars and growing!
Custom pricing
For organizations needing production-grade reliability and expert support
Health checks to optimize performance for production
Modernize NoSQL workloads for Kubernetes and cloud-native deployment
Reduce hosting and cloud costs with 5x larger node sizes
Accurate, hallucination-free AI requires securely accessing sensitive data for RAG and vector search
Build fast and scale easily with rapid provisioning, simple APIs, and data modeling freedom
Drop-in compatibility with Zero-Downtime Migration tools
Automated operations
