Billing

The Billing page contains features and pages to manage your subscription, organize and report your Dataloop usage, and manage your consolidated billing if you are part of an enterprise organization. The following tabs are available in the billing page to display various categories of Dataloop billing information:

• Usage
• Account Info
• Alerts

Usage

The Usage tab provides insights into usage metrics related to annotation studio time, datapoints, and serverless automation. Users can monitor resource consumption, track quotas, and export reports for detailed analysis.

Subscription

Every organization in the Dataloop platform has at least one active subscription. Click on the Subscription details to view the features included with your Subscription.

Usage by subscription

This section provides an overview of the total quota and the percentage of consumption for key features based on your current subscription.

📊 Why it matters

• Easily track your usage to ensure you're maximizing your subscription benefits.
• Avoid overages by monitoring key feature consumption in real-time.
• Gain insights into when you might need to upgrade or optimize usage.

Important

• Only the active subscription is displayed, making it easy to track the expiration date.
• Once a subscription expires, certain platform functionalities become restricted.
• New subscriptions include three core metrics:
  • UI Hours: Total annotation studio time used by all users.
  • Datapoints: Number of file items and annotations created.
    • Every file is 1 datapoint.
    • Every annotation is 1 datapoint.
    • In frames based files, such as video and LiDAR, every annotation on a keyframe, and every changed annotation in an interpolated frame are counted as datapoints.
      • A key-frame is a frame where manual annotation creation or editing was done.
      • An interpolated frame is a frame somewhere between 2 keyframes, in which an annotation was changed by an algorithm or a model.
    • Annotations in an interpolated frame, that has no change vs. the last keyframe, are not counted as data-points.
    • Annotations hidden in the annotation-studio still exist in the system and therefore counted as datapoints.
  • Serverless Automation: A feature that enables organizations to monitor, manage, and regulate compute resource usage within a predefined budget. It displays the total compute hours or costs used by the organization. This feature is only available if the organization has an allocated compute budget.
• Older subscriptions may also include additional metrics no longer offered, such as:
  • Storage
  • API calls
  • Compute hours
• Customers will contact users before the expiration date to discuss renewal options.
• After expiration, users can still access the platform, but key actions are restricted, including:
  • Working in the studio
  • Uploading new data
  • Running executions, etc.

Subscription usage count

Your organization's usage is taken from all projects billed to your account. By default, projects created by organization members are owned and billed to it. Also, you can set a project for billing from one organization while another remains its owner.

Usage data is collected from all respective projects, aggregated and deducted from the subscription accordingly.

Usage by month

This section provides a breakdown of usage metrics on a monthly basis.

Key statistics include:

• Max Datapoints: Total number of datapoints processed. The 'Max Datapoints' calculation looks at the aggregation for each month within the selected period and displays the maximum usage among all these months. This helps users understand their peak usage for planning future renewals.
• UI Hours: Total time spent in the annotation studio.
• Serverless Automation: Total automation hours used. Serverless Automation tracking is only applicable if the organization has a compute budget.
• Click Generate to create a report for the selected time frame.
• Click Download CSV to export detailed billing data.
• Use the date picker to adjust the reporting period. Filtering is available by month, enabling you to track project usage at both an overall level and for individual projects. You can select predefined timeframes such as the current month, last month, 3, 6, or 12 months, or customize the range by selecting specific months (use the Click + Drag to select multiple months. This flexibility allows for efficient monitoring of resource utilization across different periods and projects.

Custom Months Range

The usage information is also detailed on the project level, allowing you to learn more about consumption from the different projects.

• Sort the list by its various columns to learn more about the consumption of the different projects on each related metric.
• Use the search box to search for a specific project and filter by it.
• The list provides further details about CPU and GPU usage, by breaking it down into specific machine types.

Project level data

• Project Name: The name of the project
• Owning Organization: The organization name of the project.
• Max Managed Items: The maximum amount of items currently managed on the Dataloop system, across all projects and storage types (internal/external).
• Total Storage: The storage space used by all projects combined.
• UI Hours: Annotation studio time used by all users per project.
• Max Annotations: The maximum number of annotations currently in the organization's projects.
• Max Keyframes: It refers to the maximum number of keyframes that can be utilized or processed within your account. Keyframes are specific frames in a video where annotations are explicitly defined, allowing for efficient tracking and labeling of objects throughout the video sequence.
• API Calls: The number of API requests to the server in your projects.
• Serverless Automation: It refers to a feature that allows organizations to monitor, manage, and control their compute resource usage within a predefined budget. It displays the total hours/cost spent by the project. Users can view compute usage by cost or hours. This feature is active only if the organization has a compute budget.
• GPU: Hours of GPU used by Applications (FaaS) / services.
• CPU: Hours of CPU used by Applications (FaaS) / services.
• System Compute: It refers to the total compute resources used by all machines categorized under the system service type.

Usage email alerts

When an account reaches resource consumption limits, email alerts are sent based on thresholds:

• 80%, 90%, and 100%

Alerts Cover:

• Compute budget ($)
• Datapoints
• UI hours
• API calls

Recipients: Org owners & admins of connected organizations.

Account information

The organization's business information, as provided when creating the subscription, can be reviewed and changed as needed. The payment method that's on file is listed for review as well.

• To add a payment method: Click Add in the Business Details & Payment Method section and enter required details.
• To edit the business details: Click Manage in the Business Details section and edit the information.

The usage information gives you an in-depth analysis of your organization’s use of the Dataloop services. You can access it from the organization-related menu section on the left-side menu.

The information on this page is displayed every month, with the current month as the default. Use the month-selection option to review consumptions in past months.
You can download the data available on this page as a CSV file to use it with your system or perform further analysis.

You can copy the account ID by clicking on the Copy to clipboard icon.

Alerts

The Alerts tab provides real-time notifications about system limits, helping users manage resources effectively. These alerts are triggered when usage approaches or exceeds predefined limits in various categories, such as:

• Compute Budget: Notifies when compute resources are nearing or exceeding allocated limits.
• Datapoints: Tracks usage of labeled datapoints to ensure efficient dataset management.
• Compute CPU Limits: Alerts when CPU usage surpasses designated thresholds.
• Hosted Storage Limits – Monitors storage consumption to prevent overuse and ensure smooth operations.

Each alert entry includes the following details:

• Alert Date: The timestamp of when the alert was generated.
• Status: Indicates whether the alert is active, resolved, or pending action.
• Percentage of Used Limit: Displays how much of the allocated limit has been consumed.
• Description: Provides additional context on the alert and possible actions to take.
• Account Name: Specifies the account associated with the alert.

These alerts enable users to proactively manage their resources, preventing disruptions and optimizing system performance.