What is a request, and will I be charged overages?

A request is a call to the Core dna engine that returns a dynamic page or structured content, such as a headless query or REST API call. Calls to static assets on the CDN do not count. Bands are wide, nothing is metered live, and growing past your band starts a planned upgrade conversation.

Platform & Architecture

A request is a call to the Core dna engine that returns a dynamic page or structured content, such as a headless query or REST API call. Calls to static assets on the content delivery network do not count. Requests sit inside wide bands shown on your dashboard. There are no live meters, and if you are consistently growing past your band we start a planned upgrade conversation with you first.

The practical effect is that traffic spikes do not generate a bill. A campaign, a product launch or a seasonal peak moves you within your band rather than triggering a charge, and because the CDN absorbs the asset traffic that would dominate a metered model, the number that counts is much smaller than your pageviews. Operator includes capacity up to 4M requests a month, and higher tiers are sized to what you run. Sitting above your band consistently is a conversation about the right tier, not an invoice.

More reading

Related posts