Pricing

Simple, transparent, pay-as-you-go pricing with no upfront commitment

Compute

$0.35/FBU/hour 

* FBU - Firebolt Unit
Multidimensional elasticity

Each cluster can be scaled in single-node increments from 1-128. Additionally, each Engine can scale from 1-10 clusters to address concurrency requirements.

On demand
Per-second billing

Storage

$23/TB/month

AWS S3 list-price - no additional charge
Columnar compression
Hybrid & indexed
Zero management

Free support included for all users

Save on Compute

Tune compute resources to your workload for optimized cost and performance

Node type
Number of nodes
Select between 1-128 compute nodes.
Number of clusters
Add up to 10 clusters to increase query concurrency.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
FBUs per hour
24
FBU
Cost per hour
XX

Simple pricing

Pay for FBUs (Firebolt Units) consumed multiplied by run time (calculated per-second).

Control spend with multidimensional elasticity

Start with a single node ‘S’ type engine and scale in one-node increments up to 128.

*Consumed FBU = (Available FBU per hour / 3600) * (Engine runtime in seconds)

Pricing Examples

The following is a sample analytics lifecycle comprised of multiple workloads sharing the same storage

The data journey starts with ingesting data from external sources.

Ingestion requires a single node engine with node type S that runs for 6 minutes every hour. Node type S consumes 8 FBUs/hour.

Engine Configuration
Runtime: 6 min every hour

6 min

Start Engine
Stop Engine
Daily Runtime
8AM
5PM

Cost = $6.72 (19.2 FBUs)

8 FBUs/hr/60 x 6 min run x 24 hrs

Building dashboards for business intelligence

BI workloads run at infrequent intervals with extended idle periods. We launch an engine of node type M. On average, this workload runs for 10 minutes each hour, with 5 minutes of idle time.

Engine Configuration
Runtime: 10 min/hr + 5 min idle

10 min

5 min idle

45 min stopped

10 min

Start
Stop
Analytics
Analytics
Start
Daily Runtime
8AM
5PM

Cost = $33.60 (96 FBUs)

16 FBUs/hr/60 x (10 min run + 5 min idle ) x 24 hrs

Data modeling at scale

ELT workload runs on an engine with a single S node (8 FBUs/hr) for 10 minutes every hour. This ELT workload scales out to 4 S nodes (32 FBUs/hr) once a day for a period of an hour.  

Engine Configuration
Runtime

10 min

5 min idle

60 min

10 min

Start
Online Engine Scale-out
ELT
ELT
ELT
Online Engine Scale-in
Stop
Daily Runtime
8AM
5PM

Cost = $27.30 (78 FBUs)

23 hrs x 8 FBUs/hr x (10 min run + 5 min idle)/60 + 32 FBUs/hr

Serving low-latency analytics to customers at high concurrency via data apps

The baseline engine is a 2-node cluster of S type nodes that runs 24 x 7. To address high concurrency, this engine adds another 2-node cluster from 9am - 5pm.

Engine Configuration
Runtime

Cluster 2 (9am - 5pm)

Cluster 1 (24x7)

Concurrency Scaling
Concurrency Scaling
Daily Runtime
8AM
5PM

Cost = $179.20 (512 FBUs)

16 FBUs/hr x 16 hrs + 32 FBUs/hr x 8 hrs

All workloads

Daily Runtime
Ingest
BI
ELT
Customer-facing analytics
8AM
5PM
19.2 FBUs/day
96 FBUs/day
78 FBUs/day
512 FBUs/day

Total consumption per day: 705.2 FBUs

Total cost per day = $246.82

Workload isolation

Distributed writes

Global consistency

Simple Storage Pricing

$23/TB/month regardless of workloads or engines running

Columnar compression

Hands-free columnar format enables cost-efficient scaling.

Hybrid & indexed

Efficient indexing saves on storage costs while improving data access speed.

Zero management

Storage is fully managed by Firebolt, so there’s no need to perform storage tasks.

FAQ

What is a Firebolt Unit (FBU)?

+

Firebolt Unit is a normalized measurement of consumption. FBU normalizes consumption management irrespective of node type, number of nodes, number of clusters, duration of consumption, etc. Thanks to Firebolt’s multidimensional scaling, per-second billing, and auto-stop/start capabilities, compute consumption can be a fraction of a minute. FBU eliminates the need to keep track of individual node types, nodes, and the number of clusters. There’s no binding to specific instance types, so you are free to use pre-paid credits on any node type.

You can't run a data warehouse with a small team.

+

Yes you can.

With Firebolt's amazing performance, neither development nor administration professionals need to waste time with unnecessary processes like complicated ingest, caching layers or esoteric data languages.  You can run a lean and mean team that consistently delivers value to customers.

Does a given number of FBUs provide the same performance profile irrespective of configuration?

+

While FBUs measure consumption, the performance profile of a workload depends on the engine topology.

Speed, capacity, ease of use.  You can't have all three

+

Yes you can.

We've spent a lot of time working on all three.
1. Firebolt is natively efficient due to indexing.
2. With separated storage and compute, data volume increases don't linearly increase compute.
3. With a very user friendly GUI, numerous APIs and SDKs, and allowing all activities to happen in very familiar SQL, it's a very natural platform.

You can’t give your customer facing apps direct access to your data warehouse

+

Yes you can.

Firebolt is designed to handle massive concurrency.  It’s more than capable of supporting customer facing applications.  And if the workload increases, just scale your engines.

How is per-second billing calculated?

+

Each node type consumes a specified number of FBUs per hour. Compute consumption is billed in one-second increments. For example, a type ‘M’ node consumes 16 FBUs per hour. The same node running for one minute will consume FBU calculated as such: Consumed FBU = (Available FBU per hour / 3600) x ( 1 x 60 seconds) = (16/3600) x 60 = 0.27 FBUs.

When does consumption measurement start?

+

Consumption starts when the engine endpoint is available for querying.

What regions does Firebolt support?

+

US-EAST-1 and EU-WEST-1 (coming soon).

Does Firebolt offer commitment-based discounts?

+

Yes, commitment based discounts are available. Contact our sales team for more information.

How does Firebolt help control costs?

+

Firebolt provides multidimensional scaling to help right-size workloads. Autostop and Autostart are features that help reduce costs by eliminating idle time. Firebolt also provides global visibility of consumption and costs through built-in organizational governance and account-level consumption breakdown.

How does Firebolt provide visibility into spend?

+

Firebolt provides engine consumption and spend information in the Web UI. Additionally, granular engine-level consumption can be found via the information_schema.engine_metering_history view that details the hourly consumption of all the engines within an account. Users can also drill down into how the topology of their engines (node type, number of nodes and number of clusters) was modified over time, providing visibility into the FBU consumption of their engines.

Free trial

Free support

Free sample datasets

No credit card needed

We use cookies to give you a better online experience
Got it