Private intelligence. On your terms.Documentation

StenoAI for Defence

Built for the discussions that can't leave your boundary.

Planning sessions, programme reviews and sensitive debriefs. Capture, transcribe and summarise on the device in the room, or on servers inside your own boundary. Local mode keeps working when the network is unavailable.

Your device or your infrastructureNo meeting botOpen source
Personnel gathered around a planning table

01 / Where it is used

Illustrative settings · 8

Where it is used,
room by room.

Settings where the conversation can’t be handed to a cloud vendor, and the record StenoAI produces in each, on your device or your infrastructure.

  1. DEF-01Your network

    Operational planning

    Planning conversations that never touch a vendor's cloud.

    ForStaff officers, planning groups, HQ cells

    • Decision log
    • Taskings
    • Brief-back summary
  2. DEF-02Your device

    Debriefs and after-action reviews

    A first AAR draft straight from the debrief.

    ForAircrew, unit commanders, exercise staff

    • AAR draft
    • Lessons
    • Actions
  3. DEF-03Your device · offline

    Forward and disconnected operations

    Works when there is no network at all.

    ForDeployed headquarters, forward teams

    • Offline transcript
    • Summary
    • Taskings
  4. DEF-04Your device

    Maritime and at sea

    No bandwidth needed once you sail.

    ForShips' companies, embarked staffs

    • Brief summaries
    • Handover notes
    • Actions
  5. DEF-05Your network

    Wargaming and red-teaming

    Every move, and the reasoning behind it.

    ForStaff colleges, wargame and red cells

    • Turn log
    • Rationale
    • Insights
  6. DEF-06Your network

    Coalition and multinational meetings

    Multilingual rooms, one record you hold.

    ForLiaison officers, multinational headquarters

    • Multilingual transcript
    • Summary
    • Actions
  7. DEF-07Your cloud tenancy

    Acquisition and programme reviews

    Programme reviews stay on hardware you control.

    ForProgramme offices, industry partners

    • Minutes
    • Risk register notes
    • Actions
  8. DEF-08Air-gapped

    Secure-enclave working

    Runs fully local, with no content egress.

    ForSecurity authorities, IT and accreditation teams

    • Build from source
    • Offline models
    • No content egress (local mode)

02 / Why now · Public record

Verified October 2026

Doctrine already assigns a recorder.

Planning doctrine expects someone to keep the record. Experimentation assumes the network will fail. And the costliest losses happen when a copy leaves the system it belongs in.

  1. Nov 2024 US Army FM 5-0

    “The use of recorders is particularly important.”

    Planning doctrine has recorders capture coordinating instructions, subunit tasks and the information needed to synchronise an operation. A disconnected laptop can be a second recorder; the human recorder keeps the pen.

  2. Mar 2026 US Army experimentation

    The network is expected to degrade

    Army experimentation replicated jamming, signal interference and limited bandwidth expected against a peer threat. Once models are installed, StenoAI's local pipeline needs no network at all.

  3. Jul 2025 UK Ministry of Defence

    A file emailed outside authorised systems

    The Defence Secretary told Parliament that a Defence official had emailed an ARAP caseworking file outside authorised government systems in February 2022.

03 / Structural risk

3 points

Why cloud tools don’t fit.

  • Cloud transcription is a non-starter when the audio can't leave the enclave.
  • SaaS meeting assistants require connectivity and a vendor relationship you can't extend to classified work.
  • A meeting bot is an external participant — unacceptable in an operational context.

Your device or your infrastructure

Run it on one laptop, on a model server inside your network, or in your own cloud tenancy. Local mode also works on air-gapped and disconnected systems.

Nothing leaves your boundary

Audio stays on the machine. Transcripts and summaries stay on it too in local mode, or go only to a model server you run inside the enclave. There is no vendor in the data flow.

On-device models

In local mode, transcription (Parakeet, Whisper) and summarisation run on your hardware, with no external inference service in the path.

Open and inspectable

MIT-licensed source your security authority can review and build in a controlled environment.

04 / Law & policy

Verified October 2026

Contract clauses and classification rules.

Where controlled data may go is decided by contract and policy, not by the tool. These are the clauses a security authority will check, and where the design helps.

DFARS 252.204-7012 · (b)(2)(ii)(D)

It says
A contractor using an external cloud service for covered defence information must ensure it meets security requirements equivalent to the FedRAMP Moderate baseline.
So
In local mode a design review adds no cloud provider to that scope.
Still yours
Your NIST SP 800-171 controls on the laptop, and any provider you configure.

Government Security Classifications

It says
Cabinet Office policy on how government classifies information assets so they are appropriately protected.
So
Local mode keeps meeting content on the device; a self-hosted model server keeps text inside your network.
Still yours
Approval of the device and audio capture for any classified space, by your accrediting authority.

UK GDPR · Art. 28

It says
A controller may use only processors that provide sufficient guarantees to implement appropriate technical and organisational measures.
So
For personnel and business meetings, local mode adds no processor to the data path.
Still yours
Your records of processing, and contracts for any model server or cloud tenancy you configure.

05 / Case files · Public record

Verified September 2026

What happens when the data leaves

The pattern is consistent: the compromise happens at a link in the chain that isn't yours. A contractor's system, a vendor's build server, a file that left the enclave and couldn't be recalled.

