• Developer guide
  • API reference

›Billing

Getting started

  • Introduction to Imply Polaris
  • Quickstart
  • Execute a POC
  • Create a dashboard
  • Navigate the console
  • Key concepts

Tables and data

  • Overview
  • Introduction to tables
  • Table schema
  • Create an ingestion job
  • Timestamp expressions
  • Data partitioning
  • Introduction to rollup
  • Approximation algorithms
  • Replace data

Ingestion sources

  • Ingestion sources overview
  • Supported data formats
  • Create a connection
  • Ingest from files
  • Ingest data from a table
  • Ingest from S3
  • Ingest from Kafka and MSK
  • Ingest from Kinesis
  • Ingest from Confluent Cloud
  • Kafka Connector for Imply Polaris
  • Push event data
  • Connect to Confluent Schema Registry

Analytics

  • Overview
  • Manage data cubes
  • Visualize data
  • Data cube dimensions
  • Data cube measures
  • Dashboards
  • Visualizations reference
  • Set up alerts
  • Set up reports
  • Embed visualizations
  • Query data

Monitoring

  • Overview

Management

  • Overview
  • Pause and resume a project

Billing

  • Overview
  • Polaris plans
  • Estimate project costs

Usage

  • Overview

Security

    Polaris access

    • Overview
    • Invite users to your organization
    • Manage users
    • Permissions reference
    • Manage user groups
    • Enable SSO
    • SSO settings reference
    • Map IdP groups

    Secure networking

    • Connect to AWS
    • Create AWS PrivateLink connection

Developer guide

  • Overview
  • Authentication

    • Overview
    • Authenticate with API keys
    • Authenticate with OAuth
  • Manage users and groups
  • Migrate deprecated resources
  • Create a table
  • Define a schema
  • Upload files
  • Create an ingestion job
  • Ingestion sources

    • Ingest from files
    • Ingest from a table
    • Get ARN for AWS access
    • Ingest from Amazon S3
    • Ingest from Kafka and MSK
    • Ingest from Amazon Kinesis
    • Ingest from Confluent Cloud
    • Push event data
    • Kafka Connector for Imply Polaris
    • Kafka Connector reference
  • Filter data to ingest
  • Ingest nested data
  • Ingest and query sketches
  • Specify data schema
  • Query data
  • Update a project
  • Link to BI tools
  • Connect over JDBC
  • Query parameters reference
  • API documentation

    • OpenAPI reference
    • Query API

Product info

  • Release notes
  • Known limitations
  • Druid extensions

Billing structure overview

Imply Polaris is a fully managed database as a service (DBaaS) based on Apache Druid and designed to minimize time to value. Polaris offers a free full-feature 30-day trial, making it easy to get started with loading data and extracting insights.

This topic provides general information about the pricing structure of Polaris. For information on the free trial and paid plans, see Polaris plans. For current list prices, see Imply Polaris Pricing.

Billing dimensions

The pricing structure of Polaris follows a consumption-based model. Specifically, Polaris tracks your usage across the following dimensions, each representing a billable unit:

  • Project tier
  • Batch data ingestion
  • Streaming data ingestion
  • File storage

Keep reading to learn more about each of the billing dimensions.

Project tier

Polaris meters the number of hours a project is operating as measured at the beginning of the hour. Monthly Project tier resource consumption is calculated by multiplying the Project tier list price by the number of hours in the month.

You can choose between series A and series D Project tiers:

  • Series A are best suited for compute intensive low latency use cases.
  • Series D are best suited for general purpose use cases focused on storage optimization.

If you already know your data usage requirements, select a Project tier with a capacity that satisfies your use case. If you are unsure of your data usage, sign up for a free trial to ingest and size your data. You can also contact Imply to discuss your requirements, schemas, queries, and tables for an accurate recommendation.

The following table shows series A Project tiers:

Project tierCapacityvCPU allocationMemory
a.02200 GB24 vCPU144 GB RAM
a.04400 GB28 vCPU175 GB RAM
a.08800 GB36 vCPU275 GB RAM
a.121,200 GB64 vCPU450 GB RAM
a.161,600 GB72 vCPU550 GB RAM
a.242,400 GB108 vCPU825 GB RAM
a.323,200 GB144 vCPU1100 GB RAM
a.484,800 GB216 vCPU1650 GB RAM
a.646,400 GB288 vCPU2200 GB RAM
a.969,600 GB440 vCPU3300 GB RAM

The following table shows series D Project tiers:

Project tierCapacityvCPU allocationMemory
d.161,600 GB20 vCPU140 GB RAM
d.242,400 GB30 vCPU210 GB RAM
d.323,200 GB40 vCPU280 GB RAM
d.484,800 GB60 vCPU420 GB RAM
d.646,400 GB80 vCPU560 GB RAM
d.969,600 GB120 vCPU840 GB RAM

Batch data ingestion

Batch ingestion is the process of importing data stored in files into Polaris tables. Polaris meters the amount of data you store in the Polaris files staging area. Monthly batch data ingestion resource consumption is calculated by multiplying the batch data ingestion list price by the amount of batch data ingested during the month (in GBs).

Streaming data ingestion

Polaris meters the amount of data you stream into a destination table. Monthly streaming data ingestion resource consumption is calculated by multiplying the streaming data ingestion list price by the amount of streaming data ingested during the month (in GBs). 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).

Manage your billing profile

Organization administrators and users with the AdministerBilling permission can access the Usage and Billing page to view the billing and payment information for their organization.

To access the Usage and Billing page, follow these steps:

  1. Click the user menu icon located in the top-right corner of the UI.
  2. Click Administration.
  3. Click Usage and Billing in the left sidebar.
  4. Go to the Billing tab to view your billing summary and add a payment method.

Add a payment method

To add a payment method to your billing profile:

  1. On the Billing tab, click Add payment method.
  2. Enter your payment information, including your billing email, cardholder name, credit card information, and billing address. Polaris supports all major credit cards.

Modify payment

To modify your payment method or cancel your account, contact Polaris Support.

Learn more

See the following topics for more information:

  • Imply Polaris pricing for current list price.
  • Polaris plans for reference on the Polaris service plans.
  • Usage overview for information on monitoring account usage from the Polaris UI.
← Pause and resume a projectPolaris plans →
  • Billing dimensions
    • Project tier
    • Batch data ingestion
    • Streaming data ingestion
    • File storage
  • Manage your billing profile
    • Add a payment method
    • Modify payment
  • Learn more
Key links
Try ImplyApache Druid siteImply GitHub
Get help
Stack OverflowSupportContact us
Learn more
BlogApache Druid docs
Copyright © 2023 Imply Data, Inc