Platform
The Comvi platform is the web app at app.comvi.io where you manage keys, languages and translations, plus the REST API behind it. Production apps read translations from the CDN at runtime or bundle them at build time with the CLI or an export; the REST API is for authoring, automation and dev tooling, not for production reads.
How it fits together
Section titled “How it fits together”flowchart LR
subgraph Manage["Manage"]
Dashboard["Comvi dashboard"]
ICE["In-Context Editor"]
APIin["REST API (push)"]
CLIin["CLI (push)"]
end
Platform["Comvi Platform"]
subgraph Deliver["Deliver"]
CDN["CDN<br/>(runtime fetch)"]
CLIout["CLI pull<br/>(build-time bundle)"]
end
Apps["Your apps"]
Your["Your systems<br/>(CI, Slack, ...)"]
Dashboard --> Platform
ICE --> Platform
APIin --> Platform
CLIin --> Platform
Platform -- deploy --> CDN
Platform --> CLIout
Platform -- events --> Your
CDN --> Apps
CLIout --> Apps
Start here
Section titled “Start here”Your first projectCreate a project, add languages and keys, translate, and get a live CDN URL. No app code.
Connect your appPoint the Comvi i18n library at the CDN endpoint and ship a wording change without a redeploy.
Consume translationsLoad the JSON bundles into any app or runtime, with or without the Comvi i18n library.
Core conceptsProjects, languages, keys, namespaces, statuses and API keys, and how they relate.
Sections
Section titled “Sections”- Content: Projects, Languages, the Translations editor, the translation lifecycle, Namespaces and Import & export.
- Delivery: Content Deploy and the CDN, and API keys for the CLI and automation.
- Quality: Machine translation, AI context, Translation memory and Glossaries.
- Team: Team management and Roles & permissions.
- Integrations: Webhooks.
- Recipes: translator and reviewer workflow, staging to production, CI/CD, scaling to 20 languages, monorepo namespaces, migrating an existing project and onboarding agencies.