Pricing and billing

Learn about the pricing model and billing structure for DataStax Apollo on Constellation.

Learn about the pricing model and billing structure for DataStax Apollo on Constellation.

Pricing

Pricing for DataStax Apollo on Constellation is based on capacity unit (CU) and Service Tier.

Each Apollo database (except on the Developer tier) uses a single CU by default, which represents three database nodes that are grouped together. A single CU represents three replicas of approximately 500 GB of data.

The Service Tier represents the amount of compute power allocated to each CU, and represents three compute instances per CU. DataStax Apollo on Constellation provides the following Service Tiers:

  • Developer: low-cost development option, 25 GB storage.
  • Startup: starter configuration for development and light production workloads.
  • Standard: higher throughput, lower latency, 99.9% uptime SLA, plus support.
  • Enterprise: highest throughput, lowest latency, 99.99% uptime SLA, and best support tier.

To calculate cost, multiply the number of CUs by the Service Tier price. Pricing is presented in the DataStax Constellation console in hourly terms, but billed in one-minute granularity.

Billing

The DataStax Constellation console handles billing through an integration with Stripe, and displays all related billing information on the Billing Summary page. Enter a credit card number and associated billing information to begin creating Apollo databases.

In the main taskbar, click your username and select View My Bills. This page includes the following information:

  • Subscription name
  • Quantity of active subscriptions
  • Price per unit
  • Total cost
Note: This summary is an approximation of your current charges before taxes, and might not reflect total database usage.

Each user is tied to a single organization. The first user that creates the organization becomes the default billing contact. Because the first user is the default billing contact, they must provide a credit card and associated billing information. After adding more users to the organization, the billing contact can be transferred to a different user. When changing billing contacts, update payment methods to reflect the credit card and address of the billing contact.

The estimated cost per month is estimated from historical usage trends. The number of CUs in use, selected Service Tier, and number of active Apollo databases impact the total cost, which the estimate seeks to track.

You will be billed monthly based on Greenwich Mean Time (GMT).