Production checklist

Use this checklist before making a translated language available to customers.

Build and credentials

• Production projectId, environment, and API origin match the dashboard.
• Project token is available only during server/build execution.
• Runtime uses a publishable key, never the project token.
• Translation has explicit target locales, charge ceiling, timeout, and development-only build publish.
• CI retains IDs and redacted diagnostics, not credentials or source bodies.

Runtime resilience

• An embedded original-language file ships with the application.
• Remote catalogs pass schema, integrity, and scope verification.
• Missing, invalid, and failed-load paths render source fallback.
• Server and client begin with the same hydration state.
• Locale cookie, signed-in preference, and routing precedence are tested.

Operations

• Production release policy is explicit and authorized.
• Review queue is clear for the target version.
• Monthly hard cap and estimate acknowledgement are understood.
• A previous catalog has been restored in a rollback rehearsal.
• Published language loading is monitored separately from translation work.

Privacy and observability

• Logs redact source text, translations, authorization headers, provider keys, and payment data.
• Diagnostic callbacks record only codes, language, message IDs, and request IDs.
• Provider data use and retention are approved for production content.

Next

Keep Catalog runtime troubleshooting and Publish a language in the launch runbook.