Skip to content
Scriptorium
Transcribe free

Self-hosted transcription

Self-hosted transcription for private meetings

TryScriptorium can run on your own computer or server, where recordings are processed by the transcription engine beside the files. This is the deployment to choose when a meeting should not be uploaded to a service operated by somebody else.

What stays in your environment

In a self-hosted installation, uploaded recordings, transcripts, the search index, speaker analysis and exports stay on the infrastructure you administer. The speech model runs locally after it has been installed. No third-party transcription API is required.

The public workspace at tryscriptorium.com is a hosted service, not a self-hosted installation. It is useful for trying the product with a non-sensitive file; its data handling is described on the hosted privacy page.

Built for recorded meetings

Upload a meeting recording, or capture audio from a browser tab or screen in a local installation. TryScriptorium produces timestamped text, can separate speaker turns, lets you correct the transcript inline, and keeps a full-text library you can search later. Export plain text, subtitles, Markdown, JSON or CSV when the meeting needs to move into another workflow.

Who self-hosting is for

  • Teams with legal, medical, research or contractual confidentiality duties.
  • Organisations that need recordings and transcripts to remain on their own network.
  • Technical teams that want control of retention, access and identity-provider sign-in.
  • Individuals who want a local speech-to-text workspace without a meeting bot.

How deployment works

Run the application on the machine or server that will hold the data. A local install runs on loopback by default. A team deployment runs in server mode behind HTTPS, which disables host-file features for remote users and accepts uploads instead. Optional OpenID Connect sign-in can be configured for an organisation.

Read the deployment documentation before exposing an instance to a network. It covers persistent storage, HTTPS, server mode, retention and the security checks that belong in a production installation.

Hosted or self-hosted?

Use the hosted workspace when a quick transcription is appropriate and you accept the hosted data model. Self-host when the recording must remain under your organisation's control. That distinction matters more than a marketing promise, so it is made plainly throughout this site.

Learn about private meeting transcription or read the deployment guide.

Running it on your own hardware?

Tell us what you need to deploy and we will point you to the right setup. If you only want to see the product first, try the hosted workspace with a non-sensitive file.

Ask about self-hostingTry the hosted workspace

Frequently asked questions

Where is my recording processed?
It depends on the deployment. On the hosted site at tryscriptorium.com, a file is sent over HTTPS to the Scriptorium server and processed there. On your own installation, processing and storage stay on the machine or server you run it on.
Does Scriptorium send recordings to a third-party transcription API?
No. Transcription runs in the application itself using the Whisper family of speech models. A separate, optional AI-recipes feature can send a transcript to a cloud model, but it is off unless an administrator turns it on, and it only runs when a person asks it to.
Does self-hosted Scriptorium work offline?
Transcription does, once the speech model you chose has been downloaded. That download, from Hugging Face, happens once per model size; after that the model is loaded from disk only. The optional speaker-separation model is a one-time download as well.
Does a bot join my meeting?
No. Scriptorium works on a recording you already have, or one you capture from a browser tab on a local installation. It never joins a call.
Is the hosted site suitable for confidential recordings?
Use it for non-sensitive files. If a recording is covered by privilege, medical confidentiality or a contract that forbids third-party processing, self-host instead.
How do I get a self-hosted installation?
Get in touch through the contact page and say what you need to run it for; deployment guidance is provided for local, server-mode and systemd setups.

Keep reading