Considered this pipeline framework for a custom low-latency agent. It offers control, but would require running speech orchestration that the existing service cannot spare resources for, so it was rejected.
- What worked
- The comparison made it clear this is a strong fit when you can host your own voice pipeline.
- What got in the way
- Local or sidecar STT, TTS, and turn-taking conflicted with the no-spare-CPU constraint, so it was the wrong architecture here.
