Voxtrama

In short
Voxtrama is an open source application that runs in Docker on your own computer, and the audio never leaves it. It transcribes recordings with Whisper, separates the speakers and, with a model served by Ollama, writes a summary, decisions, themes or concepts. Every point carries the sentence from the recording and the minute it was said; when the sentence is missing from the transcript, the point is flagged Needs review.

Voxtrama turns the recordings you already have, meetings, lessons and interviews, into a transcript with the speakers told apart and a summary you can check. It runs in Docker on your own computer, and the audio stays there. I wrote it from scratch in Python and published it on GitHub on 28 September 2026 under the Apache 2.0 licence. How each point of the summary is tied to the sentence and the minute it was said is in the article on verifiable minutes.

Voxtrama on GitHub sjpagan/voxtrama (opens in a new tab)

Who builds Voxtrama, and since when

Client
Personal project
Sector
Data confidentiality GDPR public administration
Role
@sjpagan (Owner)
Year
2026

What Voxtrama is built with

Python FastAPI Docker Ollama Redis SQLite

What problem Voxtrama solves

Anyone who records a meeting to write up the minutes usually uploads the audio to an outside service, and rarely knows which server it lands on or how long it stays there. The summary that comes back is written by a language model, which can put words in someone's mouth.

How Voxtrama solves the problem

Voxtrama brings transcription, speaker separation and summary onto the machine of whoever made the recording. Every point of the summary has to quote the transcript: Voxtrama looks the quote up word for word, links the point to its minute in the audio, and flags as Needs review whatever it finds worded differently.

What Voxtrama achieved

Apache 2.0 licence, code and releases on GitHub. It is an alpha: I use it on my own work calls and I am looking for the first people to try it.

What happens to the audio

The audio never leaves your computer. A recording uploaded to Voxtrama follows this path, from upload to deletion.

Moment Where the audio is What goes over the network
Upload copied into the data folder on the host, ~/Voxtrama/recordings nothing
Clean-up, transcription, speaker separation read by the machine's processor nothing
Summary stays on disk: the model receives only the transcript text the text, to the Ollama server you configured; if Ollama runs on the same machine, as it does by default, nothing
Storage stays in the data folder until you delete it nothing
Deletion Delete › Audio on the job, Clean up, retention, or rm -rf ~/Voxtrama nothing

Retention is off by default, so a recording stays on disk until you delete it or set a limit of 7, 30, 90 or 365 days. Clean up removes on its own the recordings no job uses, once they are at least a week old.


Who it is for

Voxtrama is for people who record conversations they need to act on or study from, and who want to keep the audio in house.

  • A team that keeps minutes of its meetings, with decisions, owners and deadlines.
  • A professional firm or a public office, for which the GDPR turns this choice into an obligation.
  • Researchers who work with interviews and draw themes from them.
  • A student going back over a lesson for its key concepts.

For a company that wants Voxtrama on its own servers, or a workflow shaped like its own minutes, I install it and tailor it.


Requirements and installation

You need Docker: Docker Desktop on macOS, or Docker Engine with the Compose plugin on Linux. Memory decides the transcription model: up to 8 GB the smallest, between 8 and 32 GB the medium one, 32 GB or more the most accurate. The summary needs Ollama with at least one model pulled. Transcription alone works without it.

git clone https://github.com/sjpagan/voxtrama.git
cd voxtrama
cp .env.example .env
make up

make up starts four containers and prints the address, for example http://127.0.0.1:8000. On first start Voxtrama proposes the profile that suits the machine and downloads the transcription model, 484 MB on the smallest profile. The full steps are in the project wiki (opens in a new tab), on the Requirements (opens in a new tab), Install-on-macOS (opens in a new tab) and Install-on-Linux (opens in a new tab) pages.


Workflows: what the summary is for

A workflow tells Voxtrama what to pull out of a recording. Voxtrama ships three, plus plain transcription:

Workflow What it produces
meeting-decisions summary and decisions, each with an owner, a deadline and a quote
lesson-companion summary and key concepts with their definitions
research-interview summary and themes, each with a quote
transcribe-only the transcript with its speakers, nothing else

A workflow is a YAML file, and it behaves like a skill: the same call becomes a list of decisions or a map of themes depending on the workflow and the model that runs it. Adding one means writing the file, with no code to touch. You can define your own next to the three it ships with, for instance minutes laid out the way your office requires.


What goes over the network, and when

No part of the code sends the audio file off the machine. Only two things go over the network, at two specific moments.

Connection When What travels
huggingface.co only when Voxtrama downloads a model it does not have yet: at first start, or on the first job that needs it the request for the model files; no audio and no text
the Ollama server for the summary on every summary the transcript text, to the server you configured: by default it is on the same machine

To keep everything in, run Ollama on the same machine. If you configure a remote server, that server receives the transcript text, never the audio; the Settings › Data & privacy page shows, step by step, where each workflow runs, and a step marked local_only refuses remote servers.

I checked this on 30 September 2026 in the logs of three jobs run on giorgioserver. The first one downloaded both models and contacted huggingface.co three times, all for the download. The other two jobs, with the models already on disk, contacted no outside server; the summary went to the Ollama instance on the same machine.

The code also records a fault that has since been fixed: the speaker model, although already on disk, queried huggingface.co four times on every job to check its own files. No audio left, but the fact that this machine was running that model did. The model now loads in offline mode, and a test makes sure it stays that way.

The rest of the protection lives in the code:

  • the application answers only on 127.0.0.1 and refuses requests carrying another host name or origin, which also covers DNS rebinding;
  • a credential for the model server travels only over https or to the same machine;
  • the versions of downloaded models are pinned, because SpeechBrain builds objects from the model's configuration file;
  • retention deletes finished jobs after 7, 30, 90 or 365 days.

Speaker separation works on one recording at a time: in the next call, the same person is once again an unnamed voice. That is deliberate. A voice print is biometric data, and keeping one would turn a transcription tool into an identification system. For the same reason Voxtrama works only on files you already have, and leaves video platforms' content to them.


What each part does

Part Technology
Web application and API Python 3.11, FastAPI, Jinja2
Job queue RQ on Redis
Database SQLite with Alembic migrations
Transcription faster-whisper (CTranslate2), int8 on the processor
Speaker separation SpeechBrain ECAPA-TDNN, clustering with scikit-learn
Summary Ollama, local or remote
Command line Typer: doctor, demo, run, compare, retention
Distribution Docker Compose, four containers

The containers are the Redis queue, a database migration that runs once, the web server and the worker that runs the jobs. Everything Voxtrama keeps lives in one folder on the host, ~/Voxtrama by default: recordings, results, models, database and settings.


Project status

Voxtrama is an alpha. I have tested it with Docker on a 2017 iMac Pro with an Intel processor and, on 30 September 2026, on a Linux server with a Ryzen 9 9950X, where 30 minutes of audio took 10 minutes and 40 seconds from transcription with large-v3 to the extracted decisions. The next step is running it on other operating systems. Until 1.0 an update may change the format of workflows and stored jobs, and the release notes say so when it does. The automated measurements that would stop a release from lowering quality are not in place yet. The interface is in English and the code is ready for translations: I am waiting for the first reports from real use before choosing languages.

Branches and tags follow the drupal.org project model, the same one I use for my Drupal modules: one branch per series, 0.1.x, and tags from alpha to rc up to the release.

If you try it, the repository's issues are where your feedback helps most.


Sources

All sources were checked on 30 September 2026.

AI modified

This text was translated by AI.

How was AI used?

Translated from the Italian original with AI assistance, then read and corrected by a person, who holds editorial responsibility.

Articles on Voxtrama