Skip to main content
Run Rime’s text-to-speech engine in your own Baseten workspace, on Baseten’s autoscaling GPU infrastructure. Each model runs as a single-container deployment: the engine validates its own license and serves TTS directly, with no separate router.

Get started

Ready-to-use deploy configs for Rime’s models live in the rimelabs/rime-baseten-deploy repository. Each model directory contains a Baseten/Truss config.yaml plus a README with full deploy, secrets, and invocation steps.

Prerequisites

Before cloning the deployment repository, contact help@rime.ai for engine-image and license access. Your Baseten workspace needs these secrets:
  • gcp_rime_service_account
  • rime_license
  • rime_api_key
To deploy:
  1. Clone the repo and cd into the model directory you want.
  2. Set the three required secrets in your Baseten workspace. The per-model README describes each value.
  3. Push the config with the Truss CLI:
  1. Set the autoscaling concurrency target (each replica handles ~10 concurrent requests before a new one is added). See the model README for the exact Management API call.

Invoke

Once deployed, send inference requests to your model’s sync endpoint. The Rime API key is baked in via the rime_api_key secret, so callers authenticate to Baseten only. This request saves the audio to output.webm:
Play output.webm to confirm the deployment returns speech. raise_for_status() stops the script before it writes the file when Baseten returns an error status. For full setup instructions, including secrets and autoscaling, see the rime-baseten-deploy README for your chosen model.