Skip to main content

Billing FAQs

Billing Models

JupiterOne has historically supported both entity count and activity based billing models. For enterprise customers additional usage terms may exist in your contract. This document is intended to serve as a guide to how JupiterOne calculates billing, but your license agreement and terms of your contract with JupiterOne always take precedence over this document.

All Assets Count

Total asset count billing model is the current default billing for new JupiterOne customers. It is a very simple billing metric where all assets (aka entities) are counted, and does not include system created entities.

Employee Count or Asset Operations (legacy)

Employee count based billing relied on an "Asset Operation" (aka AO) fair usage limit, which was calculated monthly for customers.

For more details on the legacy AO billing model please see Billing FAQ (legacy)

Billable Entities (legacy)

Billable Entities (aka BE) billing was similar to the current Entity Count model but with complex exclusions for some classes of assets.

For more details on the legacy BE billing model please see Billing FAQ (legacy)


Q: How are assets counted in the "All Assets" model?

Assets can be counted using the following JupiterOne query:

FIND * WITH  _source !^= "system-" AS e
RETURN COUNT(e) AS allEntityCount

This counts all non-deleted assets in your account that were not created by the system mapping rules. This is all assets that have been created via integrations, through the API, or manually though the web UI.

For monitoring purposes this asset count is collected daily and entitlements are calculated using a rolling average.

Q: I don't want be billed for a particular asset type

One of the reasons that JupiterOne has been able to move to a simplified asset billing model is the greatly increased flexibility customers have in configuring what types of assets an integration ingests. For example the AWS integration allows fine grained control of over 160 different types of assets. Customers that don't get value from a particular type of asset can choose to not bring them into JupiterOne.

Q: Do ephemeral entities inflate my billing counts?

No, ephemeral workloads will not cause the asset count to be artificially high. Any short term spikes in assets, or weekly and monthly seasonality, will not inflate asset counts as JupiterOne reviews usage over a rolling period.

The usage calculations are done as a daily single point in time count of entities, it is not a count of all unique entities in the last 24 hours.