Usage & spend

Note

This page is about what your DeepL or Google Cloud Translation account gets billed for translating your site. It has nothing to do with your LocaleReady license or CloudCatch’s own billing — see account and billing for that. Need the key itself? Get a translation API key.

The Usage & limits tab under LocaleReady → Settings is where translation spend is watched and capped.

A monthly character limit

Set a ceiling on how many characters may be sent to a translation provider in a calendar month. At zero (the default) there is no limit. Once one is set:

• Under 80%, nothing changes.
• 80% to 100%, a warning appears on every LocaleReady admin screen and in Site Health.
• At or over 100%, the provider stops being called. Everything already translated keeps being served exactly as before — only strings that would need a new provider call fall back to the source language, until the calendar month ends or you raise the limit.

The point is bounding the worst case, not the common one: a crawler that discovers ten thousand untranslated pages in an afternoon is a real bill, and a limit is what keeps that from becoming your bill without you knowing it happened first.

Usage this month

Below the limit, a table shows exactly what has been sent to each connected provider this month — characters, strings, and requests — reset at the start of each calendar month. This is the number that turns into a line on your DeepL or Google Cloud invoice; anything already stored in translation memory costs nothing to keep serving.

Non-production environments

Outside of a production environment, LocaleReady does not call a translation provider at all by default. A staging copy of your database carries the same provider credentials as production, and the first page load there — from a developer, a client, an automated test — would otherwise bill the production account for strings nobody but that visitor will ever read. Turn on Allow provider calls outside production only for a non-production site that is genuinely meant to spend, such as a permanent staging environment translating its own content. A LOCALEEASY_ALLOW_PROVIDER constant in wp-config.php does the same thing from the deployment side, for a site where you would rather not store that choice in the database.

Stored translations are always served regardless of environment — only new provider calls are withheld.