Gaming Solution

More Than Strings,
The Whole Pipeline

Every language in one view. Every linguist in one platform. Every string from intake to live patch in one system. Wordbee is the localization operation for studios that ship without slowing down.

Connects to the Tools and Pipelines You Already Use

UnityGitGitHubGitLabBitbucketSubversionGoogle SheetsDeepLGoogle TranslateUnityGitGitHubGitLabBitbucketSubversionGoogle SheetsDeepLGoogle Translate

The Problem, and the Loop

Six Steps From Build Drop to Shipped Patch

A live-ops title ships in dozens of languages on a relentless cadence. Route every job by hand, lose context between tools, and the patch waits on the slowest language. Wordbee runs the whole loop in one platform, so every step moves without stalling.

Patch Pipeline · Live-Ops Cycle
  1. and back to the next build drop

Step 1 · Build

Build Drop

A patch, a DLC, or a seasonal event drops. New strings land wherever they live, the engine, the repo, or a sheet, and Wordbee pulls them in without anyone copy-pasting.

What Wordbee Does

  • Unity package pulls strings on build
  • Tracks your release branch and pulls new strings automatically
  • Flex API pushes .wbflex containers on demand
  • Hot folders for teams still on file drops

Multicolumn CAT Editor

Source Target Context All in One View

A game linguist needs more than two columns. Add a column for a reference language the team already signed off on, and another for an alternate variant. Pull in speaker names, gender, formality, and character limits so the person doing the work sees what the string is actually for, and the loc manager never fields the same context question twice.

  • As many live target columns as you need, plus source, all editable inline
  • Reference columns for approved prior translations or alternate variants
  • Media and reference files attached to segments for on-screen context
  • Per-row character limits enforced as you type
  • Custom fields such as speaker, scene, and formality shown alongside the string
  • Translation memory and termbase matches suggested as you work
Editor · One Row, Every Column
Side by Side
Every column for the same string, at once. Source, pivot, and as many live targets as you need, with reference media, the speaker, and the character limit that explain the line, all aligned in one view.

Vendor Network & Access

Your Whole Network, Scoped to the Job

A seasonal drop in thirty languages is not a routing problem to solve by hand in a spreadsheet. Build your network once, freelancers, agencies, in-house, and AI, then let each job find the right person by the criteria you set. Unreleased titles pass through external hands, so every login opens only the work it touches.

  • Build pools by language, domain, task type, and rating
  • Auto-propose to a group, and the first qualified linguist to accept gets the job
  • Freelancers work in the browser through a portal, no desktop app to install
  • 125 access rights scope freelancers and partner studios to only their work
  • Per-client and per-project visibility for outside studios on unreleased titles
  • Exportable Activity Log: every string, every user, every change
Automated Assignment
By Your Rules
Your network
Freelancer
LSP
AI Agent
In-house
The right supplier, by rule. Set the criteria once. Every job is matched across your whole network on language pair, domain, task type, and rating, and proposed to the best fit automatically.

Built to Ship

Into the Engine, Clean Before Cert

Wordbee plugs into the build pipeline your studio already runs, and settles quality before anything reaches certification.

Engines and Repos

The Unity connector round-trips strings with source control intact, Git connects through the Beebox connector, and the Flex API moves .wbflex containers through CI/CD build pipelines.

Read more

QA Before Ship

Configurable rules catch character-limit overruns, terminology slips, forbidden terms, and placeholder or tag breaks, and a mandatory gate holds the job until they clear.

Read more

Incremental Delivery

Confirmed strings push back the moment they clear QA, so each language goes live as soon as it is ready instead of holding the whole patch for the slowest one.

Why It Wins for Live-Ops

Ship Every Language, Without Waiting on the Slowest

The whole point: a patch goes live everywhere at once, your unreleased build stays locked down, and quality is settled before cert.

  • Incremental delivery means one slow language never holds the patch
  • Scoped access keeps unreleased titles locked to the people working them
  • MT from DeepL, Google, and Microsoft seeds high-volume live-ops content
  • AI agents run context-aware checks on top of human post-editing
  • QA gates clear placeholders, forbidden terms, terminology, and length before cert
  • One TM and termbase keep terminology consistent across the whole title

Common Questions

What Game Teams Ask Us

Ship Your Next Patch in Every Language

Book a working session with our team, who know live-ops cadences, engine pipelines, and what it takes to get LQA through cert on deadline.