Self-host Wyoming Piper with Levelrail

Fast local text to speech over the Wyoming protocol, used by Home Assistant voice assistants. Downloads the chosen voice on first start.

  • Authorrhasspy
  • LicenceMIT
  • Memory512 MiB
  • Services1

How to self-host Wyoming Piper

  1. Pull the images

    One image is pulled on your server.

    Show images
    • rhasspy/wyoming-piper:2.5.2
  2. Create the app

    One service starts in a single Compose app, with 1 named volume mount for your data, on port 10200.

  3. Fill in the secrets

    You do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

After the first start

  • Add the Wyoming integration in Home Assistant and point it at port 10200. The first start downloads the voice, so wait a minute.

Wyoming Piper requirements

Memory
About 512 MiB
Architectures
amd64 unknown, arm64 unknown
Ports
10200
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
MIT, permissive license
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Wyoming Piper. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the Wyoming Piper docs page.

Deploy Wyoming Piper your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Wyoming Piper from the CLI

levelrail-cli templates deploy wyoming-piper --name my-wyoming-piper

Deploy Wyoming Piper with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/wyoming-piper/deploy

Wyoming Piper configuration

Wyoming Piper services

ServiceImagePortsVolumes
wyoming-piper rhasspy/wyoming-piper:2.5.2 10200 data -> /data

Wyoming Piper environment variables

The catalog lists no environment variables for this template.

Ports and volumes

Ports
10200
Volumes
1 named mount: data -> /data

Wyoming Piper FAQ

How much memory does Wyoming Piper need?

The catalog lists about 512 MiB of memory for Wyoming Piper.

Does Wyoming Piper run on arm64?

For Wyoming Piper, arm64 support is not confirmed; amd64 is unknown.

What licence is Wyoming Piper under?

Wyoming Piper is licensed under MIT, which is permissive, with few conditions on reuse.

Does Wyoming Piper need configuration before it starts?

No. The template fills in its own defaults.

Which ports does Wyoming Piper use?

Wyoming Piper listens on port 10200 inside the stack.

Where does Wyoming Piper keep its data?

In a named volume: data mounted at /data.

Can I deploy Wyoming Piper on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Wyoming Piper, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image rhasspy/wyoming-piper:2.5.2 is what you deploy there.

levelrail-cli templates deploy wyoming-piper --name my-wyoming-piper