Glossary
These are the terms you will see while connecting your app and managing translations.
| Term | What it means |
|---|---|
| Organization | The team that owns projects, memberships, billing, and spending limits. |
| Project | One application's source language, builds, target languages, catalogs, and credentials. |
| Environment | A named scope for build credentials and release pointers. Start with development; production has explicit publishing. Inspect the environments actually present in your project. |
| Build | Text found during an application build, with source locations and context. The SDK and HTTP API call its artifact a manifest. |
| String | A piece of source text plus its placeholders and context. The SDK and stored data may call it a message. |
| Language / locale | A language code such as fr or a regional code such as fr-CA. The registry labels locales Supported, Preview, or Certified. Enabling a locale does not publish it. |
| Translation version | A recorded wording for a string in a target language. A human edit creates a new version. |
| Accepted | A translation has passed acceptance or a human decision. It can contribute to a catalog; this says nothing about which release is live. |
| Ready catalog | A complete, validated catalog available for publication. Pending or rejected work can prevent readiness. |
| Catalog | A versioned language file mapping messages to translated text for a project and environment. |
| Release / published | An environment's active pointer selects a catalog version for runtime delivery. Publishing and restoring change that pointer. |
| Source fallback | The original text remains readable when a translation is absent or cannot be loaded. You can also explicitly approve source wording for an individual string. |
| Project token | A secret credential scoped to a project and environment, used by builds and CI. It must stay out of browser code. |
| Publishable key | A browser-safe credential for reading runtime configuration and published catalogs. It cannot edit translations. |
| Product glossary | Versioned rules for product terms used during translation and validation. This terminology page is separate from those project rules. |
| Translation memory | Compatible prior translations reused to avoid translating the same content again. |
| Spend reservation | The maximum charge set aside before an active translation run; completed work commits usage within that authorization. |
Follow a string through the product
A build discovers a source string. A translation run prepares target wording. Review or an edit accepts a version. A complete catalog becomes ready. Publishing makes that catalog available to the runtime. The app retains source fallback throughout.
Understand builds, strings, catalogs, releases, environments, and credentials.
Last updated October 3, 2026
Did this page get you to a working result?