Pricing snapshot
Scroll sideways to see all columns. With a keyboard, focus this table and use the arrow keys.
| Decision point | What Yellowbrick states |
|---|---|
What you pay Yellowbrick for | Data Warehouse Software, priced per vCPU; the rate depends on whether you subscribe for a set number of vCPUs or use on-demand pricing |
Deployment | Your own AWS, Azure or GCP cloud account, or your on-premises datacenter |
Infrastructure | Every rate is software plus your cloud or on-prem costs; you pay your own cloud infrastructure bills |
Support | Global 24×7 support is always included, with no additional support charges |
Trial | The pricing page offers "Start a Trial"; trial length and capacity are for Yellowbrick to confirm |
Which option fits your workload
Subscription. Yellowbrick's FAQ says subscriptions make sense when a cluster runs for more than 25% of the time, or when you want to stay within a fixed data warehouse budget.
On demand. The same FAQ points to on-demand for a workload that runs only a few hours a week, or for burst capacity above your subscription for a limited time, such as quarter end.
Both. You can combine the two. Yellowbrick says customers often use on-demand for periodic ETL or bursting workloads and a subscription for 24/7 query processing.
Published software rates
Scroll sideways to see all columns. With a keyboard, focus this table and use the arrow keys.
| Option | Published price | Term and billing |
|---|---|---|
Subscription, one year ("Predictable Value") | $613 per vCPU / year | One-year term for a chosen maximum number of vCPUs |
Subscription, three years ("Guaranteed 3-Year Price") | $482 per vCPU / year | Three-year term with a guaranteed price, for a chosen maximum number of vCPUs |
On-demand ("Burst Pricing") | $0.28 per vCPU / hour | Per-second metering, billed monthly |
How the software charge works
A subscription lets you use Yellowbrick up to the maximum number of vCPUs you chose for the subscription period, at a flat rate. Yellowbrick says there are no "unused vCPU hours", so idle time does not roll forward. On-demand charges follow the vCPUs you actually run, to the second. Node size does not set the price by itself, but if a node change alters the vCPU count, the price could be different depending on which pricing option you use.
Software-cost examples
These are hypothetical inputs to show the arithmetic, not suggested sizes. Each result covers Yellowbrick software only and excludes your cloud or on-prem infrastructure.
Scroll sideways to see all columns. With a keyboard, focus this table and use the arrow keys.
| Hypothetical inputs | Working | Software-only result |
|---|---|---|
16 vCPUs, one-year subscription | 16 × $613 per vCPU / year | $9,808 per year, before infrastructure |
16 vCPUs, three-year subscription | 16 × $482 per vCPU / year | $7,712 per year on a three-year term, before infrastructure |
16 vCPUs run for 100 hours in a month, on demand | 16 × 100 × $0.28 per vCPU / hour | $448 for that month, before infrastructure |
16 vCPUs run for 500 hours in a month, on demand | 16 × 500 × $0.28 per vCPU / hour | $2,240 for that month, before infrastructure |
The same 16 vCPUs give different on-demand charges as runtime changes, so measure how many hours your clusters run before you commit.
What moves the software bill
Clusters you suspend, resume or scale. Yellowbrick lets you suspend, resume and scale instances and compute clusters through SQL or a web app. Its pricing FAQ says the software cost depends on how many vCPUs you are using when running.
Workload management. Yellowbrick says its workload management helps maximize vCPU value and reduce the need to scale.
Costs outside the software rate
Your cloud account. Yellowbrick installs into your own cloud account with data on your own object storage. You pay for that cloud storage and compute using your own contracts and credits.
On-premises hardware. On-premises infrastructure subscriptions are available to buy from Yellowbrick; contact sales@yellowbrick.com for details.
Our take
If you can measure a steady vCPU baseline that runs much of the time, a subscription sized to that baseline with on-demand for peaks keeps the software line predictable. Budget infrastructure as its own line either way: the subscription fixes only what you pay Yellowbrick.