API and on-premises. Integrate the engine where the work already happens
Your legal experts should not have to change tools to translate. You call the engine trained on Swiss law from your document management system, your intranet or your own product. When your internal rules require it, it runs in your own infrastructure.
Scope an integrationThree ways to integrate Neur.on into your IT systems
Document management
Translate from the DMS
A document stored in your document management system goes to translation from its own screen. The target version comes back next to the original, in the same folder structure and under the same rights. Your legal experts do not leave the tool in which they already file their matters, and no copy goes to an ungoverned online service.
Intranet
A translation service for everyone
Translation becomes a building block of your portal: an internal form, an upload page, a button in an approval workflow. Teams that would never open a translation platform get access where they work, with the languages and engines you have decided on.
LegalTechs and publishers
The engine in your product
You develop legal software and your Swiss clients ask for their content to be translated. Rather than train an engine, you call ours from your product: the feature is yours, the infrastructure and Swiss terminology are ours. The scope and the brand displayed are set out in the contract.
One call, the same settings as in the interface
What you choose on screen in Corrext, you also choose in a call: source language, target language, engine and area of law. This is how an integration follows the same governance as the interface, instead of creating a parallel channel without rules.
- Source and target language, from the languages on the platform
- Choice of engine, and therefore of where processing takes place
- Area of law, for the expected terminology
- Text or file, depending on what your system sends
L'établissement assujetti veille au respect du secret bancaire au sens de l'art. 47 LB et met en œuvre les exigences de la FINMA en matière de lutte contre le blanchiment d'argent.
Das beaufsichtigte Institut sorgt für die Einhaltung des Bankgeheimnisses nach Artikel 47 BankG und setzt die Anforderungen der FINMA zur Bekämpfung der Geldwäscherei um.
AlternativesDeepL Pro
Das unterstellte Institut sorgt für die Einhaltung des Bankgeheimnisses im Sinne von Art. 47 BankG und setzt die Anforderungen der FINMA zur Bekämpfung der Geldwäscherei um.
POST /v1/translate
200 OK
Illustration, not documentation.
Illustration, not documentation. The actual paths, field names and authentication are defined in the interface contract provided during scoping.
What is available, and in what form
Everything below is available today. The tools can be used in the web application as soon as you open an account. The API, on-premises deployment and rights synchronisation are set up with your IT department. Each row states in what form.
| Capability | What it is | In what form |
|---|---|---|
| REST API | Calls to the engine from your own systems, with the same settings as in the interface. | Available todayInterface contract, authentication and scope set during scoping; technical documentation provided on request. |
| On-premises deployment | Installation in your infrastructure, for environments where nothing may leave your network. | Available todayProvided as part of an integration project, after an architecture and sizing study. |
| Synchronised access rights | Your SharePoint and Active Directory rights are imported, so that everyone finds the scope they already have in your systems. | Available todayProvided as part of an integration project; not a self-service setting in the web interface. |
| Delivery by translators | Legal translators and agencies work in their own tools, Trados or memoQ, and deliver into the project workflow. | Available todayProduction workflow for projects with external review, with no action needed on your side. |
| Collaboration in Word | A translated document is reviewed in your teams' word processor rather than in yet another interface. | Available todayWith the Corrext add-in for Word, presented on the Word plug-in page. |
| The four tools of the platform | Text and document translation, Translation projects, Fast lookup CHnell and the translation of commercial register extracts. | Available todayAvailable today in the web application, as soon as you open an account. |
| Choice of engine | LexMachina, DeepL Pro, Azure OpenAI GPT and Claude, selected for each upload and governed by your organisation's policy. | Available todayAvailable today in the web application. |
Storage on Swiss servers in all circumstances; processing in Switzerland only with LexMachina or in Highly sensitive content mode. With an on-premises deployment, processing stays within your own infrastructure.
API documentation on request
The API technical documentation is provided on request, together with the interface contract.
What we need to know before scoping an integration
An integration is sized on facts, not on intentions. Five answers are enough to tell whether the project needs an API call set up in a few days, a connector to be written, or a deployment in your infrastructure. You can prepare them before the first discussion: we start from there and tell you what is realistic.
- 1
Volumes
How many pages or documents per month, with what peaks, and for how many users?
- 2
Formats
What do your systems actually produce: office files, scanned PDFs, plain text?
- 3
Languages
Which pairs, in what proportions, and what share of languages outside the four native ones?
- 4
Confidentiality level
Do your internal rules require Highly sensitive content mode, a Swiss engine, or a deployment within your network?
- 5
Existing systems
Which DMS, which directory, which portal, and who runs them, in-house or at your provider?
Other pages on the platform
Frequently asked questions about the API and on-premises deployment
Do you offer an API to integrate translation into our tools?
Yes. A REST API lets you call the engine from your own systems: document management, intranet, business workflows. We do not publish open technical documentation. The interface contract, authentication and scope of calls are set during scoping, with your IT department and our technical team.
Can we deploy the solution in our own infrastructure?
On-premises deployment is possible for the most sensitive environments, that is, when your internal rules require that nothing leaves your network. It is a full integration project, scoped with your IT department: architecture, sizing, updates and operation are defined before any commitment.
Can our access rights be imported from SharePoint or Active Directory?
This is possible as part of an integration project. Access rights can be synchronised with your directory and your document spaces, so that everyone finds in Corrext the same scope they already have in your systems. This synchronisation is not a self-service setting in the web interface: it is set up with your IT department.
Can we integrate the engine into our own product, on a white-label basis?
This is the use case for LegalTech companies and legal publishers: translation becomes a feature of your product, called via API, without your users changing tools. The functional scope, the brand displayed and the terms are set out in the contract during scoping.
Where is data processed during an API call?
The same rules apply as in the interface: storage takes place on Swiss servers in all cases. Processing takes place exclusively in Switzerland with LexMachina or in Highly sensitive content mode, which is available for German, French, Italian and English. The third-party engines, DeepL Pro, Azure OpenAI GPT and Claude, are hosted abroad and trigger the Attorney-Client privilege notice, which reminds users of your organisation's policy. With an on-premises deployment, processing stays within your own infrastructure.