Cube Consumption Unit
Cube Consumption Unit (CCU) is a way to measure resource consumption used to run Cube Cloud infrastructure and resources within it. The price of a CCU is determined by the product tier you’re subscribed to. Each product tier determines the features, scalability, availability, as well as the speed and scope of support you may receive for your deployment. You can also set Budgets to make sure you know your usage is on track and as expected.Payment plans
Payment plans determine whether you have a fixed-term contract or a recurring subscription:- On-demand payment plan allows you to subscribe at any time, add your credit card, and start using Cube Cloud right away. Starter and Premium product tiers are available on the on-demand payment plan.
- Commit payment plan allows you to have a contract with a CCU amount specified in that contract. Premium and Enterprise product tiers are available on the commit payment plan. Contact us to learn more.
Product tiers
Free
Free product tier is designed for development and testing purposes. It is not intended for production use. It offers up to two Shared deployments. You can review its support terms and limits.Starter
Starter product tier targets low-scale production that is not business-critical. It offers a Dedicated deployment, the ability to use third-party packages from the npm registry, AWS, GCP, and Azure support in select regions, pre-aggregations of up to 150GB in size, auto-suspend controls, and Semantic Layer Sync with a single BI tool (such as Preset or Metabase). You can review its pricing, support terms, and limits.Premium
Premium product tier is designed for basic small-scale production deployments. It offers everything in the Starter product tier as well as enabling the use of Multi-cluster deployments, support for custom domains, AWS, GCP, and Azure support in all regions. Cube Cloud provides a 99.95% uptime SLA for this product tier. You can review its pricing, support terms, and limits.Enterprise
Enterprise product tier is suitable for high-scale or mission-critical production deployments with more significant security and compliance needs. It offers everything in the Premium product tier as well as Semantic Layer Sync with unlimited supported BI tools, SAML support for single sign-on, dedicated infrastructure, VPC peering, monitoring integrations, and role-based access control. Cube Cloud provides a 99.99% uptime SLA for this product tier. You can review its pricing, support terms, and limits.Resources
The following resource types incur CCU consumption and apply to individual resources of deployments within a Cube Cloud account. The consumption is measured in 5-minute intervals.
The following resource types incur CCU consumption and apply to the whole Cube Cloud
account:
The following resource types incur cost and apply to the whole Cube Cloud account:
Deployment tiers
Dedicated deployments (including individual API instances) and Shared deployments are involved in serving requests through APIs & integrations under the following tiers:
You can upgrade to a chosen tier in the
Settings of your deployment.
Upgrading to the M tier is only available on the Enterprise product tier.
Cube Store Worker tiers
Cube Store workers are involved in building pre-aggregations and executing queries against them under the following tiers:
You can upgrade to a chosen tier in the
Settings of your deployment.
Query History tiers
Query History and Performance Insights features analyze and visualize the data available under the following tiers:
You can upgrade to a chosen tier in the
Settings of your deployment.
Monitoring Integrations
Monitoring Integrations, including Query History export, are available as an add-on on the Enterprise plan. [Contact us][cube-contact-us] for pricing.Audit Log tiers
Audit Log collects, stores, and displays security-related events under the following tiers:AI tokens
The price of AI tokens is passed through from the underlying AI service provider without any markup. The cost depends on the number of tokens processed by your Cube Cloud account when using AI features. You can control the const by setting the token limit on the Billing page of your Cube Cloud account. When the limit is reached, you can increase it to continue using AI features.Total cost examples
The following examples provide insight into the total cost to use Cube Cloud:- Small-scale deployment (Dedicated deployment, Premium product tier, S deployment tier).
- Medium-scale deployment (Dedicated deployment with auto-scaling, Enterprise product tier, S deployment tier).
- Large-scale deployment (Multi-cluster deployment with single-tenant infrastructure, Enterprise product tier, M deployment tier).
Small-scale deployment
Suppose a company uses Cube Cloud to power self-serve business intelligence for a couple of teams in Eastern and Pacific time zones. This organization:- Uses the Premium product tier of Cube Cloud.
- Runs a single Dedicated deployment (S tier) that is active 24/7 but never has to auto-scale its API instances because the usage is spread evenly with no bursts.
- Operates on a small volume of data that requires the usage of just 2 Cube Store Workers to run queries and refresh pre-aggregations mostly during working hours, being active approximately 50% of the time.
- Updates its data model infrequently and without using a dedicated Shared deployment for testing purposes, with 2 data engineers spending just 1 hour a day each, in the development mode of the Dedicated deployment.
Medium-scale deployment
Suppose a company with a globally distributed workforce uses Cube Cloud to enable self-serve exploration in multiple BI tools and AI agents; it also uses Cube Cloud to power embedded analytics in its SaaS platform that caters to a vast worldwide customer base. This organization:- Uses the Enterprise product tier of Cube Cloud.
- Runs two Dedicated deployments (S tier) that are active 24/7 and auto-scale up to 8 API instances during a peak hour every day.
- Operates on a moderate volume of data that requires the usage of 4 Cube Store Workers by both Dedicated deployments to run queries and refresh pre-aggregations 24/7, being active approximately 50% of the time.
- Uses a dedicated Shared deployment (S tier) for testing purposes that is active 12 hours a day.
- Has a team of 5 data engineers who frequently update the data model, with each data engineer spending about 4 hours a day in the development mode of the dedicated Shared deployment.
Large-scale deployment
Suppose a company uses Cube Cloud as a mission-critical part of their infrastructure to enable its globally distributed workforce, customer base, and (or) partners to operate at scale. This organization:- Uses the Enterprise product tier of Cube Cloud.
- Uses single-tenant infrastructure.
- Runs a Multi-cluster deployment that is active 24/7, includes 3 Dedicated deployments (M tier), with each Dedicated deployment auto-scaling up to 10 API instances during a few peak hours every day.
- Operates on a large volume of data that requires the usage of 16 Cube Store Workers to run queries and refresh pre-aggregations 24/7, being active approximately 50% of the time.
- Uses a dedicated Shared deployment (M tier) for testing purposes that is active 24 hours a day.
- Has a team of 10 data engineers who frequently update the data model, with each data engineer spending about 4 hours a day in the development mode of the dedicated Shared deployment.
- Uses a Query History tier with 14-day data retention to inform the work of data engineers.
Payment terms
Upgrades
You may upgrade your CCUs to a higher-level product tier at any time by paying the difference in per-Cube Consumption Unit pricing, or by asking to convert the price paid for the remaining CCUs into CCUs for the higher product tier at the CCU pricing for that product tier (resulting in a lower number of available CCUs but upgraded to the higher product tier).Terms
If payment is not received within the contract terms (usually Net-30) or for additional required payment for CCUs exceeding the balance of CCUs in your account, services may degrade or be suspended until new CCUs are purchased. Future purchases and upgrades are subject to the pricing that is in effect at the time of the order. No credit is allowed for downgrading CCUs to a lower product tier level. Payments are non-refundable.Troubleshooting
Token limit exceeded
On-demand customers may encounter the following error when their AI
usage exceeds the limit set for their Cube Cloud account: Token limit exceeded. Please purchase or allocate more tokens.
To resolve this issue, a user with administrative permissions needs to increase the limit
for the AI token consumption at the Billing page of their Cube Cloud account.