Pricing and billing

Astra DB handles billing through an integration with Stripe, and displays all related billing information in the Billing section of your organization.

To view your billing details, open your Astra Portal and go to Billing in the left navigation. You can review the following details here:

  • Estimated bill under Billing Details.

  • Your subscription plan and payment method.

    • If you have the free plan, select Add Payment Method to upgrade to the pay-as-you-go plan.

    • If you have the pay-as-you-go plan, the payment method appears. You can update/remove this method at any time.

  • Current year and legacy invoices, which are downloadable.

You can also see database usage for each database and streaming tenant included in your server. Click the row for the database or streaming tenant you want to view. Usage details are provided for each region for the selected database or streaming tenant.

Units of measure

The following units of measure affect the pricing of your database:

  • Read requests (per 1M): the unit of measure for billing database reads. This unit is based on the amount of data retrieved to satisfy the query. A read request that returns up to 4KB of data is considered one Read Request Unit (RRU). If the request returns more than 4KB of data, additional read requests are required. If a read request involves server-side filtering or aggregation of data, the data is measured before the filtering or aggregation takes place. Some examples of queries where this can happen are:

    • Queries that use the ALLOW FILTERING clause.

    • Queries that use the COUNT function.

    • Queries that use the GROUP BY clause.

    • Queries that do not request all columns from a row be returned.

  • Write requests (per 1M): the unit of measure for billing database writes. This unit is based on the payload size of each write request. A write request with up to 1KB of data is considered one Write Request Unit (WRU). If the request has more than 1KB of data, additional writes are required.

    • Insert/Update/Upsert: each option is treated as a write operation and is calculated as part of the Write Request Unit (WRU).

    • Logged and Unlogged are the two types of batched writes. Logged batched writes have an additional WRU consumed.

      For example, a single partition unlogged batch write operation with 10 rows, each row containing 1.2KB of data has 12 WRUs (Total size of the single partition rows divided by 1KB. That is, [(10 rows * 1.2KB)/1KB = 12 WRUs]). A 2-partition logged batch with 2 rows (one row for each partition), each row containing 1.2KB of data has 5 WRUs ([ (2 * 1.2KB) /1KB + 2 = 5 WRU]). This calculation depends on the size per table in the batch. In this case, the size of the table (2 * 1.2KB) results in 3 WRUs and 2 additional WRUs for logged batch operation.

    • One delete operation is considered one write request regardless of the size. This is calculated as part of the WRU. There is no charge for the TTL delete operation, DROP statements or TRUNCATE statements.

  • Data storage (GB/month): all data stored in the database (including the actual data, indexes, and metadata). You are not billed extra for standard backups of your data. It is included in the base storage costs.

  • Data Transfer (GB): the transfer of customer data out of the database, including data transferred between the replicas to meet the replication factor for the data. 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").

Premium charges are applied for:

  • Dimensions used in Query: based on database dimensions and average dimensions per query.

  • Aggregated count of the number of dimensions searched with vector search Approximate Nearest Neighbor (ANN) queries.

  • Aggregated count of the number of dimensions searched with vector search ANN queries.

  • Aggregated count of the number of dimensions written to.

  • Index Storage Size: estimate storage size per month, methods of procedure (MOP) per month, and either three or one Availability Zones (AZ).

Was this helpful?

Give Feedback

How can we improve the documentation?

© 2024 DataStax | Privacy policy | Terms of use

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries. Kubernetes is the registered trademark of the Linux Foundation.

General Inquiries: +1 (650) 389-6000,