The self-hosted Jitsi conference is deployed and verified — co-hosted on the Hostinger VPS beside n8n-prod. This is the live target the in-meeting transcription UI and the jigasi bridge build against.
| Check | Result | Detail |
|---|---|---|
| Edge https://jitsi.boas.dev | ✓ 200 | HTTP/2, traefik-terminated TLS (mytlschallenge), routed to web |
| Conference stack | ✓ up | web · prosody · jicofo · jvb (4 containers) |
| n8n-prod co-host | ✓ safe | Up throughout deploy · ~5 GB RAM still free · load nominal |
| Resource caps | ✓ honored | web 14/192M · jicofo 123/512M · jvb 157/900M · prosody 25/320M (~320 MB actual) |
| Media path | ✓ open | UDP 10000 direct (grey DNS) + TCP 4443 fallback |
| Auth gate (rule #19) | ✓ closed | secure-domain — room creation requires host; guests join only |
| SSOT | ✓ persisted | fleet_services.jitsi-boas-dev registered, verified |
Solid = live today. Dashed (G1) = jigasi attaches over prosody's XMPP transcriber config — the exact access 8x8 JaaS structurally won't expose, which is the whole reason to self-host. ASR is a hosted vendor call, decoupled.
An in-meeting transcript layer we design requires owning the meeting client. Zoom/Meet/JaaS won't let us paint a caption surface. Self-hosted jitsi-meet is the one client we own — render surface + transcription-injection in one.
GPUs too expensive for 1–3 low-frequency meetings. A hosted vendor is acceptable — the veto was Google STT specifically, not all rented compute. skynet/metis-051 GPU procurement dropped. Cents/meeting vs $2–3.5k capex.
Spend retracted. Only ASR needs a GPU and jigasi→ASR is a network hop, so the conference is CPU-only. Hard container caps keep a JVB spike from starving n8n-prod; split later only if prod actually degrades.
Proteus owns version-controlled config; only secret material (passwords, host account) crosses to the operator/hades leg — never an LLM transcript. Room creation is auth-gated (rule #19); no open public meeting server.
A refreshed sweep confirmed no hosted transcription service supports Jitsi natively (they target Zoom/Meet/Teams). jigasi remains the bridge between the self-hosted conference and the ASR — adopted OSS, not a rebuild.
For a same-day proof, transcription decouples from the platform entirely: whisper.cpp on the M4 (already installed) transcribes the meeting audio — no jitsi, no GPU, no vendor. Diarization is the only trade, recoverable later.