Imply Polaris is a real-time database for modern analytics applications. Built from Apache Druid and delivered as a fully managed database as a service (DBaaS), Polaris drives time-to-value and usability.
With Polaris, there is no sizing or planning required to deploy and scale a distributed database. In fact, Polaris offers a free full-feature 30-day trial, so you can start loading data and extracting insights in no time.
This topic provides general information about the pricing and billing components of Polaris. For information on the free trial and paid plans, see Polaris plans. For pricing details, visit Imply Polaris Pricing.
The pricing structure of Polaris follows a consumption-based model. Specifically, Polaris tracks your usage across the following dimensions, each representing a billable unit:
Keep reading to learn more about each of the billing dimensions.
Polaris meters the number of hours a project is operating as measured at the beginning of the hour.
The following table shows Polaris Project Tiers:
|Project Tier||Capacity||vCPU allocation||Memory|
|a.02||200 GB||16 vCPU||112 GB RAM|
|a.04||400 GB||28 vCPU||208 GB RAM|
|a.08||800 GB||56 vCPU||416 GB RAM|
|a.12||1,200 GB||84 vCPU||624 GB RAM|
|a.16||1,600 GB||112 vCPU||832 GB RAM|
To determine the Polaris Project Tier size suitable for your use case, first identify your required storage capacity.
If you know your data usage requirements, select a Project Tier with a data capacity that satisfies your use case. If your project’s capacity is larger than 1,600 GB, contact Imply to discuss your custom data sizing requirements.
If you are unsure of your use case data sizing, consider signing up for a free trial to ingest and size the data. Alternatively, you can contact Imply to discuss your use case, schemas, queries, and tables for an accurate recommendation.
Unit of measure: per hour
Consider the following example of how Polaris calculates a.08 Project Tier costs for the month of October.
An a.08 Project Tier costs $10.40 per hour.
There are 744 hours in October.
$10.40 /hr * 744 hrs = $7,737.60
Total Project Tier cost for October: $7,737.60
Batch Data Ingestion
Batch ingestion is a way to load data into Polaris as batch files.
Polaris calculates the consumption of Batch Data resources based on the amount of data you ingest into Polaris.
Unit of measure: per GB
Consider the following example of how Polaris calculates Batch Data Ingestion costs for the month of October.
On October 1, you bulk ingest 200 GB of historical data. You also ingest 40 GB of additional batch data daily.
$0.30 /GB * 200 GB = $60
$0.30 /GB * 40 GB/day * 31 days = $372
Total Batch Data Ingestion cost for October = $432
Streaming Data Ingestion
Push stream ingestion loads your data from a source data stream directly into a destination table in Polaris using the Events API. For more information on how to push data from an application source, see Push event data by API.
Polaris calculates the consumption of Streaming Data resources based on the amount of data you stream into Polaris.
Unit of measure: per GB
Consider the following example of how Polaris calculates Streaming Data Ingestion costs for the month of October.
In October, you ingest 30 GB of streaming data every day.
$0.60 /GB * 30 GB/day * 31 days = $558
Total Streaming Data Ingestion cost for October = $558
Raw data is stored in Amazon S3 buckets. You can load the entire raw data or a subset of raw data from S3 buckets to your Polaris Project Tier. File Storage charges are based on the total volume of data stored in Amazon S3.
Unit of measure: per GB-month
Consider the following example of how Polaris calculates File Storage costs for the month of October.
In October, you store a total of 270 GB of data in an Amazon S3 bucket.
$0.06 /GB-month * 270 GB-month = $16.20
Total File Storage cost for October = $16.20