— 12 languages, one source of truth —
One workflow, every language
A translation workspace for teams — shared, enforceable decision-context memory and review on every block. Self-serve and transparent: no sales call, free to create and invite, seats only when you want a shared word pool.
Free to begin · No card required
Here to help you translate
A key turned in the lock and the door swung open.
У замку повернувся ключ, і двері розчахнулися.
The knock came just before midnight.
Стукіт пролунав перед самою північчю.
Featured on
How a release ships in every language, from one workflow
- I.
Set up your team, share resources
Create a team, add members by email, share the glossary and styleguide they will all enforce. Pool words at the team level; documents can be scoped to specific people.
Team & resources - II.
One glossary, every release
Build the glossary once at the team level — every translator and every release pulls from the same source of truth. New language pairs reference the same terms; override per locale only when regional usage diverges.
Shared glossary - III.
Refine any sentence — terminology and tone enforced
Sentence-level control at scale. A custom direction ("shorter," "more formal") reworks just the block. The team's shared glossary and styleguide feed in automatically — no out-of-band fixes that break consistency on the next batch.
Direction + team styleguide - IV.
Proofread before delivery
A QA pass over the whole document or a selection. Glossary and styleguide enforced; inconsistent terminology and style deviations flagged. Run it before the release goes out.
Proofread pass - V.
Review where the work lives
Comment threads on any block. Reviewers leave feedback inline; the team resolves and reopens as the discussion lands. No more "the localization tracker doc."
Review mode - VI.
Control who can view, comment, and edit
Roles and granular access, not all-or-nothing. A teammate gets edit; a client gets a comment-only review link that never touches the rest of your workspace; a stakeholder gets view. Four levels — view, comment, edit, admin — on any document, glossary, or styleguide, plus owner and member roles at the team level.
Roles & access
Simple pricing
Pay for words you actually translate — self-serve, no sales call to start. Top up when you need more; extra words don’t expire.
Standard mode spends 1 word per source word. Pro mode uses a deeper model — 3 words per source word. Manual edits, exports, comments, and review activity are free — words are only spent when a block is translated by AI.
Free
Always freeFor your first projects
Unlimited users
Standard mode, 1 word per source word.
- Standard quality — fast, accurate, faithful
- Translation memory — a database of past translations, reused for consistency
- Workflows — chain translate, proofread, and checks into one run
- Glossary, styleguide, QA, import / export — all included
- Notion, Drive, TMX / XLIFF — import, export, bring your own memory
- 50+ languages — from Spanish to Tagalog, shelf to shelf
- 10 lifetime messages with Literess — your agentic AI literary editor, who remembers your projects and preferences
- No credit card required
Starter
For regular client work
Unlimited users
- Pro mode — deeper model for nuance, 3 words per source word
- Batch translation across whole projects
- Unlimited Literess — your agentic AI literary editor: drafts, proofreads, sets things up for you
- Teams — invite anyone free; add €29 seats to fund a shared word pool (100,000/mo each)
- Top up anytime — extra words never expire
Pro
For higher volumeFor agencies & large catalogs
Unlimited users
- 3× Starter’s allowance — headroom for batch work and full catalogs
- Priority support — direct line, faster replies
- Predictable bill — most months covered without top-ups
Prices are in EUR. VAT is added at checkout where applicable — EU consumers see local VAT, while EU businesses with a valid VAT ID pay the net price under reverse charge. Top up any paid plan with word packs — 50,000 words for €19, 200,000 for €69, or 500,000 for €149 — and pack words never expire. Working as a team? Creating a team and inviting people is free; add seats (2 or more) to fund a shared word pool — each seat contributes its plan’s monthly words, on one invoice. Cancel anytime; 7-day money-back guarantee on your first subscription payment, no questions asked.
Estimate the cost of your next project
- Words used50,000 of 100,000 included on Starter
Nothing could translate what we wrote — so we built what could
Two writers, one problem.
— Vitalii.I wrote 120,000 words of satirical romance fantasy — mages drowning in debt, a multiverse economy that makes Wall Street look ethical, and a love story tangled up in all of it.
— Mariia.I write semi-fictional stories about real people, built around how it felt. Most of the people I wrote about were foreigners. We met in English, spoke in English, lived those moments in English. So I wrote them that way too.
“But I sometimes wonder what version of them I missed by not writing them in their language.”Mariia
— Vitalii.The same flatness hit me from the other side. Every tool I tried preserved the words but killed the voice. Tone, rhythm, wit, emotional texture — nothing held. It all came back flatter than it went in.
— Both of us.So we did what we know how to do. We read the machine-translation papers. We benchmarked Claude, GPT, Gemini, and a handful of open models on the same 50-page chapter — judging accuracy, tone, and whether the satire still landed. None of them held all three; each failed in a different way. So we built the tool we wished had existed when we started.
FAQ
- For document and content localization, yes — it’s a lightweight translation management system: shared glossaries and styleguides, batch translation across many files and languages, review threads, and a release-level audit trail. It’s a translation workflow management system rather than an enterprise TMS with vendor marketplaces and procurement gates — so if you’re comparing the best translation management systems for documents (not product strings), it’s the focused, self-serve option. For string-level i18n with CI/CD, pair it with a tool like Lokalise.
- Transparently, and without a sales call. Enterprise TMS platforms are usually quote-gated and priced for procurement — you talk to sales, negotiate seats, and sign a contract. Transept is self-serve: creating a team and inviting collaborators is free on every plan. When you want a shared word budget, buy seats (from 2) — €29/mo each on Starter, €79/mo on Pro, all on one invoice, and every seat adds its plan’s monthly words (100,000 or 300,000) to a shared pool that funds the team’s translation work. Add, remove, or cancel seats anytime — changes prorate automatically. No procurement cycle, no quote.
- Create a team (free, on any plan) and invite collaborators by email — inviting is free and unlimited, and accepting just joins the team. Everyone shares the team’s documents, glossaries, and styleguides, plus comments and chat. To give the team a shared word budget, the owner buys seats (from 2) to fund a shared pool; work on team documents then draws from it. Without a pool, that work simply uses each member’s own words.
- Yes. Glossaries and styleguides are first-class team resources. Add terms once, and every team member’s translations enforce them.
- Yes — both. Connect Notion to import pages and databases, then export translations back to your workspace. Google Drive integration includes a built-in file picker for Drive content.
- Your glossary is the source of truth across every target language. New language pairs reference the same terms; you can override individual translations for a specific target if regional usage differs.
- Words are spent on translation actions (translate, regenerate, improve, fix), not on review activity. A reviewer reading and commenting doesn’t cost you words.
- Yes — block-level version history records every translation action with the actor and timestamp. The activity feed surfaces comment activity across the document. Together they give you a release-level audit trail.
- Four access levels, set per person or per team: View (read only), Comment (read and comment), Edit (read, comment, and edit), and Admin (everything, including re-sharing). At the team level there are two roles — owner (manages members, settings, and words) and member (uses and edits team resources). The document owner and the team owner always have Admin.
- Yes — send a comment-only review link. The client opens it without an account, leaves comments, and only ever sees that one document, never the rest of your workspace. Links expire after 30 days and can be revoked anytime. There’s a view-only link too if you just want them to read.
- Yes. Translation memory is searchable across the team — every approved translation any member makes is reusable by the rest, and feeds the AI on the next run. Scope a search to the whole team, a single project, or one document.
8 hours → 50 minutes
One 40,000-word document, translated by several agents at once, used to take eight hours. We got the agents to sync their memory mid-run, so a term settled in chapter 2 still holds in chapter 40. It now finishes in fifty minutes.
How the syncing works