Skip to content

v0.2.0 — Web console + WebSocket TTS + Observability

Latest

Choose a tag to compare

@ARahim3 ARahim3 released this 17 May 15:10

supertonic-server now ships with a polished single-page web UI at http://localhost:8000/. Test voices, tune parameters, hit play — and copy the exact curl / OpenAI / Pipecat / LiveKit snippet that would produce the same audio from your code. Plus a new WebSocket TTS endpoint for voice agents and an in-process Observatory with Prometheus-compatible metrics.

Install / upgrade

pip install -U supertonic-server
# or
uv pip install -U supertonic-server

Try it (30 seconds)

supertonic-server --port 8000
# then open http://localhost:8000/ in your browser

The HTTP API (/v1/audio/speech, /v1/voices, /v1/models, /healthz) is unchanged from v0.1.0. The console is just another client of the same server. Disable it entirely with --no-ui if you don't want the / route.

Docker — what changed in v0.2.0

  • The default Dockerfile is still the cross-platform CPU image, but the silent CMD ["--device", "cpu"] that overrode -e SUPERTONIC_DEVICE=... has been removed. Setting the env var now actually does what it says.
  • New Dockerfile.cuda for NVIDIA hosts: nvidia/cuda:12.4.1-cudnn-runtime-ubuntu22.04 base, Python 3.12, onnxruntime-gpu swapped in, SUPERTONIC_DEVICE=cuda baked into the env, plus a build-time sanity check so a misbuilt image fails fast instead of silently running on CPU.
  • resolve_providers() now logs a loud WARNING device=cuda requested but CUDAExecutionProvider is not available … if you ask for a hardware accelerator that isn't installed. The previous silent CPU fallback was a footgun for anyone running the default Dockerfile with --gpus all.

Compatibility

Supported
Python 3.11, 3.12, 3.13
OS macOS (incl. Apple Silicon), Linux, Windows
Hardware CPU; CoreML (Apple Silicon); CUDA (via onnxruntime-gpu)
Browsers (for the console) any modern Chromium / Firefox / Safari

Notes

  • The console is read-only with respect to server lifecycle — it doesn't start/stop the server or change its port. That's still done via the CLI (supertonic-server --port 9000). If you'd find a "manager"-style desktop wrapper useful, open an issue and tell me how you'd use it.
  • The UI is built ahead of time and committed under src/supertonic_server/ui/dist/. Devs who want to rebuild it: cd src/supertonic_server/ui && npm install && npm run build.

Links