Skip to main content
Each model ships as its own Helm chart, which installs the whole speech stack into a cluster you run, with an online or an offline billing profile.
This page covers what the deployment involves and what you need to decide. The commands, values, and troubleshooting are in the deployment runbook, which you download from Developer → Self Host with the chart version you install. The runbook is versioned with the chart; this page is not, so follow the runbook when they differ.

​
Billing profile

The billing modes are two profiles of the chart. The online profile can also pull the model weights from S3-compatible storage, Fish Audio’s or your own, instead of the in-cluster model warehouse. Installing either profile still pulls images and the chart from a registry; for a cluster with no network access at all, see Air-gapped deployments.

​
Before installing

The chart installs everything into one namespace. Arrange the rest yourself:
  • Shared storage, mounted at the same path on every node. See Requirements.
  • GPU scheduling: tolerations and node selectors, if your GPU nodes are tainted or you run more than one GPU type.
  • Ingress and TLS, off by default: put your own ingress or load balancer in front of the API service, or turn on the chart’s.
  • Secrets for registry credentials, the license bundle, and model storage, preferably from your secret manager. The services that check the license stay down until its Secret exists.
  • Metrics: the chart exposes Prometheus scrape annotations and creates no ServiceMonitors.
  • Reference voices, staged on shared storage by you or the optional voice sync before traffic that uses them starts.
  • Replica counts: talk to your account team before changing them.

​
What to expect

The first install is slow: the inference worker and the vocoder fetch their weights and prepare for your GPU type before either becomes ready. What they download or compile stays on shared storage, so later starts are quicker, as long as that storage persists. Upgrades, rollback, and uninstall are standard Helm operations; the runbook covers the order and the checks.

​
Next steps