Effective date: October 16th, 2024
Uniform Entity Type | Description | Fair use threshold |
Content Types | describe schema / structure of CMS objects | 500 content types per project |
Entries | instances of CMS content objects | 25,000 entries per project |
Components | describe schema/structure of presentation components | 500 components per project |
Composition | typically corresponds to an instance or a page or a page template (for dynamic pages) | 10,000 compositions per project |
Project map nodes | number of nodes in your sitemap | 10,000 nodes per project |
Component Patterns | pre-assembled, reusable building blocks for experience content in Uniform | 1,000 component patterns per project |
Composition Pattern | Provide a structural template for your compositions | 500 composition patterns per project |
Users / team | Team members | 500 users per team |
API keys | 500 API keys per team | |
Roles / team | 100 roles per team | |
Release | Manage, review, preview, and launch composition, entries in bulk | 250 entities in a release, 4 simultaneous releases across platform |
Redirects | Manage redirects in Uniform UI and API | 10,000 redirects per project |
Uniform Entity | Description | Fair use |
API calls | Calls to uniform.global for route or composition data (what powers the page content) | 50M / year per project |
Data Transfer | Total payload of data returned by uniform.global for route or composition data (what powers the page content) | 500 Gb / year per project |
Uniform Entity | Description | Hard Limit |
Edgehancers | Data resources per entity | A maximum of 500 external HTTP sub-requests per request |
API Response size | Manage pre-assembled, reusable building blocks for content in Uniform | 6MB response size |
Asset Library | Images uploaded into Uniform asset library, not the externally linked assets | 10MB for image assets and 100MB for non-image assets |