👍
Key Points

Data Streams use usage-based pricing measured in DVUs (Data Volume Units).

Auto Source usage (Job Runs and documents) draws from a single DVU pool. Enrichments and Direct Integrations are billed separately at their own per-component rates.

Commits let you pre-purchase DVUs at a lower rate and apply across all Auto Sources in your Data Streams.

The number of Data Streams, pipelines, components, or users does not affect pricing.

Billing is monthly.

Usage-Based Pricing

Data Streams are billed based on usage. Usage is measured in DVUs and the formula is straightforward:

(DVUs used) x (DVU price) = Cost

For current DVU rates and commit tiers, see Datastreamer Pricing.

Auto Source usage (Job runs and content retrieved) draws from one DVU pool per account, not separate pools per stream. Enrichments are billed separately at their own per-component rates.

For a detailed explanation of how DVUs are counted, see What are Data Volume Units?

Enrichments or Other Customizations

Adding enrichments or direct integrations to a Data Stream may impact your billing. Enrichments and Direct Integrations are billed at their own per-component DVU rates, separate from the Data Streams DVU pool and commit.

For specific DVU rates, see the documentation for each enrichment component.

Committed Usage Discounts (Commits)

Commits let you pre-purchase a volume of DVUs each month at a discounted rate. The more DVUs you commit to, the lower the per-DVU price.

Key points about commits for Data Streams:

Commits apply across all Auto Sources in your Data Streams. You are not required to commit per source or per provider.
Commits are not usage caps. If you exceed your committed volume, usage above the commitment is billed at your committed price.
Commits are pre-paid at the start of each billing cycle.
Commits for Data Streams do not apply to direct integrations, which may require their own commits.

Discounts of up to 80% are available at higher commit volumes. For rates and commit tiers, see Datastreamer Pricing, or use the Pricing Calculator in Portal.

Full details on Commits

Managing Costs

Tool	Level	Description
Document Limits	Job	Set a cap on how many documents a Job retrieves per run.
Volume Alerts	Pipeline	Alert when document volumes cross a set threshold. Can send email notifications.
Cost Forecasting	Account	Billing Dashboard projects spend every 6 hours based on current usage patterns.
Budget Alerts	Account	Set percentage-based spend alerts with email notifications at configured thresholds.
Tag-Level Billing	Global	Tag any Job or action to filter billing data by tag in the dashboard.
Pricing Calculator	Account	Estimate costs for planned usage or identify the right commit level.
Query and Pipeline Budget Limits (early access)	Query, Pipeline	Set a budget limit on individual queries and on pipelines, so collection stops before spend passes the limit. Contact [email protected] for access.
DVU Job API	Job	Query DVU usage for any specific Job via the DVU Count API.

Billing Cycle

Billing runs on the first of each month. Each cycle covers:

Usage from the prior month, including any usage above your commit
Commits purchased for the new month

Changes to commit levels require advance notice before the start of a new billing cycle. Notice periods are detailed in your usage agreement.

Account Tiers

Tier	Description
Standard	Full platform access. Data Streams on Auto Sources have no separate platform fee; Direct Integrations require a minimum Platform Fee commitment.
Standby	Read-only access. Data Streams cannot be deployed or run.

Tier changes require advance notice before a new billing cycle.

Direct Integrations Pricing

If you are using Direct Integrations (specific vendor connectors with your own credentials), a different pricing model applies. See Direct Integrations Pricing.