ResilientLang
Get started

How it works

Two planes that share only static files: a control plane where you work, and a delivery plane that visitors use.

How translations reach a visitorYour page is scanned and translated in the control plane, which can be offline. The result is published as a signed bundle of static files to three places: your own site and two independent CDNs. A small loader in your page reads the bundle from any of them and shows the visitor the translated page. Visitors never contact the control plane.Your pageany websiteScan, translate,review, publishcontrol planecan be offlineSigned bundlestatic filesYour own siteCDN ACDN BLoaderin your pageVisitorsees it intheir language
How translations reach a visitorYour page is scanned and translated in the control plane, which can be offline. The result is published as a signed bundle of static files to three places: your own site and two independent CDNs. A small loader in your page reads the bundle from any of them and shows the visitor the translated page. Visitors never contact the control plane.Your pageany websiteScan, translate, review, publishcontrol planecan be offlineSigned bundlestatic filesYour siteCDN ACDN BLoaderin your pageVisitor sees itin their languageVisitors never contactthe control plane.
Translations are published as static files to three places. The control plane, drawn dashed, can be offline without affecting visitors.

  1. Scan

    We find the text on your pages: headings, paragraphs, buttons and attributes such as image descriptions.

  2. Translate and review

    Machine translation with your glossary, then edit anything you like. Your own edits are never overwritten by machine output.

  3. Publish

    We build a signed, versioned bundle and copy it to your own site and two independent CDNs.

  4. Visitors see it

    A tiny loader reads the bundle, swaps the text and remembers the visitor's language. No call to our servers.

Four steps to a translated site1. Create a site in the dashboard. 2. Add the WordPress plugin or one script tag to your website. 3. Translate and review the text we found. 4. Publish: signed static files go to your site and two CDNs.1 Create a sitein the dashboard2 Add it to your siteplugin or one script tag3 Translate and reviewedit anything you like4 Publishstatic files, three places
Four steps to a translated site1. Create a site in the dashboard. 2. Add the WordPress plugin or one script tag to your website. 3. Translate and review the text we found. 4. Publish: signed static files go to your site and two CDNs.1 Create a sitein the dashboard2 Add it to your siteplugin or one script tag3 Translate and reviewedit anything you like4 Publishstatic files, three places
From a new account to a published translated site.

If our servers go down

What a visitor sees when the vendor's servers are downTop: when translations are fetched from the vendor's servers on every visit and those servers are down, the visitor gets the untranslated page. Bottom: when translations are pre-built static files on your own site and two CDNs, the loader still finds them and the visitor gets the translated page; the vendor's servers are not needed.Translations fetched from the vendor at every visitVisitorYour page+ vendor scriptVendor serverofflineUntranslated or broken pagevisitors may leavePre-built bundles served from places you controlVisitorYour page+ loaderYour own siteCDN ACDN BTranslated pageas publishedVendor server offline: not needed
What a visitor sees when the vendor's servers are downTop: when translations are fetched from the vendor's servers on every visit and those servers are down, the visitor gets the untranslated page. Bottom: when translations are pre-built static files on your own site and two CDNs, the loader still finds them and the visitor gets the translated page; the vendor's servers are not needed.Fetched from the vendor at every visitVisitorYour page + vendor scriptVendor server offlineUntranslated or broken pagePre-built bundles from places you controlVisitorYour page + loaderYour siteCDN ACDN BTranslated pageas publishedVendor offline: not needed
What a visitor sees when a vendor's servers are down, with and without pre-built bundles.

You cannot edit or publish until we are back. Visitors notice nothing, because everything they need is already static files on your site and the CDNs. If one copy is unreachable the loader tries another, and if none works it shows your original text.

Status of the integrations. The script snippet is available now and the WordPress plugin is available in early access as a zip from your dashboard. The Shopify app is built and its store listing is coming. None is listed in the WordPress.org directory or the Shopify App Store yet.

See it with your own site

Create an account See all features