StreamNative Cloud Billing

StreamNative Cloud bills are based on the consumption of resources within your cloud organization. This includes but is not limited to the compute units, storage units, and the total amount of data transferred in and out of your cluster.

Billing for each StreamNative Cloud component accrues at hourly intervals. Any usage of less than an hour is billed for the entire hour. All billing computations are conducted in Coordinated Universal Time (UTC).

Note

Billing accrues hourly, with a monthly-in-arrears invoicing cycle. If you de-provision resources that have accrued billed usage during the current month, billing will no longer accrue for these resources, but the billed usage accrued so far in the invoicing cycle will appear on your next invoice.

Subscription plan

A subscription is an agreement between you and StreamNative to pay for service on a particular schedule. In the current release, when you create an instance and a cluster on the StreamNative Cloud Console, you are automatically enrolled in the default Pay-As-You-Go subscription plan. For customers who have legacy clusters, submit a ticket to get assistance with moving your cluster to the updated subscription plan.

If you want to provision a cluster with snctl instead of on StreamNative Cloud Console, you'll need to first create a subscription with snctl. For more information about snctl, see the StreamNative CLI (snctl).

For more information about viewing your invoices, what resources are included on your invoice, how to update your payment information, and more, see the billing documentation page.

Billing dimensions

StreamNative Cloud offers Hosted and BYOC Pulsar clusters. The billing dimensions vary by cluster type.

Usage dimensions

This section describes usage dimensions for different clusters.

Usage dimensions for Hosted clusters

The following table outlines the usage dimensions for Hosted clusters.

Dimension	Unit of measure
Compute Unit (CU)	One CU represents a unit of 2 CPUs and 8 GB RAM. All stateless components are calculated using CUs, including the brokers.
Function Processing Unit (FPU)	One FPU represents a unit of 2 CPUs and 8 GB RAM. This applies to functions and connectors.
Storage Unit (SU)	One SU represents a unit of 2 CPUs, 8 GB RAM, and 125 MiBps write throughput. All stateful components are calculated using SUs, including BookKeeper.
Data in	The total amount of data produced to a Pulsar cluster.
Data out	The total amount of data consumed from a Pulsar cluster.
Data stored	The total amount of data stored in a Pulsar cluster.

Usage dimensions for BYOC clusters

The following table outlines the usage dimensions for BYOC clusters.

Dimension	Unit of measure
Compute Unit (CU)	One CU represents a unit of 2 CPUs and 8 GB RAM. All stateless components are calculated using CUs, including the proxies, brokers.
Function Processing Unit (FPU)	One FPU represents a unit of 2 CPUs and 8 GB RAM. This applies to functions and connectors.
Storage Unit (SU)	One SU represents a unit of 2 CPUs, 8 GB RAM, and 125 MiBps write throughput. All stateful components are calculated using SUs, including ZooKeeper and BookKeeper.

Consumption Units and Support Units

All StreamNative Cloud usage dimensions are calculated in StreamNative Consumption Units. Your overall charge for StreamNative Cloud usage will be equal to the total number of Consumption Units multiplied by the cost of that unit.

The support plan purchased from StreamNative is also based on the Support Units. Your overall support cost will be the total number of Support Units multiplied by the cost of that unit.

Unit	Price	Description
StreamNative Consumption Unit	$0.1	A Consumption Unit captures your StreamNative Cloud usage based on underlying metrics such as Compute Units (CUs), Storage Units (SUs), data stored, data in, and data out.
StreamNative Support Unit	$0.1	A Support Unit captures your StreamNative Support costs based on your support plan. The support plan is a separate and optional purchase item.

Pricing dimensions

This section describes pricing dimensions for Hosted and BYOC clusters and provides a pricing example.

Pricing dimensions for Hosted clusters

The following table outlines the prices for usage dimensions for Hosted clusters.

Dimension	Consumption Units	Price
Compute Unit (CU) ($/hour)	1 CU/hour = 2.4 Consumption Units	$0.24
Functions (FPU) ($/hour)	1 FPU/hour = 1.8 Consumption Units	$0.18
Storage Unit (SU) ($/hour)	1 SU/hour = 3 Consumption Units	$0.3
Data In ($/GB)	1 GB = 1.3 Consumption Units	$0.13
Data Out ($/GB)	1 GB = 0.4 Consumption Unit	$0.04
Data Stored ($/GB-Month)	1 GB-Month = 0.9 Consumption Unit	$0.09

Pricing dimensions for BYOC clusters

The following table outlines the prices for usage dimensions for BYOC clusters.

Dimension	Consumption Units	Price
Compute Unit (CU) ($/hour)	1 CU/hour = 2 Consumption Units	$0.20
Functions (FPU) ($/hour)	1 FPU/hour = 1 Consumption Units	$0.10
Storage Unit (SU) ($/hour)	1 SU/hour = 3 Consumption Units	$0.30

