malmoi

Translators never touch Git: they sign in, edit, and hit Publish.

How it works

   push to the base branch (GitHub Actions / GitLab CI) or nightly
  Repository  ──────────────────────────────────────────────▶  Malmoi
  decides which keys exist                         teammates edit values
      ▲                                                          │
      │   one pull request / merge request (Publish or nightly)  │
      └──────────────────────────────────────────────────────────┘

Connect a repository and Malmoi detects and loads its translation files. New commits come in nightly, or on every push with the generated workflow; Publish sends saved edits back as one pull request. The two sides are never merged — the repository decides which keys exist, Malmoi holds the values. GitLab.com works the same way, with a personal access token and a merge request.

Create your first project →

Features

Find, then edit

A source tree and key list on one side, the selected key in every language on the other. Search covers key names, source text, and translations.

Preview every change before it's sent

Publish lists each key × language change before writing anything, and never writes to the base branch — merging stays with your reviewers.

Every change, on the record

Logs records edits, syncs, and publishes — who did what, with translation values before and after — for the life of the project.

One workflow file

A generated GitHub Actions workflow (or GitLab CI job) brings new keys in on every push, flags translations whose source changed as Needs review, and shows where your code uses each key.

• Unsent edits are safe — while edits are unpublished or a Malmoi pull request is open, repository updates wait instead of overwriting them.
• Add or remove languages — Publish creates or deletes the file; removed translations come back if you add the language again (details).
• Nothing is deleted — keys removed from code keep their translations.
• Two roles — owners manage settings and members; editors translate and publish.
• AI agents over MCP — connect Claude Code, Codex, or claude.ai and sign in through your browser; agents can do only what you can. Malmoi itself never calls an AI model (details).
• English, Korean, or Spanish, light or dark — interface and docs.

Supported file formats

Format	Example path
JSON catalog	src/locales/{locale}.json
YAML catalog	config/locales/{locale}.yml
Chrome extension messages	_locales/{locale}/messages.json
Code dictionary, one file per language	src/locales/{locale}.ts
Code dictionary, all languages in one file	src/i18n/namespaces/*.ts
Flutter ARB	lib/l10n/app_{locale}.arb
Apple strings file	ios/App/{locale}.lproj/Localizable.strings
Apple String Catalog	ios/App/Localizable.xcstrings
Android strings file	app/src/main/res/values-{locale}/strings.xml

Publish keeps each file's layout — comments, blank lines, key order, indentation, encoding — as far as the format allows. Plurals (ICU, .stringsdict, Android <plurals>) are kept but not edited. One project can mix several sources and formats. Format-specific rules — such as Android's base language and inline tags — are in the format reference; size caps are in Limits.

What Malmoi doesn't do

Malmoi is a pipeline between your repository and your team, not a translation platform. By design, it has no translation memory or machine/AI translation, no ICU plural editing, no approval workflows or fine-grained permissions, and no real-time co-editing, in-context editing, screenshots, or translator notes. If you need those, a platform such as Crowdin or Tolgee is a better fit.

Under the hood

Exports are deterministic. The same data and original files produce byte-identical files, so Publish commits only the files that actually changed.

On GitHub, commits come from the GitHub App, not from people, so a translator leaving the organization doesn't break the pipeline. GitLab writes as the person whose token the project uses.

More in docs/ARCHITECTURE.md (Korean).

Self-hosting

Use mal-moi.com, or run the same app on one Linux server with Docker Compose (app, PostgreSQL 17, a nightly scheduler, behind your HTTPS proxy). Every release publishes ghcr.io/sinhyeokkang/malmoi:v<x.y.z>. You bring the OAuth apps for sign-in, a Resend domain for invitations, and optionally a GitHub App to connect GitHub repositories. Kubernetes, multiple instances, GitHub Enterprise, and GitLab Self-Managed aren't supported. Self-hosting guide →

Privacy

mal-moi.com sends data only to GitHub, GitLab and Google (if you use them), Supabase (database, Tokyo), Vercel (hosting, pictures, cookieless page-view counts), and Resend (invitation emails). A self-hosted installation uses the operator's own server instead of Supabase and Vercel, and its privacy policy is the operator's own. Full policy →

Development

nvm use            # Node 24
pnpm install
cp .env.example .env.local   # fill in the values
pnpm db:generate
pnpm dev

Commands and conventions are in CLAUDE.md (Korean, also the agent instructions); product scope is in docs/PRODUCT.md. The engineering docs and source comments are in Korean — the project is built by one person, and that's the language it was thought in.

License

MIT © 2026 Sinhyeok Kang