Taiga Backend — Django API and Domain Backend for Taiga Project Management

Overview

Taiga Backend is the server-side component of the Taiga project-management platform. It provides domain logic and REST APIs for projects, epics, backlogs, user stories, sprints, tasks, issues, users, and permissions, using Django/Python with PostgreSQL, Celery, Redis, and related services.

Features and best fit

Based on official documentation; not hands-on tested · Content checked: 2026-09-20

Expose domain APIs for projects, backlogs, sprints, and issues

Taiga frontend and integrations use backend APIs to operate agile project-management resources, permissions, and workflows.

Sources: [2][5]

Combine Django, Celery, PostgreSQL, and Redis for backend processing

Django serves web requests, PostgreSQL persists domain data, and Celery/Redis-related components support asynchronous work.

Sources: [4][6]

For self-hosting or customizing Taiga APIs and domain behavior

The backend fits teams extending Taiga workflows, integrations, authentication, or project-management logic in their own infrastructure.

Sources: [2][6]

Do not evaluate the backend repository as the complete Taiga product

UI and asynchronous/event components live in other repositories and services. Follow the official self-hosting guide for the full frontend, database, queue/cache, media, proxy, backup, and upgrade architecture.

Sources: [6]

Official sources

[1]taigaio/taiga-back repository(2026-09-20)
[2]Taiga Backend README(2026-09-20)
[3]Taiga Backend MPL-2.0 license(2026-09-20)
[4]Taiga Backend requirements(2026-09-20)
[5]Taiga API documentation(2026-09-20)
[6]Taiga documentation(2026-09-20)

Supplemental curator note

This repository is not the complete Taiga UI; it is the backend responsible for project/backlog/sprint/issue domain logic and APIs. Its requirements include Django 3.2.x, Celery, PostgreSQL, and Redis-related components. For product evaluation, use the official self-hosted Taiga stack including frontend and asynchronous services.

Try it in 3 steps

1
Review the full Taiga self-hosting guide
taiga-back is not a complete UI by itself, so choose the official installation path for the full Taiga stack.
https://docs.taiga.io/
2
Start backend, database, async services, and frontend together
Run PostgreSQL, Taiga backend, asynchronous processing, frontend, and related services as a supported stack.
Follow the official Taiga self-hosted installation for the complete stack
3
Inspect both the UI and backend API
Create a project/backlog/sprint in the UI and inspect how the same resources are exposed by the backend API.
Open the Taiga UI and then inspect https://docs.taiga.io/api.html

Check the official README

Growth

Growth trends · Last 30 days

851 Stars

Trend data is still being collected.

Development activity

Last 90 days · weekly

Commits (last 30 days): 9
Open PRs: 34
Issues opened: 2
Issues closed: 3
PRs opened: 10
PRs merged: 8

Issues

2 / 3

Jun 23Sep 20

Issues openedIssues closed

Pull requests

10 / 8

Jun 23Sep 20

PRs openedPRs merged

Maintenance

Median first response: 23 hr
Issue response rate: 50% (1/2)

Based on up to the 100 newest issues opened by external users in the last 90 days. A first comment from an OWNER, MEMBER, or COLLABORATOR counts as a response; issues whose full comment history cannot be checked are excluded. The median and response rate update weekly.

Built with

Python

Categories and tags

GitHub data

GitHub dataView detailed GitHub data

View on GitHub

Stars: 851
Forks: 309
Watchers: 16
Open issues: 58
Contributors: 84
Primary language: Python
License: MPL-2.0
Repository last updated: Sep 9, 2026

Write a related article

Share a guide or use case for this OSS in Markdown. Articles are published after administrator approval.

Report incorrect information

Tell us if any listing information is incorrect or outdated.