Flow manages multilingual content at the key level: source text, every translation, context, versions and review state live on one key. Dispatch work by language to multiple vendors, then review and ship from a single system.
Accounts are invite-only · New teams: contact flowsupport@ecinnovations.com
quest.1024.titleThe Silverwood Pact银林之契Publisheditem.0092.descRestores 40 HP over 8s8 秒内恢复 40 点生命In reviewnpc.elder.greetThe forest remembers.森林记得一切。Translatingui.shop.buyBuy now立即购买↻OutdatedKey model
Files are just an exchange format. Flow breaks every localizable string into its own key, and every language, piece of context and revision hangs off it.
01 · Single source of truth
Sync from JSON, CSV, PO and other source files or an engine connector, and every string lands as a stable key. Source changes are detected and affected locales go back to pending.
02 · Every locale
Each target locale sits side by side under its key, with its own status. Review, QA and terminology checks run per key, so progress is obvious at a glance.
03 · Versions & release
Every edit is recorded — diff it, roll it back. Export release bundles by version and locale, so engineering only ever pulls reviewed content.
Multi-vendor
Give different languages and stages to different language vendors instead of shuttling files through email and spreadsheets. Dispatch languages in parallel and track progress, quality and settlement in one place.
zh-CN · zh-TWEditja-JPEditde-DE · fr-FREditAll localesViewSeveral vendors work on different locales of the same keys at once — nobody waits, each locale ships on its own.
Send Japanese to one vendor and German and French to another; progress rolls up on one board.
Compare QA issues, rework rate and turnaround per vendor, and let data decide who gets the next order.
Track delivered volume per vendor and order, then generate statements and performance data.
How it works
From source files in your repo to every line your players and users read.
Connect projects and source files to extract localizable content as keys. Unity projects sync directly through Flow Connector.
quests_en.json1,204 keysitems.csv860 keysdialog_act2.po3,110 keysSynced as 5,174 keys
Pick a key range, target locales and a due date, then create orders for one or several language vendors.
64%
Vendors deliver in a context-rich editor with TM, glossary and QA built in. Reviewed keys ship as a versioned release.
The forest remembers.
森林记得一切。
One workspace
No more one system for you and another for your vendors. Your internal team and every language vendor collaborate in the same workspace: vendors join as teams, conversations need no middleman, and data stays scoped by project.
Keys, orders, queries and linguistic assets live in one place. Your staff and your vendors see the same live data, with no file round-trips.
Each vendor is a collaborator team whose own lead manages its members. Collaborators are not organization members and take no seats.
Questions and discussion attach to projects and keys. Every team on a project shares the answer — ask once, everyone sees it.
Access is granted per project as view, edit or manage. Projects a team is not granted are invisible to it, and revoking takes effect immediately.
View as
Query · Aurora · npc.elder.greetVisible to every team on AuroraCapabilities
Generic tools manage text. Flow binds context, quality and discussion to every key.
Quests, items, characters, storylines and screenshots travel with the key into the translation UI, so linguists know where a line appears.
Appears in quest "Moonshadow Rite"
A herb glowing at night — not "silver leaf"
TM reuse, terminology alerts and placeholder or length checks live inside every key’s workflow — not in a rework pass.
Query puts vendors, PMs and developers in the same thread on the same key, and answers become searchable knowledge.
Is this line sarcasm or literal?
Sarcasm — the NPC is taunting the player.
Resolved · Shared with 3 vendors
Designed for multi-locale, multi-vendor projects: orders, progress, settlement and analytics included.
14 locales · 1.28M words
The details
Not a feature checklist — the parts of the job you actually touch every day.
Sources2
connector.unitySync keys and text assets from inside the engine
assets.mediaText, audio, images and video managed in one place
Quality3
history.diffEvery key keeps its history — diff it, roll it back
tm.reuseReuse existing translations across projects
glossary.alertsProject terminology that flags deviations as you type
Delivery3
orders.localesOne place for orders across languages and vendors
vendor.settlementStatements generated per order on delivery
vendor.analyticsCompare throughput, quality and turnaround by vendor
FAQ
Find more in the product docs, or talk to our team directly.
Every localizable string is a key with a stable identifier. Its source text, translations, context, status and history all live on that key. Files are only an import/export format — collaboration, review and releases all happen per key.
Yes. Each vendor joins as its own collaborator team with view, edit or manage access per project. Split orders by language across vendors and see progress and settlement in one place.
Vendors only see the projects they are granted. Readers of the same project share its collaboration content, such as queries, so answers stay consistent; projects they are not granted stay invisible.
Flow extracts localizable content from JSON, CSV, PO and other source files. Unity projects sync via Flow Connector. See the product docs for more integrations.
Flow is currently invite-only. Existing users can sign in to the app directly; new teams should email flowsupport@ecinnovations.com and our support team will help you onboard.