Understanding Openflow costs¶
By using Openflow, you can incur the following types of costs:
Cost category |
Description |
|---|---|
Openflow (shown as ‘Openflow Compute BYOC’ on your Snowflake bill) |
Cost based on the number of virtual CPU cores (vCPU) used by connector runtimes within your bring your own cloud (BYOC) environment. You are charged for active runtimes only. The compute used for Openflow management processes is excluded from this specific charge. Credits are billed per-second with a 60 second minimum. For information on the rate per vCPU per hour, refer to Table 1(g) in the Snowflake Consumption Table. |
Infrastructure (only for BYOC configuration) |
Applicable only for BYOC deployments, you directly pay your cloud provider, for example, AWS, for the underlying infrastructure provisioned in your environment to run Openflow. This primarily includes compute (for runtimes you provision to run the connectors and for managing the runtimes), networking, and storage costs and will appear on your CSP bill. The EC2 compute requirements are illustrated in the following image: 
|
Ingestion |
Cost for loading data into Snowflake using services such as Snowpipe or Snowpipe Streaming, based on data volume. Appears on your Snowflake bill under respective ingestion services line items. Certain connectors may require a standard Snowflake warehouse, incurring additional warehouse costs. For example, database CDC connectors require a Snowflake warehouse for both initial snapshot and incremental CDC. You can schedule MERGE operations to manage the compute cost. |
Telemetry Data Ingest |
Standard Snowflake charges for sending logs and metrics for Openflow deployments and runtimes to your event table within Snowflake. The rate is 0.02 credits per GB of telemetry data ingested. |