Billing overview
Imply Polaris operates on a consumption-based pricing model. Each project is billed based on the project size, batch and streaming ingestion volumes, the amount of file storage and deep storage used, and asynchronous (async) queries.
Users with the AdministerBilling permission can view total accrued charges and per-project usage charges in the Billing page of the Polaris UI.
For current pricing, see Imply Polaris pricing.
Billing dimensions
Polaris tracks usage across the following billing dimensions:
Project size
Polaris measures the number of hours a project has been operating, starting at the beginning of each hour. Monthly project size resource consumption is calculated by multiplying the project size price by the total number of hours used in the month.
You can choose between starter, series A, and series D project types:
- The starter project 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.
Series A
The following table shows series A project sizes:
| Project size | Capacity | vCPU allocation | Memory |
|---|---|---|---|
| A.01 | 100 GB | 10 vCPU | 64 GB RAM |
| A.02 | 200 GB | 20 vCPU | 128 GB RAM |
| A.04 | 400 GB | 24 vCPU | 160 GB RAM |
| A.08 | 800 GB | 40 vCPU | 288 GB RAM |
| A.12 | 1,200 GB | 60 vCPU | 432 GB RAM |
| A.16 | 1,600 GB | 76 vCPU | 560 GB RAM |
| A.24 | 2,400 GB | 108 vCPU | 816 GB RAM |
| A.32 | 3,200 GB | 144 vCPU | 1088 GB RAM |
| A.48 | 4,800 GB | 216 vCPU | 1632 GB RAM |
| A.64 | 6,400 GB | 320 vCPU | 2432 GB RAM |
| A.96 | 9,600 GB | 432 vCPU | 3264 GB RAM |
Series D
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 | 128 GB RAM |
| D.16 | 1,600 GB | 24 vCPU | 160 GB RAM |
| D.24 | 2,400 GB | 32 vCPU | 224 GB RAM |
| D.32 | 3,200 GB | 40 vCPU | 288 GB RAM |
| D.48 | 4,800 GB | 60 vCPU | 432 GB RAM |
| D.64 | 6,400 GB | 76 vCPU | 560 GB RAM |
| D.96 | 9,600 GB | 112 vCPU | 832 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 measures your consumption of batch and streaming ingestion resources based on the processed bytes, which refer to the uncompressed size of your input data in a successful ingestion job. The processed size may differ from the original input size due to format and compression.
Polaris bills you for every ingestion job even if you're ingesting the same data into different tables. For example, if you ingest a stream as both detailed and aggregate tables, this increments the billable processed bytes twice. Reingesting data that already exists in Polaris also increases your billable processed bytes.
Batch and streaming ingestion resources are measured and billed independently 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 price for streaming ingestion remains the same regardless of the streaming ingestion source. For supported streaming ingestion sources, see Ingestion sources.
File storage
Polaris charges you for file storage when you upload files to the staging area for batch ingestion. File storage consumption is calculated by multiplying the file storage price by the total volume of data stored per month (in GB-month).
Deep storage
Deep storage encompasses all persisted data, including precached and noncached data. When you query deep storage data, the results also include real-time data. Unlike data loaded into precache, data stored in deep storage doesn't count towards your project size. It is billed at a much lower rate, making it a cost effective solution for long term data retention.
Polaris calculates deep storage consumption by multiplying the deep storage price by the total data volume stored per month (in GB-month).
To reduce costs and conserve resources, especially for infrequently accessed data, you can implement a precache policy to automatically stop caching older data. For information on precache policies, see Data lifecycle management.
Async query
Polaris measures the compute resources consumed by async queries in Data Processing Unit (DPU) minutes. A DPU is a normalized unit of processing power in Polaris. One DPU-minute corresponds to one task consuming one DPU for one minute. Each async query task running for one minute is billed as one DPU-minute.
Because async queries run on dedicated hardware that Polaris provisions on demand, you only pay for the query while it’s running, without any ongoing computing or maintenance costs.
You can manage how many compute resources an async query consumes by controlling task concurrency. Higher concurrency typically results in faster execution times. For instance, a query with a concurrency of two that takes 12 minutes to execute can take around six minutes with a concurrency of four.
Cloud provider marketplace
The method you use to sign up for Polaris determines how your organization is billed. If you sign up directly on Polaris, Polaris bills you for the resources you consume. If you sign up through a cloud provider, the provider manages all billing and invoicing for your Polaris subscription. For current provider pricing, refer to the Polaris marketplace listing on Amazon Web Services (AWS) and Microsoft Azure. To change your billing method, contact Polaris support.
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.