Case 01 UK Ministry of Defence, Afghan relocations · 2022, disclosed 2025

A spreadsheet that left the building

In February 2022 a member of staff at UK Special Forces headquarters emailed out a dataset holding the names and details of roughly 19,000 Afghans who had applied for relocation under ARAP. It was not discovered until August 2023, when part of it surfaced in a Facebook group. The government obtained an unprecedented superinjunction that kept the breach — and a secret resettlement scheme built in response — out of public view until July 2025.

What StenoAI changes

Nothing was hacked. A copy was made and sent, and it could not be recalled. StenoAI cannot stop a person emailing a file, and doesn't claim to — but it adds no copies of its own: no vendor-side duplicate, no automatic sync, no export step in the pipeline. Recordings, transcripts and summaries are ordinary local files, held under whatever controls you already run on that machine.

House of Commons Defence Committee report (opens in a new tab)

Case 02 UK MoD payroll provider · 2024

The contractor was the way in

Disclosed to Parliament in May 2024: an external payroll system operated by contractor Shared Services Connected Ltd was accessed by what the Defence Secretary called a malign actor, exposing names and bank details of up to around 270,000 serving personnel, reservists and veterans. The MoD's own networks were not the entry point — the third party's system was.

What StenoAI changes

Defence security is bounded by the least-defended system holding the data, and that system frequently belongs to someone else. Every SaaS notetaker adds one. StenoAI adds none: there is no vendor holding your meeting content, so there is no vendor to breach.

AP / SecurityWeek, May 2024 (opens in a new tab)

Case 03 SolarWinds Orion · 2020

A trusted update carried the attacker in

An actor the US government attributed to Russia's SVR compromised SolarWinds' build process and planted a backdoor in signed Orion updates shipped between March and June 2020. CISA issued Emergency Directive 21-01 ordering federal civilian agencies to disconnect the product; agencies including Treasury, Commerce and DHS were breached through it.

What StenoAI changes

StenoAI does not make supply-chain risk disappear — no software does, and any vendor claiming otherwise is selling you something. What it removes is the standing data flow a compromise could ride: StenoAI makes no network calls with your meeting content, so there is no established channel out. And it is MIT-licensed, so your security authority can review the source and build it themselves rather than trusting a binary.

CISA advisory AA20-352A (opens in a new tab)

Each incident is a matter of public record, summarised from the linked source and verified September 2026. StenoAI is not affiliated with any organisation named here.

06 / Deployment postures

Device → network → tenancy

Deployment postures
at the edge.

One application, three ways to run it. The product doesn’t change; the network around it does, and so does exactly what we can claim.

Posture 01 Single device

One laptop, no network.

The whole pipeline runs on one managed laptop.

  1. Install the app and download models while connected
  2. Disconnect: local mode needs no network after setup
  3. Switch usage analytics off in Settings
  4. Block the update check at your firewall or through device management

What holdsIn local mode, meeting content never leaves the device.

Posture 02 Isolated network

Your model server, inside your boundary.

Endpoints record and transcribe locally. Transcript text, never audio, goes to a model server you run on the same network, such as Ollama or an OpenAI-compatible endpoint, so larger models can run on your GPUs.

  1. Review the MIT-licensed source and build it in a controlled environment if required
  2. Run the model server on the isolated network
  3. Point summaries at it in the app's AI settings
  4. Restrict access: Ollama has no authentication by default

What holdsAudio stays on the device. Transcript text stays on your network.

Posture 03 Connected

Your cloud tenancy, your keys.

Where the classification allows, summaries run in your organisation's own cloud account, such as AWS Bedrock or your OpenAI or Anthropic agreement, or through your organisation's gateway so desktops never hold provider keys.

  1. Choose a provider approved for the information involved
  2. Configure it centrally through your organisation
  3. Keep transcription on the device (the default)

What holdsStenoAI runs no server that receives meeting content.

Use in any classified space needs your accrediting authority’s approval of the device and the audio capture. Accreditation is a function of your own deployment and authorisation process, not the app alone.

On compliance

In local mode, StenoAI runs entirely on your device. Your meeting recordings, transcripts, and summaries never reach our servers — there is no third-party processor handling your meeting data, which addresses a meaningful part of HIPAA, GDPR, and data-residency exposure. (Those frameworks also cover safeguards, agreements, and processes that remain your responsibility — no tool hands you compliance.) StenoAI itself isn't a certified cloud service, because there is no cloud service handling your meetings to certify — and that's the point: the vendor-breach risk that frameworks such as SOC 2 exist to assure against isn't in that path.

07 / Questions

Questions your
security team will ask.

01Can it run on our own infrastructure, or air-gapped?

Both. Summaries can run on a model server inside your network or in your own cloud tenancy, with transcription on the device by default. In local mode, after the one-time model download, everything runs with no network connection at all.

02Is any data ever sent to StenoAI's servers?

No. StenoAI runs no server that receives meeting content. In local mode recordings, transcripts and summaries stay as files on your device; if you configure a model server, content goes only to the endpoint you run or choose.

03Can we review and control the build?

Yes. It's open source, so it can be audited and built from source in your own environment before deployment.

Your next conversation deserves better.

Keep the record.
Keep control.

See what private meeting intelligence
can do for your organisation.

Request a briefing Download the open-source app
Your device or your infrastructure. Never ours.macOS · Windows alpha