5.2.41. Parakeet (STT engine)¶
Parakeet is one of the STT engines selectable via STT_PROVIDER_SOURCE. It is
documented under the STT Provider aggregator rather than as a standalone
service, because the user-facing role is "pick an STT engine" — not "pick
Parakeet":
→ See services/stt-provider/README.md for the full user-facing description, source-variant table, and configuration reference.
1. Engine quick reference¶
- Image:
nvcr.io/nvidia/pytorch:26.06-py3(GPU only — Parakeet-TDT model) - License: CC-BY-4.0 (NVIDIA)
- Activation:
STT_PROVIDER_SOURCE=parakeet-container-gpu(orparakeet-localhost— Parakeet-MLX on macOS / native Linux) - In-container port: 8000
- Host port:
${STT_PROVIDER_PORT}(computed fromBASE_PORTby the bootstrapper) - Readiness: Uvicorn starts while a deadline-bounded background task loads
the configured model.
GET /healthreturns503until loading completes.
This manifest also owns the broader STT_PROVIDER_SOURCE enum (every STT
option across engines), which is why it lives here historically rather than
on the aggregator. The manifest (service.yml) and compose fragment
(compose.yml) in this folder are the bootstrapper's source of truth for those
values; treat this README as a pointer, not a duplicate of the aggregator doc.
2. Dependencies & Integrations¶
2.1. Current — Upstream (this service calls)¶
No upstream calls.
2.2. Current — Downstream (services that call this)¶
| Service | Category |
|---|---|
| kong | infra |
| hermes | agents |
| n8n | agents |
| jupyterhub | apps |
| open-webui | apps |
2.3. Architecture diagram¶
Open the full-size diagram for a full-screen view.
2.4. Future — Missing pair integrations¶
No high-confidence opportunities identified.
2.5. Future — Candidate new services¶
No high-confidence opportunities identified.
2.6. Future — Unused features in this service¶
No high-confidence opportunities identified.