locoloop vs Loco: the same simplicity, with variants and a review step
Loco (localise.biz) is a small, fast, well-made string manager, and for a single app with one set of wording it is genuinely hard to beat on simplicity. locoloop starts from the same place and goes one step further.
You ship the same product to more than one client or market and the wording differs per customer; you want AI translation with a glossary and a review step rather than a plain string store; or you want a coding agent to be able to write strings through MCP.
You have one app, one set of wording, no variants and no review workflow, and you want the smallest possible tool that does exactly that. There is no shame in it — it is a good answer to that question.
Where we genuinely differ
Variants that inherit
A locoloop project overrides only the strings one client needs and reads the rest through to the default, permanently. Change a shared string and every variant that had not overridden it follows on the next pull. There is no copy to keep in sync, because there is no copy.
A review state that means something
Translations carry needs review separately from translated. A locale can be 100% translated and 0% reviewed, and GET /status will tell your build so.
Registers, not just languages
German du and Sie are a setting per locale across thirty-five languages, and a formal variant can be rebased on its approved informal sibling rather than translated twice. How that works.
Try it against your own strings, not our page
Import a file, translate a locale, decide in an afternoon. Free while you are evaluating.