Product · Translation management system
A translation management system with the editor built in
A translation management system is where projects, people, files and deadlines are managed. Lionrapid is one with the rest of the job on the same platform and the same price ladder: the CAT editor, the translation memory and termbase, the quality checks, the quoting and the localization API. Assignment happens by offer, stages carry QA gates, the PM cockpit shows every project, every quote re-derives to the same number, and all of it runs on servers we operate in Finland. Translation memory and terminology on every plan, including the free one.
What a translation management system does, and where Lionrapid does it
- Projects and files. Upload, stages, deadlines, delivery: the workflow.
- People. Offers to ranked translators, a searchable people directory, roles per organization and project: assignment.
- Memory and terms. One translation memory that fills the editor, prices the quote and decides when machine translation is not needed; a termbase that enforces mandated and forbidden terms: translation memory.
- Quality. Eighteen checks in the editor, structural checks on the rebuilt file, quality estimation on every machine-translated row, QA gates per stage: quality assurance.
- Money. CAT-band analysis, rate cards, hashed quotes anyone can re-derive: quoting.
- The editor. A CAT editor on every plan, the whole document loaded at once: CAT editor.
- The pipeline. A REST API, a JavaScript SDK, an edge proxy, a WordPress plugin, XLIFF, TMX and TBX: developer API and integrations.
Document translation, software localization and website translation in one product, with one price ladder.
- tools that usually cost six subscriptions, on one login
- 6
- languages in the catalog
- 345
- file formats, layout intact
- 13
- published monthly availability, with service credits on paid business plans
- 99.5 %
Projects and stages
Your process as stages, each with a QA gate
Model your actual process as workflow stages, translation, review, quality check, whatever your projects need, and save it as a template for your organization. Each stage can carry a QA gate that warns about or blocks on open issues, so nothing advances that should not.
Roles are scoped per organization and project: project manager, translator, reviewer, proofreader. Progress is visible per file and per stage, and a client can follow it without an account of their own.
- Configurable stages
- Org, personal and global templates
- QA gates: warn or block
- Roles: PM, translator, reviewer, proofreader
People
Assignment by offer, ranked by fit
Send an offer and the platform ranks candidates by real fit: language pair, service capability, domain experience, with a daily fairness rotation so good work is spread rather than hoarded by the algorithm. Terms can be negotiated with counter-offers. The first acceptance fills the seat, the other offers close automatically, and work only starts once the assignment is confirmed.
A people directory with translator profiles, work history and capabilities keeps your talent pool searchable, whether the translators are in-house, freelance, or found through the platform.
- Ranked offers
- Counter-offers
- First acceptance fills the seat
- Searchable people directory
The cockpit
Progress per project, file and stage; deadlines watch themselves
Status updates land in the PM cockpit live, without a refresh: charts, not chases. Deadline notifications fire at 72 hours, 24 hours and overdue, so nobody discovers a late delivery by accident. Chat threads run at the project level and on each document, and notifications cover the whole lifecycle, offers, messages, stage changes and deadlines, in the app and by email.
On the Company plan an optional client portal lets your clients sign in with a magic link, see status and download deliverables, with no account to manage.
- Live progress charts
- T-72h, T-24h, overdue alerts
- Project and document chat
- In-app and email notifications
- Client portal (Company plan)
Memory, terms and checks
One memory that fills the editor, prices the quote and skips machine translation
Every confirmed segment is written into the translation memory, with a ten-version history and a client's authoritative memory written only at payment. The same memory surfaces exact and fuzzy matches in the editor, prices the quote by CAT band, and lets segments close enough to a past translation skip machine translation entirely. The termbase is lemma-aware in about 35 languages, and a mandated term you missed or a forbidden one you used is a QA error on the row, not a suggestion.
Eighteen checks run in the editor, eleven of them live as you type; structural checks compare the rebuilt document against the source across 49 issue types and 33 document detectors; every machine-translated row gets a quality estimate you can route by. Memories and termbases leave as TMX and TBX, translations as XLIFF, on every plan, and nothing expires.
- Translation memory on every plan, including Free
- Termbase on every plan
- 18 checks, 11 live as you type
- Structural rebuild-and-diff
- Quality estimation per MT row
- TMX, TBX, XLIFF in and out
Money
Quotes that re-derive to the same number
Every project file is analyzed against the attached translation memories and each row lands in one of six CAT bands, from repetitions down to genuinely new text. Rate cards with per-band multipliers price each band, and the analysis snapshot is hashed: run the same files against the same memory in a year and the number does not move, so a quote can be audited months later.
Offers to translators show the full calculation, payment is held until the project manager accepts the delivery, and machine translation is billed by the word.
- Six CAT bands
- Org rate cards
- Hashed, reproducible quotes
- Offer math shown in full
- Payment held until acceptance
The pipeline
An API for content that never stops changing
A REST API keyed by locale, namespace and key, a universal JavaScript SDK, and continuous projects that never finish by design. ICU MessageFormat is parsed properly, so plurals, selects and nested messages survive translation with their structure intact. Sites connect through the edge proxy or the WordPress plugin; content systems through connectors or the interchange formats.
A command-line validate step fails a build on a missing translation, signed webhooks tell the systems that need to know when something changed, and API keys come in classes, can be narrowed to fewer scopes, and expire on a date you set.
- REST API and JS SDK
- Edge proxy and WordPress plugin
- CLI validate --ci
- Signed webhooks
- ICU MessageFormat
- XLIFF, TMX, TBX
Hosting
Servers we operate in Finland, a published DPA and SLA
Your files, your translation memory and the machine translation itself run on servers we operate ourselves in Finland, on models we host, with entity protection masking names, codes and URLs before the model sees them. The data processing agreement is published, with standard contractual clauses and a 48-hour breach notice; the service-level agreement is 99.5 % monthly availability with service credits on paid business plans, measured on a status page that checks every minute. Sign-in uses our own identity service with multi-factor authentication your organization can require.
- Servers we operate in Finland
- Models we host
- Published DPA
- 99.5 % SLA
- MFA, organization-wide
- Status page measured every minute
FAQ
Translation management systems, answered
Translation management software is where translation work is run rather than done: projects and files, the people assigned to them, the review stages, the deadlines, the memory and terminology they share, and the API that feeds content in and out. Lionrapid is a translation management system that also carries the doing: the CAT editor, the quoting and the quality checks sit on the same platform and the same plan.
A CAT tool is where a translator translates: segments, matches, terminology, live checks. A TMS is where projects, people, files and deadlines are managed. Many stacks pair one vendor's TMS with another's editor; in Lionrapid both are one product, so the memory that fills the editor is the memory that prices the quote and gates the stage. The editor has a page of its own; assignment, stages and deadlines live in the workflow.
Translation memory and a termbase on every plan, quality checks that can gate a stage, assignment that reaches the right translator, quotes derived from memory leverage rather than a sales estimate, an API for continuous content, export of your own assets whenever you like, and hosting you can name. Some platforms put translation memory behind a €699-a-month plan while giving machine translation away, and it is common to find quality checks behind a €179-a-month tier. Here they are on every plan; you pay for machine translation by the word, because that is the part that costs compute.
Six plans, from a free editor to full agency workflow: Basic at €9.90 a month including VAT, Pro at €24.90, Studio at €59.90, Business at €99 with five seats included, Company at €249.90 with twenty, and a Free tier with 3,000 words on real documents. Subscriptions cover the platform; machine translation is priced by the word, with word packs beyond the monthly allowance, and paid plans include a 14-day trial on paid plans. Every price is on the pricing page; some platforms in this category publish no subscription price at all.
The Free tier is the full CAT editor on real documents with 3,000 words to start, valid 90 days, plus the PM dashboard, reports and custom workflow authoring, and it is private by default. Free plans elsewhere can expire in 7 to 14 days, or archive your projects and charge you to download your own files; here your translation memory does not expire and leaves as TMX whenever you ask.
Yes. Attach an SDLXLIFF or MQXLIFF from Trados or memoQ to a document as its segmentation and pre-translation source, and round-trip TMX memories, TBX termbases and XLIFF files, so Lionrapid fits inside a workflow your clients already mandate. Export is never gated by a plan; on some platforms it is a €299-a-month feature.
Yes. API keys are live in the app: a REST API keyed by locale, namespace and key, a JavaScript SDK, a command-line tool whose validate step fails a build on a missing translation, signed webhooks, and continuous projects. Sites can skip the API entirely with the edge proxy or the WordPress plugin. Details on the developer API page.
On servers we operate ourselves in Finland, run by Logoteknia Oy: files, translation memory and the machine translation itself. The data processing agreement, the subprocessor list and the service-level agreement are published, and the status page measures uptime every minute. More on hosting in the EU.
Create your organization and run the first project
Free to start with 3,000 words; the editor, the memory and the terminology are there from day one.