Skip to content

For enterprises

Enterprise localization you can audit, hosted in the EU

Lionrapid is an enterprise localization platform running on servers we operate ourselves in Finland, built and run by Logoteknia Oy, a Finnish company. Sign-in uses our own identity service with multi-factor authentication your organization can require, roles are scoped per organization and project, the DPA and the 99.5% SLA are published, machine translation runs on models we operate, and every quality check is one you can inspect row by row. Each claim on this page names the mechanism behind it.

Identity & access

Enterprise localization starts at sign-in

Every account signs in through Lionrapid's own identity service. Multi-factor authentication works with an authenticator app, a security key, or an emailed backup code, and an organization can require it for every member and every assignee. Roles are explicit: project manager, translator, reviewer, and proofreader, granted per organization and per project, and every request is checked against that membership before any data is read. When our support staff need to look at a project, they do it through a time-limited grant, and each access is logged.

  • Own identity service (OIDC)
  • MFA: authenticator app, security key, email code
  • Organization-wide MFA requirement
  • Roles per organization and project
  • Logged, time-limited support access

Governance

Terminology enforced, every edit versioned

Approved terms are rules, not suggestions: a mandated or forbidden term that is missed raises a quality-assurance error on the row, and the Finnish checks understand inflected forms. Review runs in stages, with gates that warn or block a hand-off, so a file cannot move on with open issues unless someone with the role decides it should. Every edit to a segment is versioned with its author, and any earlier version can be restored. Before the file leaves, the rebuilt document is compared against the source structure, so a dropped heading or a broken table is a flagged issue rather than a surprise.

In-editor translation memory and QA loopA segment receives translation memory matches and machine translation suggestions, the translator edits it, live QA detectors check the result and offer auto-fixes, and the confirmed segment is written back to the translation memory.SegmentSuggestTM match · MTEdittranslatorLive QAtags · numbers · termsConfirmauto-fix appliedconfirmed segments update the translation memory

Data & compliance

Where your documents are stored and processed

Your files, your translation memories, and the machine-translation models run on servers we operate ourselves in Finland, under Logoteknia Oy, a Finnish company. The data processing agreement is published: Article 28 terms, standard contractual clauses, breach notice within 48 hours, and 30 days' notice before any new subprocessor. Backups are encrypted before they leave the server, stored nightly in Finland, and restored in a rehearsal, not just kept. Machine translation never reaches a third-party AI provider, and entity protection masks names, product codes, IBANs, and URLs before the model sees a sentence. Every provider we do use is named in the subprocessor list with its role and location.

Your text

Pay the deposit to FI21 1234 5600 0007 85 by 12 May — order LR-2041.

What the model sees

Pay the deposit to ⟨IBAN_1⟩ by 12 May — order ⟨CODE_1⟩.

Restored, translated

Maksa varausmaksu tilille FI21 1234 5600 0007 85 12. toukokuuta mennessä — tilaus LR-2041.

the model never sees what must survive — and the date localizes instead of being locked

Integration

Meets your stack where it is

A REST API for strings and continuous localization, a command-line tool whose validate step fails a build on a missing translation, and signed webhooks for the systems that need to know when something changed. API keys come in classes, can be narrowed to fewer scopes, and expire on a date you set. Content systems connect through the Contentful connector, the custom-CMS connection with its suggestions loop, the WordPress plugin, or the edge proxy that serves a translated site without touching its code. Documents travel as DOCX, ODT, PDF, XLSX, PPTX, CSV, XML, DITA, and HTML; strings as JSON, YAML, PO, ARB, Apple and Android resources; subtitles as SRT and VTT; and translation assets as XLIFF, TMX, and TBX, in and out.

Edge proxy integration modesYour website connects to Lionrapid through one of four modes — at the CDN edge, through a WordPress plugin, with a JavaScript snippet, or via the REST API — and visitors receive translated pages.Your siteany platformCDN edgetranslate at the edgeWordPressplugin + resyncJS snippetone tagREST APIfull controlLionrapidTM · MT · QAVisitorstranslated pages

Cost

Costs your procurement team can audit

Rate cards belong to the organization, so pricing is a policy rather than a negotiation per file. The analysis that buckets a document into translation-memory bands is hashed and stored, which means the same file always produces the same quote, and anyone can re-derive the number later. Offers to translators show the full calculation, payment is held until the project manager accepts the delivery, and usage is billed by the word. Translation memory is included on every plan, so what you pay for once keeps lowering the next quote.

CAT-band quotingFiles are analyzed against attached translation memories into six match bands — repetitions, exact matches, three fuzzy bands, and new words. Rate-card multipliers price each band, producing a reproducible quote with a verifiable hash.Analysisfiles × your TMRepetitionsExact matchesFuzzy 95–99%Fuzzy 85–94%Fuzzy 75–84%New wordsRate cardper-band pricesQuotereproducible

FAQ

Enterprise localization, answered

Where your data lives, in detail: how Lionrapid keeps your documents in the EU and the security page.

Product

Bring the pilot project

Run one real workflow end to end, with your glossary and your reviewers, and measure it.