Fair Use Policy
Contentstack’s priority to its customers is to keep the Contentstack service available, which requires each Customer to have reasonable and set policies for fair use of the resources of the Contentstack service (We refer to the Contenstack service or the “SaaS Services” as defined in our standard Master Agreement as the “Service”). While the Service includes broad access to a variety of resources such as API requests, storage, and bandwidth, they are not unlimited (unless expressly stated as such) or it would affect the stability of the system, including but not limited to the Service, which is why we have this Fair Use Policy.
This Fair Use Policy (FUP) is additional Documentation for the Service set forth in the Master Agreement or similar defined terms describing the Contentstack service used in our contract with you. Capitalized terms used but not defined below, shall have the meaning outlined in the Master Agreement and Use Policy. If the Use Policy is attached to or referred to in our contract with you or our contract uses similar terms, this Fair Use Policy is considered part of the “Documentation.”
We reserve the right to update this, and any other Documentation, at any time, including but not limited to adding limits on modules created in the future. Such limits, guidelines, and parameters may be listed elsewhere in other Documentation.
Per our Master Agreement or other written contract with you, all customers are required to comply with Sections 3.2, 3.3 and 3.4 of the Use Policy as well as this Fair Use Policy and any other Documentation in the use of the Service.
We include a variety of components in the Service, but we provide for policies regarding certain parameters in order to keep the Contentstack service stable, available and uniform. Exceeding these parameters may result in i) throttling or limitation of access to the Service as set forth in Section 5.6 of the Master Agreement in the Master Agreement (or other similar terms in our agreement with you); and/or additional costs as set forth in the Order Form.
Key Parameter Policies
Currently, using the dialog, you can select up to 10 assets at a time. The size of an asset should not exceed 700 MB. The maximum number of Assets per Org shall not exceed 500,000.
The maximum number of Branches allowed per Stack is 5.
There are certain limitations that we have applied to the option to publish entries in bulk. Let us understand what they are:
- At a time, you can publish 10 entries in 10 languages and on 10 environments
- The rate limit for bulk actions is 1 request per second
The rate limit is the maximum number of requests that you can make using any Contentstack API in a given period. There are no limits on the requests that you make to the cached data on Contentstack’s CDN. Contentstack's API automates caching to enable our API to scale. For uncached requests, i.e., requests to the origin server, there is a maximum limit of 100 requests per second per organization. The rate limit depends on your plan, and you can request an increase in your rate limit if necessary.
By default, any Contentstack Management API enforces the following rate limits:
- Read (GET) requests: 10 requests per second per organization
- Write (POST/PUT/DELETE) requests: 10 requests per second per organization
Your application will receive the HTTP 429 response code if the requests for a given time period exceed the defined rate limits.
The maximum number of Content Types per Org shall not exceed 1,000.
Digital Properties are defined as production-level presentation layers (web, mobile, IoT, in-game, etc) and should be limited per Stack. We’re no longer charging for Digital Properties, however, if your plan currently caps the number of Digital Properties, we will continue to enforce limits on the number of production properties that can be powered per Stack.
The maximum number of Entries per Stack shall not exceed 2,000,000.
Environments represent duplicate instances of an entry published in each environment. The maximum number of environments per Stack shall not exceed 3.
Locales represent duplicate instances of an entry published in each language, market, or region. The maximum number of locales per Stack shall not exceed 150.
Stacks Per Org
Stacks are provisioned according to the product tier the customer has subscribed to. All pricing tiers will include a defined number of Stacks along with a per-Stack add-on price. Customers cannot go above the defined Stack allowance without incurring marginal costs for the additional Stacks. Legacy customers may keep the stacks they currently have, but will not be allowed to create new Stacks unless they pay for them. Additionally, Contentstack reserves the right to charge for those stacks retroactively or limit access to certain features (namely Branches) based on unreasonable data usage from the high number of Stacks in that Org.
Contentstack has a number of other parameters that may impact the operation of the Service. In the unlikely event any of these other parameters are exceeded, we will reach out to the customer to identify and address the issue before any further steps are taken