How Datastreamer is priced
An overview of how pricing and costs are measured and displayed for your pipelines.
Key Points to Know!
As a summary, here are the key things to know about the platforms pricing. Each of these points are covered in greater detail in their own sections.
- The Platform is usage-based pricing.
- Usage of various components are measured in Data Volume Units (DVUs).
- The number of pipelines, components, or users do not affect pricing.
- The billing cycle is monthly.
- Committed Usage Discounts (Commit) can be used on a monthly basis to lower the costs of pipeline resources by pre-committing to expected volumes upfront.
Datastreamer operates on Usage Based Pricing
The Platform you are using to create your dynamic pipelines is a usage-based model. The amount of data flowing through the Pipeline is measured with "Data Volume Units" (DVUs), and billed accordingly. This can be simply visualized with the following formula:
(DVUs used) X (DVUs price) = Component Cost
Data Volume Units (DVUs) are relative units meant to bring a common measurement to the many different measurements present in different data sources, vendors, providers, AI providers, and more. The Data Volume Units page gives a detailed understanding of this metric. Data Volume Units Explained.
You can lower the DVUs price from the above example with Committed Usage Discounts (Commits), which are explained below.
The Platform usage is measured as a sum of usage across the components in any pipeline, so you can use as many (or as few) pipelines as you need.
Committed Usage Discounts (Commits)
Spend-based committed volumes discounts (Commits) provide a discount in exchange for your commitment to a minimum volume for a pipeline offering (platform, enrichment, data source, etc). The discount applies to that set of eligible resources.
Details on Commits is available on it's own documentation page here.
Managing Your Billing
We recognize that working with web and social data relies on fluctuating volumes. To support you, Datastreamer has a number of features and tools that you can use within your Pipelines to ensure full control of costs.
You can see usage at any time.Portal has a detailed Billing Dashboard page that allows you to see the usage and costs at any point. You can also see projected spend based on usage patterns, and historical usage from previous months.
| Resource | Level | Capabilities & Usage |
|---|---|---|
| Managing Volumes (Document Limits) | Job | Within each Job, you can set Document Limits that act as a soft cap on the volume of documents that can return from a request to a data source. The Job system within your pipeline observes, monitors, and stops requests if that number is exceeding your limit. |
| Alerting on Volumes | Pipeline | Within Document Inspector, alerts can be set on the volume of content and timeframes for alerting. Alerts write to your logs, and can also be sent to email. |
| Cost Forecasting | Account | Within your Billing Dashboard, the cost projections are updated every 6 hours, projecting your overall costs based on usage patterns. |
| Budget Alert | Account | Budget alerts can be set on percentages overall spend, and configured to send emails at any set percentages when that amount of usage is met. |
| Tag-level Billing Insights | Global | Fully configurable in Job creation, Tags can be added to any action and will be available as filterable options within the billing dashboard. Any number of billing tags can be used. |
| Cost Estimation Calculator | Account | The cost estimation calculator allows you to project the cost of future projects or right-size to Committed Usage Discounts (Commits) with a configurable interface. |
| DVU Job API | Job | The DVU Count API (Job-level), provides the usage (in DVUs) of any Job. |
Billing Cycle
Billing is done on the first of every month, and consists of usage in the past month (which may have exceed any commits), and any Commits for the new month.
Changing commits and account tiers are required to have prior notice before a new billing cycle. A notice period of changing commits is detailed in your usage agreement.
Account Tiers
Within the Platform, your organization's account can be either in Standard or Standby. A Standby account has read-only access to their platform and is unable to run or deploy dynamic pipelines.
A Standard account requires a minimum Platform Fee commitment, and has full access to all Platform capabilities.
You can migrate an account between Account Tiers each billing month. However, changing tiers are required to have prior notice before a new billing cycle. A notice period of changing account tiers is detailed in your usage agreement.
Updated 8 days ago
