— 68 languages, one source of truth —
One workflow, every language
No cardFirst 5 pages freeYour work never trains AI
Built for work you answer for
Private by default
Your text is never used to train AI, not by us and not by any provider we use, and it stays out of our logs. Delete your account and your text is deleted with it.
How we handle dataSecurity you can check
Hosted in Germany, in Hetzner’s ISO 27001-certified data center. Every sub-processor is listed, and a DPA is one email away.
All sub-processorsGive it context
Glossaries, styleguides, translation memory and per-string notes go with every request. You set them up once per project.
GlossariesYou’re the human in the loop
The AI drafts; you decide. Review every change side by side, keep or revert it, and send a review link when a client needs to look.
Review linksAPI, MCP and webhooks
The full API on every paid plan. Connect Claude or another AI assistant over MCP, or start runs from your own tools.
Developer guideSomething bigger?
Large catalogs, custom workflows, a DPA for procurement. Transept stays self-serve; write to us for the rest.
support@transept.aiHow a release ships in every language, from one workflow
I.Set up your team, share resources
Create a team, invite members by email, and share the glossary and styleguide that apply to everyone’s work. Pool credits at the team level, and limit any document to specific people.
II.One glossary, every release
Build the glossary once at the team level, and every translator and every release draws on the same terms. New language pairs use them too, and you override a term for one locale only when regional usage differs.
III.Refine any sentence without losing terms or tone
Type a direction such as "shorter" or "more formal", and only that block is rewritten. The team's shared glossary and styleguide apply automatically, so a one-off fix never breaks consistency on the next batch.
IV.Proofread before delivery
Run a QA pass over the whole document or a selection before the release goes out. It checks the text against the glossary and styleguide and flags inconsistent terminology and style deviations.
V.Review where the work lives
Reviewers comment on any block, right in the document, and the team resolves or reopens each thread as the discussion moves on. No more "localization tracker" doc.
VI.Control who can view, comment, and edit
Give each person the access they need. A teammate can edit, a client gets a comment-only review link that shows nothing else in your workspace, and a stakeholder can view. There are four levels (view, comment, edit, and admin) on any document, glossary, or styleguide, plus owner and member roles at the team level.
Who did what, on every document
Each document keeps one activity list for the whole team: who edited, who accepted a fix, who approved a review, and what the AI wrote. Download it as a report for a client or an audit.
- Counted by word. The words the AI wrote, the words you changed and the paragraphs you wrote yourself, each counted on its own.
- Every step on record. Translations, rewrites, fixes, your edits and your approvals in one list, each line marked as yours or the AI's.
- Your sign-off, dated. Before the PDF downloads, Literess asks whether you read the translation through. Say yes and the report records it.
Two reports on the Free plan, unlimited on every paid plan.
Originality report
Chapter 3 · Ukrainian → English
Reviewed in full by the author, confirmed on Oct 21, 2026
Simple pricing
1 credit = 1 source word. Pro mode costs 3 credits per word. What each action costs
Free
Always freeFor your first projects
Unlimited users
Translated and proofread on Standard. About five with Pro.
- Pro mode: the model thinks each passage through, 3 credits per source word
- Standard quality: fast, accurate, faithful
- Translation memory: your past translations, reused to keep new ones consistent
- Glossary, styleguide, QA, import / export: all included
- Notion, Drive, TMX / XLIFF: import, export, and bring your own memory
- 68 languages: from Spanish to Tagalog
- Paragraph-by-paragraph translation in every mode
- Literess, your AI literary editor: 10 messages free, then credits
- Originality reports: 2 included
- No card required
Lite
The pocket edition
Unlimited users
- Whole pages and documents in one run
- Unlimited originality reports
- Workflows: chain translation, proofreading, and checks into one run
- API, MCP & webhooks: automate runs, or let AI assistants work in your account
- Teams: create as many as you need and invite anyone for free
- Top up anytime: pack credits never expire
Starter
Most popularFor regular client work
Unlimited users
- 3× Lite’s credits: for weekly work
- Teams: invite anyone for free; add €29/$33 seats to fund a shared credit pool (80,000 credits a month each)
Pro
For higher volumeFor agencies & large catalogs
Unlimited users
- 3× Starter’s credits: headroom for batch work and full catalogs
- Priority support: a direct line and faster replies
- Predictable bill: most months need no extra credit packs
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.
Vitalii VlasiukCo-founder
Mariia IvakhnenkoCo-founder
“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 and judged them on 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.
We still use it every day. This site is localized in Transept: every change to its German, Japanese and Chinese pages goes through the same workflow you'd use.
FAQ
- For document and content localization, Transept is a lightweight translation management system with shared glossaries and styleguides, batch translation into many languages, review threads, and a release-level audit trail. It’s a translation workflow management system, not an enterprise TMS with vendor marketplaces and procurement gates. 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.
- Transept’s prices are public, and you never need a sales call. Enterprise TMS platforms usually quote on request and price for procurement: you talk to sales, negotiate seats, and sign a contract. Transept is self-serve, and creating a team and inviting collaborators is free on every plan. For a shared credit budget, buy seats (minimum 2) at €29/$33 a month each on Starter or €79/$90 a month on Pro, all on one invoice. Each seat adds its plan’s monthly credits (80,000 or 240,000) to a shared pool that funds the team’s translation work. Add, remove, or cancel seats at any time: an added seat is prorated for the rest of the period, and a removed one comes off the next invoice.
- Create a team (free on any plan) and invite collaborators by email. Invites are free, teams have no member cap, and accepting an invite adds the person to the team. Everyone shares the team’s documents, glossaries, and styleguides, plus comments and chat. To give the team a shared credit budget, the owner buys seats (minimum 2) to fund a pool, and work on team documents draws from it. Without a pool, that work uses each member’s own credits.
- Glossaries and styleguides work as shared team resources. Add a term once, and every team member’s translations follow it.
- Both are supported. Connect Notion to import pages and databases, then export the translations back to your Notion workspace. For Google Drive, a built-in file picker lets you choose files from your Drive.
- The terms carry over: your glossary is the source of truth for every target language. A new language pair uses the same terms, and you can override a term’s translation for one language when regional usage differs.
- No. Reading and commenting cost nothing. Credits are spent on AI actions, each priced before you click: translating, rewriting, sentence alternatives, fixes, proofreading and checks, building glossaries and styleguides, and Literess’s edits.
- Each block’s version history records every translation action, with who made it and when. The activity feed shows comment activity across the document. Together they give you a release-level audit trail.
- Every document keeps one activity record for the whole team, and the originality report turns it into a PDF: the share of words people wrote or changed against the AI's, the paragraphs a person reviewed, and each teammate's edits and approvals by name. Every paid plan downloads as many reports as you need.
- There are 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 credits) and member (uses and edits team resources). The document owner and the team owner always have Admin.
- Send a comment-only review link: the client opens it without an account, leaves comments, and sees only that one document, never the rest of your workspace. Links expire after 30 days, and you can revoke one at any time. If you only want them to read, there’s a view-only link too.
- Translation memory is searchable across the team: any member’s approved translations can be reused by everyone else and feed the AI on the next run. You can search 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 worksFeatured on
