Credit Consumption Breakdown
DLH.io uses multiple pricing configurations to provide its users and customers with the best experience at an affordable pricing configuration. All prices are in USD.
The product offerings from DLH.io are mainly capacity or utilization based for the Data Synchronization product offering. These credits are used to pay for the consupmotion of resources. As a unit of measure when a customer uses a resources for Data Sync customers under the capacity pricing, credits are consumed based on the rows loaded. For analytics packages pricing structures such as our Ceridian Analytics, Salesforce.com Analytics, or McLeod Analytics, etc. include an annual contract for licensing. Credits can also be purchased in advance for utilization in our DLH.io markeplace.
DLH.io credits are used and consumed when:
for Data Sync:
- Utilization and times when a Sync Bridge (aka DLH.io Software) was available for use and/or running, or
for Data Catalog:
- Number of a data sources and data artifacts referenced or implemented
for DLH.io Markeplace:
- Transactions exchanged for services or products to DLH.io or one of our DLH.io partners in the marketplace
Credits are based on levels of plans which have certain features or capabilities. As a transparent way of communicating with our customers, for example, the enterprise and business critical plans have additional features such as SSO, etc. which costs DLH.io more to operate, and thus those plans have higher pricing structures to ensure we can support and continue to provide these services to our customers.
Where there is an compute hour credit allocation, this is due to DLH.io resources running our software which enables the services for our customer. In the case of Data Sync (ELT), this is monitored and billed at a minimum of 15 minute increment.
As a way to level set a standardized approach to charging customers for ELT based on a more consistent, and often lower set of data records to be sychronized to a target destination, DLH.io can bill customers at a flat rate per records loaded per month. We refer to this as Monthly Active Events (MAE). The "Events" portion of this way to reference data is that not every source system is a database, and there for rows and records are legacy ways of looking at data where "Events" are any type of transactional data generating occurances such as IoT, SFTP, Files, Databases, etc.
This rate is also based on a plan that customers select to start with and can also upgrade to for the feature sets they wish to take advantage of as part of the DLH.io services.
What happens when Credit thresholds are exceeded?
A DLH.io customer success manager reviews your monthly usage intermittently each month reviewing your usage. If customers exceed their monthly rate limits they will be charged an overage rate that is inline with the standard rate for the same edition of the plan selected.
Capacity Plan Per
DLH.io Compute Hour
1 credit / compute hour
DLH.io Additional Users
50 credits per addition user outside of plan users