All Collections
Billing & Account
Billing
How is the price of sensors & add-ons calculated in LimaCharlie?
How is the price of sensors & add-ons calculated in LimaCharlie?
Ross avatar
Written by Ross
Updated over a week ago

Billing Model

There are two categories of sensors: sensors billed on Quota set by the user (vSensor basis), and sensors billed on usage basis. The price listed below is up to date as of January 28, 2022 and includes 1 year of full telemetry storage. Please visit our price list for the most up to date pricing.

Sensor Type

Billed on

Cost

Windows

Quota

$2.5/sensor/month

Linux

Quota

$2.5/sensor/month

macOS

Quota

$2.5/sensor/month

Docker

Quota

$2.5/sensor/month

VMWare Carbon Black EDR

Quota

$0.5/sensor/month

Chrome OS

Quota

$0.25/sensor/month

Syslog

Usage basis

$0.15 / GB*

Amazon AWS CloudTrail Logs

Usage basis

$0.15 / GB*

Google Cloud Platform (GCP) Logs

Usage basis

$0.15 / GB*

1Password

Usage basis

$0.15 / GB*

Microsoft/Office 365

Usage basis

$0.15 / GB*

Windows Event Logs

Usage basis

$0.15 / GB*

Microsoft Defender

Usage basis

$0.15 / GB*

Duo

Usage basis

$0.15 / GB*

CrowdStrike

Usage basis

$0.15 / GB*

GitHub

Usage basis

$0.15 / GB*

Slack Logs

Usage basis

$0.15 / GB*

Other external sources

Usage basis

$0.15 / GB*

*billed once (at ingestion) and includes one year of full telemetry storage

Detailed explanation

Sensors billed on vSensor basis

LimaCharlie has a concept of vSensor. A vSensor is a virtual sensor used for the purpose of setting up quota and billing. One vSensor cost as of January 28, 2022 is $2.5 (includes 1 year full telemetry storage).

Below is the table that lists sensors billed on the vSensor basis, along with their vSensor value as of January 28, 2022. For the up to date pricing, please visit our pricing page.

Sensor Type

Billed on

vSensor Value

Cost

Windows

vSensor basis

1 vSensor

$2.5/month for one Windows sensor (includes 1 year full telemetry storage)

Linux

vSensor basis

1 vSensor

$2.5/month for one Linux sensor (includes 1 year full telemetry storage)

macOS

vSensor basis

1 vSensor

$2.5/month for one macOS sensor (includes 1 year full telemetry storage)

Docker

vSensor basis

1 vSensor

$2.5/month for one Docker sensor (includes 1 year full telemetry storage)

VMWare Carbon Black EDR

vSensor basis

0.2 vSensor

$0.5/month for one VMWare Carbon Black (includes 1 year full telemetry storage). Calculated as follows: $2.5/month per 1 vSensor * 0.2 (vSensor value for VMWare Carbon Black EDR)

Chrome OS

vSensor basis

0.1 vSensor

$0.25/month for one Chrome OS sensor (includes 1 year full telemetry storage)

Example: if you set quota to 100 vSensors, this means that at any point in time for $250/month you can have:

  • 50 Windows sensors + 50 Linux Sensors connected concurrently, OR

  • 20 Windows sensors + 30 Linux Sensors + 50 macOS sensors connected concurrently, OR

  • 100 macOS sensors connected concurrently, OR

  • 100 VMWare Carbon Black EDR sensors (a total of 20 vSensors based on the above value) + 25 Linux sensors + 55 macOS sensors, OR

  • any other combination as long as the total number of sensors does not exceed the quota of 100 vSensors

Sensors over Quota

If the quota is maxed out when a sensor attempts to come online, the sensor will be given a message to go away for a period of time and then they can check again. A sensor_over_quota event will be emitted in the deployments stream as well enabling users to set up alerts and be notified about this happening. The amount of time sensors are told to go away for increases if they connect again and the organization is still over quota.

Sensors billed on usage

Some sensors are billed based on usage.

Sensor Type

Billed on

Cost (includes 1 year full telemetry storage)

Syslog

Usage

$0.15 / GB

Amazon AWS CloudTrail Logs

Usage

$0.15 / GB

Google Cloud Platform (GCP) Logs

Usage

$0.15 / GB

1Password

Usage

$0.15 / GB

Duo

Usage

$0.15 / GB

Slack Logs

Usage

$0.15 / GB

Other external sources

Usage

$0.15 / GB

You don’t need to account for sensors billed based on usage when setting up the quota. For example,

  • 50 Windows sensors + 50 Linux Sensors + 100 1Password sensors connected concurrently will require a quota set to 100 vSensors (Windows + Linux), as 100 x 1Password sensors will be billed based on usage at $0.15 / GB

Add-ons

LimaCharlie Add-Ons are billed on the vSensor basis. When an add-on is used with a sensor billed on usage (eg., 1Password), the Add-On will be free.

For example:

  • One year of telemetry storage (Insight add-on) for a Windows sensor will cost $0.5/sensor/month, calculated as follows: add-on cost of $0.5/month * 1 (vSensor value for Windows)

  • One year of telemetry storage (Insight add-on) for a VMWare Carbon Black EDR sensor will cost $0.1/sensor/month, calculated as follows: add-on cost of $0.5/month * 0.2 (vSensor value for VMWare Carbon Black EDR)

Did this answer your question?