OpenTranscribe — System Architecture

OpenTranscribe — System Architecture An architecture diagram generated by Archify. User · Browser · Architecture component User Browser MinIO · media/object storage · Architecture component MinIO media/object storage SvelteKit SPA · frontend/src · Architecture component SvelteKit SPA frontend/src Nginx · reverse proxy · Architecture component Nginx reverse proxy OpenSearch · hybrid/neural search · Architecture component OpenSearch hybrid/neural search FastAPI Backend · backend/app/api · Architecture component FastAPI Backend backend/app/api Redis · broker + cache · Architecture component Redis broker + cache PostgreSQL · primary DB · Architecture component PostgreSQL primary DB Celery Workers · 8 queues — see next tab · Architecture component Celery Workers 8 queues — see next tab LLM Provider · local or remote · Architecture component LLM Provider local or remote HTTPS presigned GET/PUT fetch (cookie auth) proxy_pass search query SQL enqueue task dispatch write results index transcript chat / summarize read/write media Legend Frontend Backend Database Cloud Message bus External

Web tier

  • • SvelteKit SPA, httpOnly-cookie auth, no JS-readable token
  • • Nginx terminates TLS, proxies /api and /ws
  • • Frontend media reads/writes go via presigned MinIO URLs — the backend only generates the presign URL string, Celery workers do the actual streaming

Backend + async pipeline

  • • FastAPI routers under backend/app/api
  • • 8 real Celery queues (gpu, cpu, nlp, embedding, redaction, utility, download, cloud-asr) — full breakdown on the Celery Queues tab
  • • ASR is local (WhisperX) or one of 8 cloud providers — see the Cloud ASR tab

Data + retrieval

  • • Postgres is system of record
  • • OpenSearch does hybrid/neural transcript search
  • • MinIO holds original media + derived artifacts