Everything Ownlate does, and how to use it.

One page takes you from an empty workspace to a translated build. The rest goes as deep as your work needs: the editor and review for translators; the CLI, the API and over-the-air releases for developers; members, settings and billing for whoever runs the workspace.

Get started API reference

A new workspace starts on the free plan. No card needed.

~/checkout zsh

$ ownlate login      # store an API key
$ ownlate init       # pick a project, write the config
$ ownlate push       # upload source strings
$ ownlate pull       # download translations
$

Start here

What Ownlate is made of, and the path from the first file to an approved translation.

Getting started: Create a workspace, upload a file and translate your first segment.
Core concepts: Workspaces, projects, files, segments and translations — and how they nest.
The editor: Views, filters, plural forms, the assist panel and the keyboard shortcuts.
Translation workflow: Statuses, review and approval, bulk actions, tasks and suggestions.

Getting more out of it

Catch mistakes early, reuse approved work, let a machine draft the rest, and know which formats go in and out.

Quality and glossary: Automatic checks, your own rules, and terminology that stays consistent.
Translation memory: Reuse approved work, and fill a language before anybody opens the editor.
AI translation: Six providers, the built-in engine, and what each one costs you.
Files and export: Nine formats in, three formats out, and what happens on a re-upload.

For developers

Get strings in and translations out from a shell, a pipeline, a repository, your own code or an AI assistant.

Releases and OTA: Ship a translation change without shipping a build.
Integrations: Git sync and pull requests, chat notifications, signed webhooks.
REST and GraphQL API: Authentication, error shapes and the full endpoint list.
CLI: Push, pull and gate your pipeline on translation coverage.
SDKs and clients: Go, Rust and NestJS at runtime; in-context editing in the browser.
MCP server: Let an assistant work in your workspace, within permissions you choose.

Administration

Who can do what, how the workspace is set up, and what it costs.

Members and access: Levels, permission codes, invites, API keys and tokens.
Workspace settings: Notifications, metrics and the language catalogue.
Plans and billing: Limits, how words are counted, and how to pay.