Changelog¶

Dated, newest first. Product changes to the API and portal; engine and server internals live in the repositories' DECISIONS.md.

2026-10-16 — Developer portal and docs¶

Portal at tts.vartalaap.si: e-mail magic-link sign-in, organisations and projects, API keys with per-key voice allow-lists (shown once, hashed at rest), a playground that streams over REST or WebSocket with a live time-to-first-audio timer and the normaliser's output, usage (per-day audio, requests, p50/p95 TTFA, RTF; by key, voice and endpoint; CSV), billing at 20 paise per audio-minute, a voice gallery and a "train your voice" request form.
API: POST /v1/normalize previews the Hinglish normaliser and the chunking without synthesising. WS /v1/tts/stream accepts the key as ?api_key= for browsers. Keys created in the portal (vt_live_…) and short-lived playground keys (vt_pg_…) join the server's key check; a server with the portal enabled is never open.
Docs at docs.vartalaap.si (this site).

Rust server over the native C++ engine: POST /v1/tts (wav / pcm16 / opus, chunked from the first 80 ms frame), WS /v1/tts/stream (JSON events + binary audio, many utterances per connection), GET /v1/voices, /healthz, /readyz, /metrics.
Hinglish normaliser ported byte-exact from the training pipeline (66 canonical cases), en_digits option for codes.
503 + Retry-After when every worker is busy; per-request JSON log with ttfa_ms, rtf, audio_s, chars.
Measured in Mumbai on a c3-standard-4: 41 ms end-to-end first audio warm (18 ms engine-side with a cached prefill), 12.4 audio-seconds per wall-second at four streams.