Sign in Get started

Reference

Features

Every feature Mergua offers, field by field, with a link onward to the page that documents it.

Still deciding whether Mergua fits? /features walks through the same ground as a tour, starting with branches.

Take the tour →

Editing & Translation

Translation Editor

A side-by-side editor showing source text and translation. Supports three view modes (panel, inline, table), keyboard navigation, search, and status filters. On a phone it is the inline view — source over translation, full width — with the key tree a drawer. Includes character count tracking and the QA checks below.

AI Translation

Translate individual keys or batch-translate all missing translations with AI. Results are saved unreviewed, and as drafts when a placeholder, character limit, protected term or ICU syntax check fails.

Protected Terms

A per-project list of words that stay in the original in every language — product names, brands, a slogan. The editor marks them in the source text, and flags a translation that dropped one. The AI round is given the list and writes a draft rather than refusing when it did not keep a term. The list only protects: it records no target spelling for anything. An owner maintains it under Settings; everybody on the project sees it.

QA Checks

Every translation is compared with its original: placeholders, character limits, protected terms, leading or trailing whitespace, double spaces, empty values marked translated, final punctuation and ICU syntax. Findings show in every editor view, on every upload and in the CI log; they report and never block. A "Has issues" filter and a count per language show what is left, and a finding that is right for one string can be ignored for exactly that text.

Translation Memory

When editing a translation, Mergua shows similar translations from your project. Click to insert — great for keeping terminology consistent.

Translation History

Full audit trail of every change. See who translated, reviewed, or modified a key — with timestamps and the ability to restore previous values.

Collaboration

Branches

Work on translations in isolation with feature branches. Create branches from main, make changes, review diffs, and merge back — just like Git.

Review Workflow

Translations go through Draft → Translated → Reviewed states. Reviewers can approve or reject with comments. Optionally require approval before merging branches.

Review Overview

One page across every project: branches waiting for your review, your own values a reviewer sent back, and comments that mentioned you. Longest wait first, and the count beside it in the header. Three things also reach you by email — a branch sent for review, the mentions you have not read, and your own changes a reviewer sent back, the last two collected rather than sent one at a time. Switch them all off in Settings or from the link in the email itself.

Team Management

Invite team members by email. Assign roles — Owner, Translator, or Viewer — to control access levels across your organization.

Integration & API

Multiple JSON Files per Language

Keep the split your framework already uses — common.json, errors.json, one per area. A project setting decides whether it holds one file per language or several; imports carry the file names in, the editor filters and groups by file, and downloads come back in the same shape. Files can be renamed, merged and deleted. Called a namespace by the CLI and the API.

Import & Export

Upload JSON files (flat or nested) to import keys and translations. Download individual locales or all at once as a ZIP archive.

Pipeline Sync

Integrate Mergua into your CI/CD pipeline. Translations are automatically pulled into your project on every build, with branch-aware matching.

Webhooks

One outbound URL per project. Mergua POSTs to it when translations change or a branch is merged, filtered to one branch — main unless you change it. Every delivery carries an HMAC-SHA256 signature over the raw body, and a burst of writes coalesces into one delivery per language and file rather than one per key. The payload names what changed, never the text itself. A failed delivery is not sent again.

API Keys

Generate project-scoped API keys for programmatic access. Use them in CI/CD pipelines or custom integrations to pull translations via the REST API.

Account

Plans & Billing

Start free, upgrade when your team grows. One flat price per organization, billed monthly or yearly via Stripe. API access, MCP and webhooks from Starter, branches and the review workflow from Pro.

FAQ

Answers to common questions about Mergua — from getting started and branches to Pipeline Sync and billing.