Accelerate the Value of Data

Quota and limits

Learn about the quotas and limits on the platform's resources.

Quota limits

Reltio enforces quota limits on resource usage for various reasons. For example, quotas protect the community of Reltio Platform users by preventing unforeseen spikes in usage.

Table 1. Reltio Data Cloud quota details
ItemDefinitionQuota LimitRequest Quota Increase
Reltio Data CloudThe Reltio base Platform consisting of one Production, one Test, and one Development tenant. Contains a Base tenant, and associated Quota Limits, which may vary by License Agreement (See Base tenant) N/A
Aggregate Consolidated Profile A unique profile managed for creating and consolidating data by bringing together attributes from multiple sources Varies by limits and types stated in License Agreement. Subscription is limited to profiles for named Data Domain types (the “Permitted Domains”) Extra fees for new unique profiles that exceed those previously stated in License Agreement, and/or new Data Domain types to be “mastered”
APIs Any calls to the Reltio REST API, outside of calls made by the Reltio out-of-the-box User Interfaces (UI). 1,000,000 per day aggregated across all base platform tenants

Maximum processing up to 300 Operations per second (OPS)

API calls made greater than the maximum per day included in the subscription, will be charged at an extra cost per day
Data Domain A named domain type, for example: customer, product, organization. Industry-specific examples include HCP or HCO for life sciences. Varies by limits and types stated in License Agreement. There is a charge for extra data domains
Reltio Storage Unit (RSU) Total combined primary and secondary storage used across production, test and development tenants, which includes consolidated profiles, reference profiles, interactions, activity log and history data. You find the number of RSUs that you’ve contracted for, in your order form. You can track your RSU consumption for each tenant in the Usage and Billing Metrics page in the Console.

Note again that your RSU Quotas consumed are the total across all of your tenants.

Extra fees apply for extension to existing RSU quota limit (see Reltio Quotas).

Object limits per customer

You can create several objects in Reltio up to the counts mentioned in the table below.

Table 2. Object limits per customer
ObjectsPermissible Limit (count)
Users15000
Clients500
Roles5000
Groups5000
Note: While passing an array of objects through the APIs, you can specify a maximum of 100 objects in a single API call. For example, while creating users, you can send upto 100 entries at a time.

Activity log and history data retention periods

Storage occupied by activity logs and history data consumes your allocated Reltio Storage Units (RSUs). To support automatic reclamation of unused data, Reltio supports retention policies for tenant activity logs and history data. Activity log data is collected for all online user actions and API calls made on a tenant. History data contains versions of your entity profiles for each time the entity profile is changed within a tenant.

No matching or merging, merge tree/history, or potential match data is kept in the history dataset. It’s only a snapshot of the entity profile. Enabling retention of entity history records won’t impact matching and merging/unmerging operations.

The retention periods for activity log data and history data are configured per tenant. The same retention period will be used for activity log and history data for a given tenant. This configuration is managed by Reltio.

Table 3. Retention period details
Environment TypeActivity Log Retention PeriodHistory Data Retention Period
Development1 month1 month
Test3 months3 months
Production1 to 7 years based on industry type (see table under)1 to 7 years based on industry type (see table under)

You can request custom production retention periods outside of the default values to meet your specific business needs or obligations. To request this change, open a support ticket.

The following is the retention period per industry as used by activity log and history data lifecycle management.

Table 4. Retention period details per industry
Industry*Retention Period (Years)
Consulting and Business Services1
Consumer Packaged Goods1
Energy1
Finance and Insurance6
Healthcare7
High Tech1
Life Sciences7
Logistics and Transportation1
Manufacturing1
Media and Communications1
Retail1
Travel and Entertainment1
Oil and Gas7
The default retention period for any industry not listed is One year.
Note: It is recommended to always specify the time period filter when searching/exporting activity log and history data. This approach will help reduce your general quota consumption.

By default, activity log searches return data for the last four months. If you wish to search beyond the default period of four months, specify the appropriate date/time range.

The table specifies retention periods for the activity log. Beyond the retention period, all the data is purged. No results are returned for any searches beyond the retention period.