How Data Streams are Priced
How Data Streams are Priced
Key Points
- Data Streams use usage-based pricing measured in DVUs (Data Volume Units).
- All usage in a Data Stream draws from a single DVU pool, including sources, enrichments, and pipeline operations.
- Commits let you pre-purchase DVUs at a lower rate and apply across all 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
DVUs accumulate across all activity in your Data Streams: Job runs, content retrieved, and any enrichments applied. Within Data Streams there is one DVU pool per account, not separate pools per stream.
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 other direct integrations are billed at their per-component DVU rates, which may be in addition to those DVUs draw from the same pool as the rest of your stream.
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 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 70% or more are available at higher commit volumes. To discuss pricing tiers, contact our team or use the Cost Estimation Calculator in Portal.
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. |
| Cost Estimation Calculator | Account | Estimate costs for planned usage or identify the right commit level. |
| 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. Requires 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.