For product teams

Change the text in your app without waiting for a developer

A typo on the checkout button, a call to action marketing wants reworded, a legal sentence that has to read exactly as written. None of them is a code change. In Mergua the person who owns the words edits them in the browser, and your pipeline ships them.

Create your account Read the guide

Works for an app in one language
No code editor
Ships through your own pipeline

Everyone keeps the part that is theirs

The words are already data: every visible string is a key, and its text sits in a locale file. Mergua holds those files, so nobody has to open the repository to change one.

You own the words

Translator role

Edit every value and open a branch for a change. Nothing in the project settings, nothing in the code.

Someone signs it off

Owner or Maintainer

Approves each change on the branch and merges it. With approval on, the default, nothing merges unreviewed.

The developer, once

Sets up the pipeline

Adds the sync script to the build and points a webhook at the CI server. After that, a copy change is not their ticket.

Edit, review, merge, ship

The path a copy change takes, with nobody in it who does not need to be.

Step 1
Edit the wording on a branch
Open the key and change its value in the browser. The change stays on its branch, invisible to the app until it is approved.
Step 2
Get it approved
A second pair of eyes on the legal sentence, or the product owner signing off the new call to action. The approval sits on the value, with the reviewer's name beside it.
Step 3
Merge it into main
The approved change lands where your release reads its files from.
Step 4
Your pipeline ships it
The merge starts your build through a webhook. The build pulls the files and deploys. Nobody opened a ticket.

Live means live with the next build, not the moment you press save. The words are bundled into the app, so they reach users through your pipeline, staging included, like every other change.

What each plan gives this flow

Worth checking before you promise it to a team.

Free

Edit every value in the browser
No API access, so no sync script and no webhook
No branches, no review

Somebody downloads the file and commits it. The ticket goes away; the developer does not.

Starter

Edit every value in the browser
API access: the pipeline fetches the files and the webhook starts it
No branches, so no review step

An edit goes straight to main and ships with the build it triggers.

Pro and up

Edit every value in the browser
API access, sync script and webhook
Branches and the review workflow

A change waits for an approval before it reaches main and the pipeline: the whole flow above.

Pricing has the limits and the prices.

What stays with the developer

Said up front, so nobody finds out in the middle of a launch.

A new text in a new place

A new key needs a line of code that shows it. Rewording an existing one does not.

Text that has to fit

A character limit on the key, set by whoever knows the layout, warns you while you type rather than after the build.

Placeholders

In Hello, {name} the {name} is filled in by the code. The editor flags one you removed or renamed.

For the developer: the webhook reference

Fix the wording this week, not next sprint.

Bring your developer the setup once, and keep every change to the words after it.

Create your account

Read the guide