Skip to main content
Both offline modes need no outbound access at runtime, but installing them still takes artifacts from Fish Audio: the images and, on Helm, the chart. An air-gapped deployment is about getting those across the boundary, together with the license bundle and the reference voices you use. The license expires, so plan a recurring transfer, not a one-off; voices are copied in as archives, since voice sync cannot reach Fish Audio from there.
Fish Audio does this with you as part of an air-gapped delivery, and the step-by-step procedure is in the deployment guide for the version you install. This page is what to expect and what to plan for.

​
Which one to choose

The air-gapped All-in-One appliance is the straightforward answer to a strict air gap: one image, moved to the disconnected host as a file and loaded there. Beyond the image, the license bundle — and, in the external-weights modes, the weight fileset — has to be carried across. Its online counterpart cannot run air gapped: it authorizes every request against Fish Audio. The Helm chart is more work, because the release is many images rather than one. Every image has to be mirrored into a registry the cluster can reach and the release pointed at it, component by component. Plan for the whole set, and expect to do it with your account team rather than alone.

​
Offline usage accounting

Offline billing records usage in a signed ledger on persistent storage. It is durable data, not cache: back it up, and agree with your account team how often to send it for reconciliation.

​
Proving there is no egress

Regulated deployments usually need evidence rather than a configuration review, and your deployment guide carries the exercise. It shows both that the deployment works without the internet and that, with voice sync off, it makes no calls when the internet is available. On Helm it is a cluster-level exercise, so involve whoever runs your cluster early: a namespace-scoped account cannot complete it.

​
Next steps