If the content owner is highly privacy-conscious, or they’re handling sensitive data, like financial or HIPAA-data, the requirement that it must not leave their systems, aside from a small handful of audited, trusted third parties, is entirely valid. So how can you offer the power and convenience of the proxy to such clients?
By moving the proxy inside their security boundary, that’s how. Codenamed INSIGNIA, this deployment mode allows the content owner to deploy a copy of Easyling with all its scaling and related powers, into their own resource pool of sufficient size, making it easy to maintain the translated website.
Your client might be operating in an industry that is subject to heavy government regulation, or your content might be such that it contains sensitive protected information (such as HIPAA data), meaning you cannot use our proxy service despite all the upsides you can see. It seems like you’re destined to be stuck using the same outdated methods to handle your content forever, unable to upgrade to something your localization department would find more comfortable.
Enter our latest offering: INSIGNIA. This new development is a way to deploy what is effectively a private installation of Easyling into your own datacenter or resource pool, opening up all the advantages of the proxy, without any of the security or privacy concerns that usually come with it.
Easyling makes it easy to keep up with new content in its INSIGNIA deployment mode by automatically grabbing anything that’s not translated on your website and forwarding it to a translation service hosted within your own datacenter or private cloud.
One assumption we’ve made throughout development is that you’ll have something at your disposal to handle said content, something that’s assumed to be a trusted third-party system, like a dedicated MT engine. Vendors like Google Translate or Systran work wonders, in our experience, especially when coupled with domain-specific training corpuses.
The first use case springing to mind here is that of an insurance company, who is mandated by local law to remain off of any big name cloud providers, for data security reasons. Thus, they have implemented their own private cloud, hosting it in a datacenter of their own building, but now they want translations to take place - except nobody can help them in their locked-down environment. And this is where INSIGNIA enters the picture: by launching an instance of INSIGNIA in their datacenter, the client gains the ability to take advantage of the proxy’s instantaneous translation capability, while secure in the knowledge that they can maintain compliance as their clients' information is secure in their own infrastructure, never being sent to any untrusted third parties.
There are times when nearly everything is stacked against you: the content owner requires that no data pass through a third-party proxy, but cannot modify the site at all, nor can they support INSIGNIA’s resource requirements. In this seemingly-hopeless situation, we have one more ace up our sleeve, the ability to translate the site via a Chrome plugin that can be brought into the company profile using channels already known and used to maintain compliance in client browsers.
Sometimes, the highest barrier for entry is not the translation itself, but how to publish the translations. The client might be facing internal restrictions that prevent them from using the proxy, or they might be prevented from including our client-side translator. So while Easyling makes the actual translation easy, it seems like delivering the translations is near-impossible.
Enter our Chrome extension: by installing the extension in the browser, injecting the translations into the page becomes possible, without having to make any changes. And because Chrome is natively ready for centralized management, controlled by the IT department, managing the extension from a centralized point is also a breeze.
Easyling normally makes it very easy to keep up with any new content being published. Every time the translated pages are viewed, the proxy notes any new content that has no translations, and can either alert you, or prepare said content for translation right away. It is no different with the Translator Extension either.
Any time your web team publishes new content, as soon as someone loads the language pages with our extension, it can report back newly published content to Easyling, from where the internal localization team can take over, and transcreate the content for your in-country teams.
This is a scalable solution with a focus first and foremost on large-scale enterprise users. Typically, these users have understandably strict, comprehensive and in some cases limiting IT policies in place that require major rethinking of the environment with a view of limiting outside risk. Furthermore, depending upon the size and increasingly wide geographical nature of many firms, which have dispersed over various time zones, enterprise partners can encounter conflicting stakeholders within the organization with diverging priorities.
Regardless of the size of any firm, time and money are always an issue within any organization it offers an ease of implementation and deployment as it does not require change to the original existing site. While allowing enterprise clients to put the power of CREST into their people’s browser, in the form of a Chrome extension that can be subject to centralized and accepted control points. In this way an enterprise client can be assured that accepted protocols and methodologies are enforced from the word ”GO”.