Skip to content

GOVERNMENT · DEFENCE · MISSION-CRITICAL

An interpreter your accreditation team can audit.

Live interpretation into up to four languages at once, on one PC inside your facility. No cloud. No internet. No linguist in the room. Nothing about the meeting leaves the building — and your own engineers can prove it.

Book a demonstration Download the security brief How it runs air-gapped →

Sensitive meetings already cross languages. Until now, every answer had a leak.

OPTION A

Human interpreters in the room

Cleared linguists are scarce, expensive and booked weeks ahead. Every extra language is another person who hears everything.

OPTION B

Commercial translation services

Fast and cheap — and not deployable here. The meeting's audio goes to a third party, outside the facility and often outside the jurisdiction.

OVVOS WASEL

Interpretation with the posture of your own infrastructure

No linguist in the room. No packet off the site. One box you own, inspect and switch off.

WHAT LEAVES THE FACILITY
0

bytes of meeting audio, text or metadata.

We measured it. Then we measured it again, a different way.

Starting up, idling and running a full meeting with live speech in four languages, the application's processes made no connection to any address outside the PC, and looked up no outside name. Two independent witnesses: the operating system's connection table, and audit hooks inside every process the application starts.

VERIFY IT YOURSELF

Run a span port or host firewall log for the length of an acceptance meeting. Expected result: no outbound flow from the Ovvos Wasel processes.

Default on-premise profile. The application window is drawn by Microsoft Edge WebView2; Ovvos Wasel starts it with background services switched off, and in our measurement it made no outbound connection. Windows Update and other software on the PC stay under your own IT policy.

DATA HANDLING

Every artefact the system touches, where it lives, and how long it survives.

ARTEFACT WHERE IT LIVES LIFETIME DEFAULT
Meeting audioMemory on the room PCSecondsNever written to disk — no setting exists that would
Recognised textMemory on the room PCOne sentenceDiscarded once spoken
Interpreted audioRoom network → the chosen phonePlayed onceNot recorded anywhere
Captions on a phoneThat phone's browser, while openUntil close or meeting endNot stored on the device
TranscriptRoom PC memory, only if enabledOperator-setOFF
Operational logsRoom PC diskRotatingThe length of each sentence — never its words

Transcript retention, transcript export and meeting text in logs are three separate switches. Each is off by default and visible to the operator on the Privacy page.

Three doors into the system. Each has its own lock.

1

The listener page

Reachable only from the room network. A per-meeting PIN gates it — until it is accepted, the page offers nothing to choose. Each phone receives only the language its holder picked.

2

The operator console

Runs on the room PC inside the operator's Windows session. Access from other machines requires the administrator password — generated at installation, never kept in the shareable configuration.

3

The room display

Output only: the join address, the PIN and the languages running. The live transcript is off until an operator turns it on, and clears when the meeting ends.

Ending a meeting stops interpretation on every handset immediately. Anything not yet spoken is discarded, every phone drops the audio it was holding and says the meeting has ended. Outside a meeting, nothing is interpreted at all.

Your delegation follows every word. In their own language.

Bilateral and multilateral talks

A foreign delegation speaks over the video link; your officials hear it in Arabic.

Joint exercises and coordination

Partner nations brief in English; liaison officers follow in their own languages.

Ministerial and board meetings

One room, four languages, nobody waiting for a booth.

Classified briefings with an international participant

No third party hears the meeting — human or machine.

Phone showing a live Arabic caption Phone in dark mode showing a live German caption

What your accreditation team receives before deployment.

  1. 01Network behaviour statement. Every port the product opens, every address it contacts. The second list is empty.
  2. 02Offline installation media. Software, language models and voices in one package. No download step, ever.
  3. 03On-site inspection. Your team observes installation and runs its own packet capture during acceptance.
  4. 04Patching on your terms. Windows updates come from Microsoft, through your own IT, under your existing policy.

We cannot reach your machine. We don't want to.

STEP 1

You open the door

With your own approved tool, at a time you choose.

STEP 2

Attended throughout

Your staff watch every action as it happens.

STEP 3

The door closes

End the session and the route is gone.

No inbound port. No vendor account. No log upload. No meeting content. Fully air-gapped rooms are supported by telephone with your operator at the keyboard, or by on-site visits under escort.

ACCURACY, STATED HONESTLY

Built for comprehension in the room.

On-premise means models sized for one machine in your building, not the largest in the world. Ovvos Wasel is for following a meeting in your own language. It is not a certified translation, a record of proceedings, or a substitute for a cleared interpreter where a binding rendering is required.

Glossary

Ranks, unit names and designations are fixed and never drift.

Expected languages

Naming who is in the room removes whole classes of misrecognition.

Good audio in

A line feed from the mixer beats any model upgrade.

Four loss counters

The operator sees exactly which stage lost a sentence, and what fixes it.

Questions accreditation teams ask.

Can it run in an air-gapped room?

Yes. It installs from offline media and needs no internet to install, start or run a meeting. Recognition, translation and speech all run on the room PC.

How do we verify nothing leaves the facility?

Run a span port or host firewall log for an acceptance meeting. Expected result: no outbound flow from the Ovvos Wasel processes. Our own method and results are in the Network Behaviour Statement.

Does the vendor need remote access?

No. There is no standing agent, vendor account or inbound port. Support happens through an attended session you open, by telephone, or on site under escort.

Does it connect to Teams or our conferencing tenant?

No. It listens to the room PC's sound output at the Windows audio layer. No app, bot, API key, OAuth consent or tenant approval is involved.

See it live, before anything is installed.

Bring your delegation to our office; your colleagues join from yours, over your usual platform, in their own language. Run your own agenda with your own terminology. Then: accreditation review, installation under your escort, acceptance testing.

Book a demonstration