|
| 1 | +--- |
| 2 | +title: Pricing |
| 3 | +permalink: /cloud/pricing |
| 4 | +category: Pricing |
| 5 | +menuOrder: 20 |
| 6 | +--- |
| 7 | + |
| 8 | +Cube Cloud pricing is based on consumption of compute power which we measure |
| 9 | +using Cube Compute Units. The units are priced based on which subscription plan |
| 10 | +you have chosen. Each plan has different features and functionality that you |
| 11 | +should review as you think about what is right for your business. |
| 12 | + |
| 13 | +<InfoBox heading="What's a Cube Compute Unit?"> |
| 14 | + |
| 15 | +A **Cube Compute Unit** is a way to measure compute power used to run Cube Cloud |
| 16 | +infrastructure. The price of a compute unit is determined by the Cube Cloud plan |
| 17 | +you're subscribed to. |
| 18 | + |
| 19 | +</InfoBox> |
| 20 | + |
| 21 | +| Node Type | Compute Unit per hour | |
| 22 | +| ------------------------- | :-------------------: | |
| 23 | +| Cube Production Cluster | `4` | |
| 24 | +| Cube Development Instance | `1` | |
| 25 | +| Cube Store Worker | `1` | |
| 26 | +| Cube API Instance | `1` | |
| 27 | + |
| 28 | +Cube Cloud has four subscription plans that you can review |
| 29 | +[here](https://cube.dev/pricing). The subscription plan you choose will |
| 30 | +determine the price per Cube Compute Unit (CCU). Each subscription plan |
| 31 | +determines the features, scalability, availability, as well as the speed and |
| 32 | +scope of support you may receive for your deployment. |
| 33 | + |
| 34 | +## Starter |
| 35 | + |
| 36 | +The Starter Plan starts at a minimum of $99/month and targets low-scale |
| 37 | +production that is not business-critical. |
| 38 | + |
| 39 | +It offers a production cluster, the ability to use third-party packages from the |
| 40 | +npm registry, AWS and GCP support in select regions, pre-aggregations of upto |
| 41 | +150GB in size, alerts, auto-suspend controls and a 50,000 queries per day limit. |
| 42 | + |
| 43 | +### Support |
| 44 | + |
| 45 | +The Starter plan includes support via the community Slack channel and chat |
| 46 | +support with three questions per week. |
| 47 | + |
| 48 | +| Priority | Response Time | |
| 49 | +| -------- | ---------------- | |
| 50 | +| P0 | 8 business hours | |
| 51 | +| P1 | 8 business hours | |
| 52 | +| P2 | 8 business hours | |
| 53 | +| P3 | 2 business days | |
| 54 | + |
| 55 | +## Premium |
| 56 | + |
| 57 | +The Premium plan starts at a minimum of $12,000/year, and is designed for |
| 58 | +mission-critical production deployments. |
| 59 | + |
| 60 | +It offers everything in the [Starter plan](#starter) as well as a dedicated VPC, |
| 61 | +Okta support for single sign-on and AWS, GCP, and Azure support in all regions, |
| 62 | +a dedicated VPC, and unlimited queries. |
| 63 | + |
| 64 | +### Support |
| 65 | + |
| 66 | +The Premium plan includes support via the community Slack channel and unlimited |
| 67 | +chat support on weekdays. Cube Cloud provides a 99.95% uptime SLA for this plan. |
| 68 | + |
| 69 | +| Priority | Response Time | |
| 70 | +| -------- | ---------------- | |
| 71 | +| P0 | 60 minutes | |
| 72 | +| P1 | 4 hours | |
| 73 | +| P2 | 8 business hours | |
| 74 | +| P3 | 2 business days | |
| 75 | + |
| 76 | +## Enterprise |
| 77 | + |
| 78 | +The Enterprise plan starts at a minimum of $18,000/year, and is suitable for |
| 79 | +high-scale or mission-critical production with security and compliance needs. |
| 80 | + |
| 81 | +It offers everything in the [Premium plan](#premium) as well as SAML/LDAP |
| 82 | +support for single sign-on, VPC peering, and logs/metrics export. |
| 83 | + |
| 84 | +### Support |
| 85 | + |
| 86 | +The Enterprise plan offers improved support response times as compared to the |
| 87 | +[Premium plan](#premium-support) with the addition of a dedicated CSM. Cube |
| 88 | +Cloud provides a 99.99% uptime SLA for this plan. |
| 89 | + |
| 90 | +| Priority | Response Time | |
| 91 | +| -------- | ---------------- | |
| 92 | +| P0 | 30 minutes | |
| 93 | +| P1 | 2 hours | |
| 94 | +| P2 | 8 business hours | |
| 95 | +| P3 | 2 business days | |
| 96 | + |
| 97 | +## Enterprise Premier |
| 98 | + |
| 99 | +The Enterprise Premium Plan caters to high-scale, high-availability |
| 100 | +mission-critical production deployments with security and compliance needs. |
| 101 | + |
| 102 | +It offers everything in the Enterprise plan as well as enabling the use of |
| 103 | +production multi-clusters, unlimited pre-aggregation sizes and custom domains. |
| 104 | + |
| 105 | +### Support |
| 106 | + |
| 107 | +The Enterprise Premier plan includes the same |
| 108 | +[support plan as the Enterprise plan](#enterprise-support). Cube Cloud provides |
| 109 | +a 99.995% uptime SLA for this plan. |
| 110 | + |
| 111 | +| Priority | Response Time | |
| 112 | +| -------- | ---------------- | |
| 113 | +| P0 | 30 minutes | |
| 114 | +| P1 | 2 hours | |
| 115 | +| P2 | 8 business hours | |
| 116 | +| P3 | 2 business days | |
| 117 | + |
| 118 | +## Payment Terms |
| 119 | + |
| 120 | +Future purchases and upgrades are subject to the pricing that is in effect at |
| 121 | +the time of the order. Payments are non-refundable. If your usage of resources |
| 122 | +exceeds the balance of CCUs in your account, services may degrade or be |
| 123 | +suspended until new CCUs are purchased. You may upgrade your CCUs to a |
| 124 | +higher-level subscription plan at any time by paying the difference in per-Cube |
| 125 | +Compute Unit pricing, or by asking to convert the price paid for the remaining |
| 126 | +CCUs into CCUs for the higher subscription plan at the CCU pricing for that plan |
| 127 | +(resulting in a lower number of available CCUs but upgraded to the higher |
| 128 | +subscription plan). No credit is allowed for downgrading CCUs to a lower |
| 129 | +subscription plan level. |
| 130 | + |
| 131 | +## Support Priority |
| 132 | + |
| 133 | +We prioritize support requests based on their severity, as follows: |
| 134 | + |
| 135 | +- **P0**: The platform is severely impacted or completely shut down. We will |
| 136 | + assign specialists to work continuously to fix the issue, provide ongoing |
| 137 | + updates, and start working on a temporary workaround or fix. |
| 138 | + |
| 139 | +- **P1**: The platform is functioning with limited capabilities or facing |
| 140 | + critical issues preventing a production deployment. We will assign specialists |
| 141 | + to fix the issue, provide ongoing updates, and start working on a temporary |
| 142 | + workaround or fix. |
| 143 | + |
| 144 | +- **P2**: There are issues with workaround solutions or non-critical functions. |
| 145 | + We will use resources during local business hours until the issue is resolved |
| 146 | + or a workaround is in place. |
| 147 | + |
| 148 | +- **P3**: There is a need for clarification in the documentation, or a |
| 149 | + suggestion for product enhancement. We will triage the request, provide |
| 150 | + clarification when possible, and may include a resolution in a future update. |
0 commit comments