Self-host Taiga

updated Sep 2026deployed by usprices checked · Jul 2026Install verified on Ubuntu 26.04 · Sep 2026 · how we test

We earn commissions when you shop through the links below. Full disclosure →

Open-source agile project management platform built around Scrum and Kanban, with backlogs, sprints, epics, user stories, issue tracking, and a wiki. The self-hosted stack is the same MPL-2.0 open-source code that powers Taiga's cloud product — self-hosting is free with no project, member, or storage caps and no feature gate; only the hosted cloud plans and an optional paid on-premise support/SLA contract sit on top of the identical software.

Key facts

CategoryProject Management

LicenseMPL-2.0

StackPython, AngularJS, PostgreSQL

Min RAM2048 MB

Official imageyes

Measured idle RAM722 MB

Difficulty

Sourcegithub.com/taigaio/taiga-docker

Websitetaiga.io

Our recommendation

Pick Taiga when you want a Scrum/Kanban-first tool — backlogs, sprints, epics, user stories, issue tracking, a wiki — and want confidence that self-hosting isn't a stripped-down edition: the self-hosted stack is the identical MPL-2.0 code behind Taiga's cloud product, with no project, member, or storage caps and no feature gate. The tradeoff is a heavier six-service Docker stack (four Taiga services plus Postgres and RabbitMQ) than the leaner apps in this cluster — budget for more moving parts to run and monitor.

Follow the Taiga deploy guide →

What you need

Any VPS with at least 2048 MB of RAM
A domain you control — most self-hosted setups need HTTPS in front of them
About an afternoon — budget time for troubleshooting

Where to host itaffiliate disclosure

Hetzner Cloudrun it on

From $23.59/mo · 2 vCPU / 4 GB / 80 GB · EU + US

Get Hetzner Cloud

Kamaterafree trial

From $4/mo · 1 vCPU / 1 GB / 20 GB · US + EU + Asia

Start free on Kamatera →

DigitalOceanalso works on

From $6/mo · 1 vCPU / 1 GB / 25 GB · US + EU + Asia

Deploy on DigitalOcean →

Paid link — we earn a commission if you shop through it.

Install

Run these commands on your server:

# Taiga — official docker-compose stack (taiga-back/taiga-front/taiga-events/taiga-protected + Postgres + RabbitMQ)
# Note: upstream's own compose file pins postgres:12.3, nginx:1.19-alpine, and rabbitmq:3.8-management-alpine (all EOL) — kept as-is here; research bumping them before a production deploy
git clone https://github.com/taigaio/taiga-docker.git --branch stable --depth=1 taiga && cd taiga
sed -i 's/^TAIGA_DOMAIN=.*/TAIGA_DOMAIN=SERVER_IP:9000/' .env
sed -i 's/^SECRET_KEY=.*/SECRET_KEY="change-me-to-a-random-string"/' .env
sed -i 's/^POSTGRES_PASSWORD=.*/POSTGRES_PASSWORD=change-me/' .env
sed -i 's/^RABBITMQ_PASS=.*/RABBITMQ_PASS=change-me/' .env
sed -i 's/^RABBITMQ_ERLANG_COOKIE=.*/RABBITMQ_ERLANG_COOKIE=change-me-too/' .env
./launch-taiga.sh
./taiga-manage.sh createsuperuser   #  →  http://SERVER_IP:9000  (log in with the superuser account you just created)

deploy guideHow to Deploy Taiga on a VPS vps picksBest VPS for self-hostingbenchmarked quarterly · re-priced monthly

What you take on

Taiga doesn't gate features on you, but the official install stack needs its own attention:

non-negotiableNo feature gating, confirmed. The paid cloud tiers differ only in storage/support, and the optional on-premise support contract is an SLA layered on the same open-source code, not a feature unlock — a real difference from the other apps in this cluster.

non-negotiableThe official compose file pins deliberately dated, end-of-life base images for Postgres, the reverse proxy, and RabbitMQ. Upstream ships it that way; research bumping them before a production deploy rather than assuming they're current.

non-negotiableIt's a six-service stack — four Taiga services (backend, frontend, events, protected) plus Postgres and RabbitMQ — at a 2 GB floor, more moving parts to monitor and back up than the lighter apps in this cluster.