Billing structure
Imply Polaris follows a consumption-based pricing model. Polaris tracks usage across the following billing dimensions, each representing a billable unit:
Project size
Polaris meters the number of hours a project is operating as measured at the beginning of the hour. Monthly project size resource consumption is calculated by multiplying the project size list price by the number of hours in the month.
You can choose between starter, series A, and series D project sizes:
- The starter project size is best suited for functional evaluation of Polaris during trial or proof of concept. It is limited to 25 GB storage capacity, 4 vCPU, and 16 GB memory.
- Series A are best suited for compute-intensive analytical workloads that power critical business applications.
- Series D are best suited for storage-intensive production applications with lower cost and moderate performance needs relative to the amount of queryable data.
The following table shows series A project sizes:
| Project size | Capacity | vCPU allocation | Memory |
|---|---|---|---|
| A.01 | 100 GB | 14 vCPU | 80 GB RAM |
| A.02 | 200 GB | 24 vCPU | 144 GB RAM |
| A.04 | 400 GB | 28 vCPU | 175 GB RAM |
| A.08 | 800 GB | 36 vCPU | 275 GB RAM |
| A.12 | 1,200 GB | 64 vCPU | 450 GB RAM |
| A.16 | 1,600 GB | 72 vCPU | 550 GB RAM |
| A.24 | 2,400 GB | 108 vCPU | 825 GB RAM |
| A.32 | 3,200 GB | 144 vCPU | 1100 GB RAM |
| A.48 | 4,800 GB | 216 vCPU | 1650 GB RAM |
| A.64 | 6,400 GB | 288 vCPU | 2200 GB RAM |
| A.96 | 9,600 GB | 440 vCPU | 3300 GB RAM |
The following table shows series D project sizes:
| Project size | Capacity | vCPU allocation | Memory |
|---|---|---|---|
| D.04 | 400 GB | 8 vCPU | 48 GB RAM |
| D.08 | 800 GB | 12 vCPU | 80 GB RAM |
| D.12 | 1,200 GB | 20 vCPU | 140 GB RAM |
| D.16 | 1,600 GB | 24 vCPU | 160 GB RAM |
| D.24 | 2,400 GB | 30 vCPU | 210 GB RAM |
| D.32 | 3,200 GB | 40 vCPU | 280 GB RAM |
| D.48 | 4,800 GB | 60 vCPU | 420 GB RAM |
| D.64 | 6,400 GB | 80 vCPU | 560 GB RAM |
| D.96 | 9,600 GB | 120 vCPU | 840 GB RAM |
If you are unsure of your data usage, sign up for a free trial to ingest and size your data. After you move out of the trial and become a paid customer, you can select from the following default project sizes: starter, A.01, A.02, A.04, A.08, D.04, D.08, D.12. To change to a different project size, contact Imply.
Data ingestion
Polaris ingestion autoscales to meet your needs. You only pay for the raw bytes of data that Polaris processes during ingestion.
Imply measures and bills your monthly consumption of batch and streaming ingestion resources using the following tiered model:
- First terabyte (1000 GB) in a month.
- Next 9 terabytes (9000 GB) in a month.
- Anything over 10 terabytes in a month.
The list price for streaming ingestion is the same irrespective of the streaming ingestion source. For a list of supported streaming ingestion sources, see Ingestion sources.
File storage
When you upload your raw data to the Polaris staging area, Polaris stores the raw data in Amazon S3 buckets. You can ingest the entire raw data or a subset of raw data from the staging area to a Polaris table. Monthly file storage resource consumption is calculated by multiplying the file storage list price by the total volume of data stored (in GB-month).
Learn more
See the following topics for more information:
- Imply Polaris pricing for current pricing.
- Polaris plans for reference on the Polaris service plans.
- Monitor account usage for information on monitoring account usage from the Polaris UI.