How are Overages Calculated and Charged?

Need help with something?

Talk to data expert

Overage charges are calculated based on the usage that exceeds your plan's row limit. Here's how the overage charges work for different growth plans:

Growth Plan Overage Rates

Plan Limit (Rows) Overage Rate (per extra million row)
5 Million $28.5
10 Million $27
25 Million $21
50 Million $19.5
100 Million $15

Note for LITE Plan users

All the details mentioned for Growth Plan users also apply to Lite Plan users, with the following specifics:

Plan limit for Lite Plan: 1 million rows
Overage Rate for Lite Plan: $33 per additional million rows

 

To compare different plans and offerings in Daton, you can visit the Daton Pricing Page.

Enterprise Plan Overage Rates

For enterprise plans, overage charges are determined by the specific terms of your contract, which may differ from the growth plan rates.

Please check your contract or write us at support@sarasanalytics.com if you want to learn more about the terms of your contract. 

Let's understand how overages are charged using an example:

Given you are on a 5 Million Growth Plan, this means your usage limit is 5 million rows. 

  • If your row usage is less than 5 million, no overage charges will apply, and you will be charged $0.
  • If your row usage exceeds 5 million, you will be charged $28.5 per additional million rows.
 
The calculation for overages is as follows:
Overage charges = (Rows used in millions - Row limit) × Overage rate
Example 1: If your usage is 8 million rows, the calculation will be:
Overage charges = (8M - 5M) × $28.5 = 3 × $28.5 = $85.5
Example 2: If your usage is 5.34 million rows, we round up to the next million (i.e. 6M).
 The calculation will be:
Overage charges = (6M - 5M) × $28.5 = 1 × $28.5 = $28.5

Key Points:

  • Any extra usage is rounded up to the nearest million for calculation purposes.
  • Overage is only charged on rows exceeding the plan limit.
  • The rate of $28.5 per million rows applies to this specific plan. The rates will differ based on your plan.

Overage on Monthly and Yearly billing cycles

For Monthly Billing Cycle Users

  • Your overage or usage cycle aligns with your billing cycle. For example, if your subscription cycle runs from March 12th to April 12th, your overage or usage cycle will also follow the same timeframe.
  • At the time of your monthly plan renewal, any overage charges from the previous month will be automatically deducted from the card linked to your Daton account. These charges will be clearly reflected in your monthly invoice for transparency.

For Yearly Billing Cycle Users

  • Even though you pay annually, your usage and overage cycle operates on a monthly basis. For instance, if your annual billing cycle runs from February 12th, 2024, to February 12th, 2025, your usage will be tracked and reported in monthly intervals:
    • February 12th, 2024, to March 12th, 2024
    • March 12th, 2024, to April 12th, 2024, and so on.
  • Overage charges will be calculated based on your monthly usage and plan limits. You will receive separate invoices for these overages, and the corresponding amounts will be debited monthly from the card linked to your account. This ensures accurate billing for any additional usage beyond your plan's limits throughout the year.

Special Cases: Data Exclusions from Overages

In certain scenarios, specific data processing activities are excluded from overage calculations. This section outlines these special cases and their implications on your usage.

7 day free historic/Initial load

When you create a new integration, you can load all your historical data free of charge for the first 7 days.


Scope: All historical data—whether it spans 2 months, 2 years, or more—can be processed without impacting your usage limits, as long as it is completed within 7 days.

Coverage: Applies across all plans and every supported source integration.

Purpose: This allows you to populate your tables for the first time, without worrying about billable rows or overages.

ℹ️ Note: In most cases, historical loads finish within the 7‑day window. If you notice delays, please contact support.

 

2 day Rollback window

A rollback reverts a table to an earlier state by discarding recent changes and restoring data as it existed at a previous point in time. This is useful when incorrect or duplicate data was loaded and you need to return the table to a clean, trusted version before reprocessing.
 

Scope: The rollback benefit applies at the table level. Any data reprocessed from that source within the 48 hours following a rollback is free—whether you revert to a point in time from months or even years ago.

Purpose: Enables you to fix issues or backfill safely without additional usage costs.

ℹ️ Note: Rollbacks must be requested through the support team (except for Amazon Selling Partner, where self‑service rollback is available).  
 

2 day Reload Window

A reload fully reprocesses a table starting from a specified point in time, replacing the existing data with a fresh and consistent copy from the source.

 

Scope: The reload benefit applies at the table level. Any data processed from that source in the 48 hours following a reload is free, even if it covers extensive historical data.

Purpose: Allows you to refresh or correct data without incurring usage charges or overages.


How to optimise your usage?

To optimize your usage and reduce unnecessary costs, consider the following strategies:

1. Adjust Integration Frequency

  • Reduce Frequency: If you have integrations set to run too frequently (e.g., every hour), consider adjusting them to run less often, such as every 12 or 24 hours. This can significantly reduce the number of rows processed and lower your costs.
  • Match Frequency to Needs: Ensure that the frequency aligns with your business needs. If real-time data isn't necessary, reducing the frequency can be an effective cost-saving measure.

2. Pause Unused Integrations and Tables

  • Identify Unused Resources: Regularly review your integrations and tables to identify those that are no longer needed or used. 
  • Pause or Delete Unused Items: Pause or delete integrations and tables that are not being used. This will prevent unnecessary data processing and reduce your overall usage.

If you're interested in learning more about managing your Daton account, here are some helpful resources:

For more information, please visit our pricing page or contact our support team.