Pricing models

You can either pay as you go or make an annual commitment. Discounts based on usage are available with annual commitments.

Annual commitments

StreamNative Cloud offers the ability to commit to minimum spending over a specified period. This commitment gives you access to discounts and allows you to use this commitment across the entire StreamNative Cloud stack, including Hosted clusters, BYOC clusters, connectors, functions, and support.

If you use more than your committed amount, you can continue using StreamNative Cloud without interruption. You will be charged at the on-demand price for usage beyond the committed amount until the end of your commitment term. Commitments are minimums. If you exceed this minimum, overage charges will be billed to the payment method set for your organization.

Pay-As-You-Go

With the Pay-As-You-Go pricing model, you can sign up and pay monthly in arrears. You can sign up for the Pay-As-You-Go billing model directly from StreamNative, or you can sign up with your cloud provider to pay via your cloud provider billing account. StreamNative Cloud billing integrates with Google Cloud Marketplace and Amazon Web Services.

If you sign up for StreamNative Cloud directly through StreamNative or Cloud Marketplace channels, your organization will be on the Pay-As-You-Go billing model by default.

Pay-As-You-Go billing schedule

This section describes the billing schedule for the Pay-As-You-Go pricing model.

Monthly, billed by StreamNative

When you sign up for StreamNative Cloud service by adding your credit card details in the StreamNative Cloud Console, you are billed monthly.

At each billing cycle, on the first day of each month, all usage for the previous month is aggregated, invoiced, and charged in arrears on the credit card used to sign up for the service.

All usage is expressed and charged in US dollars only.

Monthly, billed through Marketplace

Note

Typically, marketplaces invoice you in arrears on the first day of each month. However, there are exceptions, such as in the case of the Google Cloud billing cycle.
AWS marketplace only accepts integer usage. If your usage is smaller than the billing unit, the user is still charged at the billing unit price.

You can sign up for StreamNative Cloud service through Cloud Marketplace channels. In this case, all usage is reported hourly to the marketplace.

At the marketplace's billing cycle, all usage is aggregated and charged as part of your cloud provider bill.

StreamNative Cloud service usage is a single invoice line with the total amount charged.

Pricing examples

This section provides pricing examples for Pulsar clusters, Pulsar functions, and connectors.

Note

The examples below estimate service costs based on a normalized monthly time frame. It assumes there are 730 hours in a month ((365 days * 24 hours) / 12 months in a year). The actual hours in a given billing period will vary slightly.

Pricing example for a Pulsar cluster

Note

On StreamNative Cloud, a basic Hosted cluster consists of 2 brokers and 3 bookies. Each broker consumes 0.2 compute units per month and each bookie consumes 0.2 storage units per month. Therefore, the minimum cost for a basic Hosted cluster is about $201 per month.

Suppose you have a Hosted cluster on StreamNative Cloud, running an entire month, with the following details:

3 brokers, each with 2 CUs
3 bookies, each with 2 SUs
200 GB data in
200 GB data out
200 GB data retained
CU: The total Consumption Units are 6 CUs x 2.4 Consumption Units / CU-hour x 730 hours = 10,512 Consumption Units
SU: The total Consumption Units are 6 SUs x 3 Consumption Units / SU-hour x 730 hours = 13140 Consumption Units
Data in: The total Consumption Units are 200 GB x 1.3 Consumption Units / GB = 260 Consumption Units
Data out: The total Consumption Units are 200 GB x 0.4 Consumption Unit / GB = 80 Consumption Units
Data stored: The total Consumption Units are 200 GB-Month x 0.9 Consumption Unit / GB-Month = 180 Consumption Units

Therefore, the total cost of this cluster will be 24,172 Consumption Units x $0.10 per Consumption Unit = $2417.2.

Pricing Example for Pulsar Functions and Connectors

Pulsar functions and connectors are billed based on the Function Processing Unit (FPU). You can convert the CPU and memory usage of your functions and connectors to FPUs based on the following formula:

max((CPU / 2),(Mem (in GB) / 8))

For example, if you specify 1 CPU and 1 GB memory for a function, the total FPU for this function is max(1 / 2,1 / 8) = 0.5 CU.

If you have a Hosted cluster on StreamNative Cloud, running an entire month, with

32 functions, each with 0.5 CPU and 1 GB memory
20 connectors, each with 1 CPU and 1 GB memory

The total FPUs used by these functions and connectors are 32 x max((0.5 / 2), (1 / 8) ) + 20 x max((1 / 2),(1 / 8)) = 18 FPUs.

The total Consumption Units used by these functions and connectors are 18 FPUs x 1.8 Consumption Unit / CU-hour x 730 hours = 23652 Consumption Units.

Therefore, the total cost of these functions and connectors will be 23652 Consumption Units x $0.10 per Consumption Unit = $2365.20.