Self-host Label Studio with Levelrail
A flexible data labeling tool for text, images, audio, and video, with export to common ML formats.
- AuthorHumanSignal
- LicenceApache-2.0
- Memory1 GiB
- Archarm64
- Services1
How to self-host Label Studio
-
Pull the images
One image is pulled on your server.
Show images
heartexlabs/label-studio:1.21.0
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 8080.
-
Fill in the secrets
1 secret is generated and stored encrypted, 2 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Label Studio requirements
- Memory
- About 1 GiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 8080
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- Apache-2.0, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 8080 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Label Studio. 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 Label Studio docs page.
Deploy Label Studio your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Label Studio from the CLI
levelrail-cli templates deploy label-studio --name my-label-studio Deploy Label Studio with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/label-studio/deploy Label Studio configuration
Label Studio services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| label-studio | heartexlabs/label-studio:1.21.0 | 8080 | label_studio_data -> /label-studio/data |
Label Studio environment variables
| Variable | Service | Value |
|---|---|---|
| LABEL_STUDIO_DISABLE_SIGNUP_WITHOUT_LINK | label-studio | Preset by the template |
| LABEL_STUDIO_PASSWORD | label-studio | Generated at deploy |
| LABEL_STUDIO_USERNAME | label-studio | Preset by the template |
Ports and volumes
- Ports
- 8080
- Volumes
- 1 named mount: label_studio_data -> /label-studio/data
Label Studio FAQ
How much memory does Label Studio need?
The catalog lists about 1 GiB of memory for Label Studio.
Does Label Studio run on arm64?
For Label Studio, an arm64 image is published; amd64 is image published.
What licence is Label Studio under?
Label Studio is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does Label Studio need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does Label Studio use?
Label Studio listens on port 8080 inside the stack.
Where does Label Studio keep its data?
In a named volume: label_studio_data mounted at /label-studio/data.
Can I deploy Label Studio 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 Label Studio, 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 heartexlabs/label-studio:1.21.0 is what you deploy there.