Getting Started

Ownlate is a translation management platform that brings translators, reviewers, and developers together in one place — from uploading source files to shipping approved translations.

1. Create a workspace

A workspace is your team’s isolated environment. Everything — projects, members, integrations, glossary — lives inside it.

After signing up, give your workspace a name and choose your billing currency. You can invite team members later.

2. Invite your team

Go to Workspace → Members and invite people by email. Each member gets a role:

Role	What they can do
Owner	Full access including billing and workspace deletion
Admin	Manage members and projects, approve translations
Translator	Write translations, save drafts
Viewer	Read-only access

3. Create a project

A project groups all translations for one product or app.

1. Click New Project
2. Choose a source language (the language your developers write strings in)
3. Add one or more target languages

You can add more target languages at any time.

4. Upload a translation file

Go to your project and upload a source file. Supported formats:

• JSON — flat or nested key-value
• YAML
• PO / POT
• Markdown / MDX

Ownlate parses the file and creates one segment per translatable string. A segment holds the source text and all its translations across every target language.

5. Translate

Open the editor. For each segment you’ll see:

• The source text and any context (URL, screenshot)
• Translation Memory suggestions from previously approved translations
• Glossary term highlights
• Real-time QA feedback (missing variables, forbidden terms, HTML tag mismatches)

A translation moves through these statuses:

untranslated → draft → needs_review → reviewed → approved

Translators submit translations, reviewers check them, approvers sign them off. Approved translations are automatically saved to the Translation Memory for reuse in future segments.

6. Speed up with AI pre-translation

Instead of translating from scratch, run Pre-translate on a project to fill segments automatically using:

• Translation Memory — exact and fuzzy matches from your previous work
• Machine Translation — OpenAI, DeepL, Google Translate, Azure, Mistral, or Claude

Pre-translated segments land in needs_review status so your team can review them before approval.

7. Export or distribute translations

Once translations are approved, get them into your app:

• Download — export the file in its original format (JSON, YAML, PO)
• VCS integration — connect GitHub, GitLab, or Bitbucket and push a pull request automatically
• Cloud storage — sync to AWS S3 or Google Cloud Storage
• OTA distribution — create a Release and fetch translations at runtime via the OTA API (useful for mobile apps)
• CLI — use @ownlate/cli to pull translations in your CI/CD pipeline

Next steps

• Set up a VCS integration to automate file sync with your repository
• Configure AI translation to speed up first-pass translations
• Add QA rules to catch errors automatically
• Create a Glossary to keep terminology consistent across your team