Pricing

Simple, Usage-Based Pricing

No per-seat fees. No per-pipeline charges. Two product paths, each with its own model. Pay for data volume, not infrastructure.

Two Product Paths

Pick the model that fits your team.

Both paths use the same pipeline and enrichment infrastructure. The difference is how sources are managed and how usage is billed.

Primary: Data Streams
DVU-Based Pricing
Pre-purchase data volume across all your sources at once. No vendor-by-vendor commitments. Commits apply across all sources, not per provider.
1 DVU
per Job Run
1 DVU
per 100 documents (first 100 per Job Run included)
Source-agnostic committed usage discounts
Enrichments billed separately at per-component DVU rates
Monthly billing, adjustable each cycle
Per-job cost visibility and budget alerts
No contracts locked into annual terms
Get a Usage Estimate
Advanced: Direct Integrations
Per-Component Pricing
Connect specific vendors using your own API credentials. Pricing is per component, based on what you configure and how you use it.
Per
component configured
Full
provider control
Use your existing vendor contracts and API keys
Full control over provider selection and config
Same pipeline and enrichment infrastructure
Separate pricing model from Data Streams
Best for teams with existing procurement relationships
Talk to Sales
Data Streams Pricing

How DVUs work.

A DVU (Data Volume Unit) is a normalized unit of measurement across all sources, enrichments, and operations. One common denominator for the many different volume metrics across providers.

1 DVU per Job Run
Each time a stream queries a source, that is one Job Run and counts as 1 DVU. This applies regardless of how many documents are returned in that run.
1 DVU per 100 documents retrieved
The first 100 documents of each Job Run are included at no extra cost. Each additional 100 documents beyond that counts as 1 DVU.
Enrichments add DVUs at per-component rates
Each AI or NLP enrichment operation (sentiment, NER, emotion classification, etc.) adds DVUs at its own per-component rate. You only pay for the enrichments you use.
Commits earn lower DVU rates
Pre-purchase expected monthly DVU volume at a discount. Commits apply across all sources, not per vendor, so you can shift data collection between sources without losing your discount tier.
Included in the platform
Unlimited pipelines, users and integrations
Schema transformation and data management
Auto-scaling infrastructure and recovery
Pipeline metrics, versioning and diagnostics
Jobs API and connector automation
Budget alerts, billing dashboard and projections
Document inspector and failed items viewer
Searchable Storage APIs (Lucene)
MCP server integration
Slack community and support ticketing
Premium add-ons (billed separately)
Brightdata sources Socialgist feeds DarkOwl search AI enrichments Social Voice OpenAI completion
Get a Usage Estimate →
Direct Integrations

For teams with existing
vendor relationships.

Direct Integrations give you full control over which providers you connect, using your own API credentials. A separate pricing model from Data Streams.

1
Bring your own API credentials
Connect specific vendors using your own contracts and API keys. Datastreamer handles the pipeline, enrichment, and delivery. You control the provider relationship.
2
Per-component pricing model
Pricing is based on what you configure, separate from the DVU model used by Data Streams. Talk to sales for a breakdown based on your specific components.
3
Same infrastructure as Data Streams
Both paths run on the same pipeline, enrichment, and delivery infrastructure. The difference is source management. Everything else works the same way.
4
Mix both paths
Some teams use Data Streams for most sources and Direct Integrations for specific vendors they already have relationships with. Both can run in the same platform account.
Not sure which path fits your team?
Most teams start with Data Streams for fast time to value and move specific vendors to Direct Integrations as procurement relationships mature. Talk to sales for a recommendation based on your data requirements and vendor setup.
Talk to Sales See how the two paths compare →
Common Questions

Pricing FAQ

What is a DVU?
A Data Volume Unit (DVU) is a normalized unit of measurement across all sources, enrichments, and operations. It gives you one common pricing metric regardless of which providers or operations you use in your Data Streams.
How do commits work?
Commits are pre-purchased monthly DVU volumes at a discounted rate. They apply across all your sources, not per vendor, so you can shift data collection between sources without losing your discount tier. Commits are set at the start of each billing cycle and can be adjusted with prior notice.
Can I use both Data Streams and Direct Integrations?
Yes. Both paths run in the same platform account. Some teams use Data Streams for the majority of their sources and Direct Integrations for specific vendors they already have relationships with.
How is billing handled?
Data Streams usage is billed on the first of each month based on prior month consumption. You get per-job cost visibility, budget alerts at configurable thresholds, and cost projections updated every six hours.
Are enrichments included in the base DVU rate?
Enrichments are billed separately at per-component rates on top of your base source DVU usage. You only pay for the enrichment operations you actually run. The platform itself includes all pipeline infrastructure, schema management, and observability at no extra charge.
Is there a free trial or sandbox?
Talk to sales for trial access and a usage estimate tailored to your data volumes and source requirements. The team will walk you through expected DVU costs based on your specific use case before you commit to anything.
Get a Usage Estimate

Talk to sales before you commit.

We'll estimate your DVU costs based on your specific sources, volumes, and enrichment requirements. No surprise bills.

Talk to Sales DVU Explained →

Usage-based pricing that scales with your volumes. No per-seat fees.