Solutions · five audiences

Every team hits the same wall in a different language

Five audiences, one platform. Each page states the workflow it replaces, the capabilities that matter to that team, and the limits that still apply today.

Start free See pricing

Audience pages

File formats

Integrations

By audience

Find yourself on this list

Same platform, five different first weeks. Each page argues from the friction you already have, not from a feature list.

Five pages · one product

Path 01

For developersManage i18n as code: a REST API to pull and push your strings, signed webhooks to trigger on your pipeline, and native file formats for the stack you already run — no spreadsheets, no manual hand-offs.Read →

Path 02

For localization managersSee exactly where every string stands, keep human translators and AI drafts moving through the same workspace, and lean on translation memory so nobody re-translates the same sentence twice.Read →

Path 03

For game studiosGames are string-heavy and unforgiving: dialogue, item and skill names, tooltips, and lore all have to read right and fit the box. Translate them on the screen they appear on, keep every term consistent, and catch overflow and broken placeholders before a player screenshots them.Read →

Path 04

For agenciesKeep each client’s project isolated with its own seats and settings, move faster with AI-assisted translation and memory, and hit delivery dates without adding headcount.Read →

Path 05

Open sourcetransglot is open-source under the MIT license: a modern, present-day alternative if you’re migrating off Texterify or evaluating tools like Weblate or Tolgee. It’s a standard Laravel app you can self-host today — there’s no Docker image or one-click installer yet (packaged Docker and enterprise air-gap are on the roadmap), or skip the ops and use our hosted cloud.Read →

What every audience gets

The same platform underneath

These four numbers do not change with the page you are on. Each one points at the file that decides it.

Native file formats, imported and exported, in every plan.

APP/ENUMS/FILEFORMAT.PHP

Marketplace integrations: connectors, design plugins, developer apps.

CONFIG/INTEGRATIONS.PHP

Signed webhook events, with the last 50 deliveries logged and redeliverable.

DEVELOPER PLATFORM

Organization roles, plus per-project and per-language grants — on every plan, Free included.

CONFIG/PLANS.PHP · NO RBAC FEATURE

Your first week

A rollout you can put in a plan

This is the order the product is built to be adopted in, not a benchmark. Every gate named here comes from the plan matrix on the pricing page.

Plan gates from config/plans.php

DAY 1

Import what you already have

Create a project, push your existing locale files in any of the twenty formats, and add the languages you sell in. Nothing is rewritten on the way in.

20 FORMATS · EVERY PLAN

DAY 2

Draft the untranslated keys

Batch AI translation drafts every missing string with Claude. Placeholders and tokens survive because the pipeline is structured output, not free text.

AI TRANSLATION · EVERY PLAN

DAY 3

Fix the terminology

Load a glossary from TBX or CSV. Mandated terms ride into every relevant AI call and are checked deterministically afterward; a forbidden rendering is a hard failure.

GLOSSARY · INDIE AND UP

WEEK 1

Make it a pipeline step

Pull and push from the CLI or the GitHub Action, subscribe an endpoint to batch.completed, and gate a merge on the placeholder and plural pre-gate.

QA · TEAM AND UP

Keep reading