HumanSignal / HumanSignal/label-studio

Self-hosted Label Studio is unusable offline (hard frontend dependency on internet)

Open
#9,086 3 comments 4 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
28.3k
Forks
3.7k
Avg merge
14h
Merged PRs (30d)
15

Description

Label Studio version: 1.21.0
Image: heartexlabs/label-studio (official Docker image)
Deployment: self-hosted with local PostgreSQL
Environment: offline / air-gapped

Expected behavior:
A self-hosted Label Studio instance must work fully offline when all data,
database, and services are local and analytics are disabled.

Actual behavior:
When the machine has no internet connection:
- UI loads but project pages hang indefinitely
- Backend APIs respond normally (200 OK)
- No pending requests, no visible errors
- The moment internet connectivity is restored, the UI immediately works

This makes Label Studio unusable offline.

Disabled configuration (confirmed at runtime):
- COLLECT_ANALYTICS=0
- SENTRY_DSN=
- FRONTEND_SENTRY_DSN=

No references to Sentry or Google Analytics appear in:
- rendered HTML
- served JS bundles

Nevertheless, the frontend still blocks without internet access.

Why this is critical:
- Breaks air-gapped and regulated deployments
- Violates expectations of self-hosted software
- Creates a hidden online dependency without warning or documentation

This is not a configuration issue.
It is a frontend architecture problem: the UI implicitly depends on external
connectivity even in self-hosted mode.

Request:
Please remove all implicit frontend dependencies on external services or
explicitly document that Label Studio cannot run offline.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.