{
 "schema_version": 1,
 "generated": "2026-11-09",
 "id": "humansignal-label-studio--run-a-team-labeling-server-with-docker-compose",
 "repo": "HumanSignal/label-studio",
 "repo_url": "https://github.com/HumanSignal/label-studio",
 "repo_slug": "humansignal-label-studio",
 "title": "Run a shared labeling server for a team",
 "page_title": "How to run a shared labeling server for a team with Label Studio",
 "summary": "Use the Docker Compose stack with Nginx and PostgreSQL for multi-user labeling.",
 "who": "A team lead coordinating several annotators across multiple datasets.",
 "problem": "Passing files around and merging labels from several people leads to lost and conflicting work.",
 "outcome": "One server where every annotation is tied to a user account, with multiple projects and cloud storage imports.",
 "steps": [
  "From a checkout of the repo, run `docker-compose up` to start Label Studio, Nginx and PostgreSQL",
  "Open the app at localhost and have each annotator sign up so their annotations are tied to their account",
  "Create one project per dataset and import from files or cloud storage such as Amazon AWS S3 or Google Cloud Storage",
  "For local S3 testing, run `docker compose -f docker-compose.yml -f docker-compose.minio.yml up -d`",
  "Use the REST API to pull finished annotations into your training pipeline"
 ],
 "agent_prompt": "Deploy HumanSignal/label-studio with the Docker Compose stack on <server>, connect project <name> to my <S3 or GCS bucket>, and write a script that uses the REST API to export completed annotations nightly.",
 "agents": [
  "claude-code",
  "codex",
  "cursor"
 ],
 "difficulty": "Intermediate",
 "time": "1 hour",
 "basis": "readme",
 "caveat": "If the server is reachable from the internet, put it behind HTTPS and restrict sign ups to your team.",
 "category": "Data and analytics",
 "tags": [
  "Data and analytics"
 ],
 "lang": "typescript",
 "requirements": [
  "Docker, or Python 3.10 or later for the pip install",
  "Docker Compose for the production stack with Nginx and PostgreSQL",
  "Optional: a model server built with the Label Studio ML backend for pre-labeling"
 ],
 "risk": "none",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [
  {
   "tag": "credentials",
   "notice": "Connecting cloud storage means giving Label Studio bucket credentials; use a key scoped to just the labeling bucket."
  }
 ],
 "best": false,
 "score": 0.8,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/humansignal-label-studio/run-a-team-labeling-server-with-docker-compose/",
 "md": "https://dedupedai.com/use-cases/humansignal-label-studio/run-a-team-labeling-server-with-docker-compose/index.md",
 "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/humansignal-label-studio--run-a-team-labeling-server-with-docker-compose.json",
 "api_version": "v1"
}
