Taiga
Open-source agile project, issue and team planning application.
- AWS
- DigitalOcean
- Railway
- Linode
- Vultr
- Hostinger
- LumaDock
5 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Cloudron package; Application platform deployment
Runs in
Documented customer environment
Taiga frontend, backend, database, task workers and persistent media.
- AWS: Customer cloud account
- DigitalOcean: Customer cloud account
- Linode: Customer cloud account
- Vultr: Customer cloud account
- Hostinger: Customer VPS account
- LumaDock: Customer VPS account
- Railway: Customer platform workspace
- AWS
- DigitalOcean
- Railway
- Linode
- Vultr
- Hostinger
- LumaDock
Servers / containers
Operated by
Your team
Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Cloudron Store ↗ · Source checked 2026-11-19
- DigitalOcean: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Cloudron Store ↗ · Source checked 2026-11-19
- Linode: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Cloudron Store ↗ · Source checked 2026-11-19
- Vultr: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Cloudron Store ↗ · Source checked 2026-11-19
- Hostinger: Customer VPS account · Customer-operated
An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.
Cloudron Store ↗ · Source checked 2026-11-19
- LumaDock: Customer VPS account · Customer-operated
An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.
Cloudron Store ↗ · Source checked 2026-11-19
- Railway: Customer platform workspace · Customer-operated
Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Railway ↗ · Source checked 2026-11-19
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Cloudron package; Application platform deployment |
|---|---|
| Infrastructure | Servers / containers Taiga frontend, backend, database, task workers and persistent media. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure. |
| Licensing model | Open Source / Open Core Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. |
| License | Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
4 of 12 fields researched (33%) · 4 documented · 0 unresolved. Evidence coverage is not a feature score.
- Single sign-on
AvailableEvidence and scope for Single sign-on
The upstream self-hosting guide documents GitHub and GitLab OAuth user login, disabled by default. Both backend and frontend settings, registered OAuth clients and public-registration settings must align. This establishes those social/provider login paths, not general SAML/OIDC or Cloudron-package SSO support.
Upstream Taiga user login configuration; packaged distributions may differ · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The official taiga-docker repository supplies Compose, initialization configuration and environment settings for application, async worker, database, events and supporting services. Configure secrets, TLS, email and persistent volumes, and align all component image versions before use.
Official self-hosted Compose stack; not the source-development quickstart · Source ↗ · Deployment artifact ↗ (main (moving branch); choose compatible component release tags) · Reviewed 2026-11-20
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The Cloudron package declares 300MB minimum app memory. The platform additionally requires at least 2 GB RAM and 20 GB disk; this is not whole-system, data-volume or HA sizing.
Selected Cloudron application package; add database, files, backups and concurrent workload requirements · Source ↗ · Cloudron platform requirements ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Taiga; software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
Show all fields (8 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
- Release snapshot / cadence
- Not researched Supply a public source.
Scope & considerations
Cloudron packages Taiga 6.10.2 separately from its own package version; the Railway recipe is a separate deployment. OAuth and external integrations require their own credentials.
Community & maintenance
The reviewed upstream contributor history includes bameda, superalex, jespino, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.
Category fit
- Project management
- Open-source agile project, issue and team planning application.
Compare within Project management
- Azure DevOps ServerSource control, CI/CD, work tracking, testing and package management installed on Azure virtual machines you operate.
- Azure
- Ever GauzyOpen-source business operations platform for people, projects, time and financial records.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Railway
- Render
- Heroku
- Fly.io
- JetBrains YouTrack ServerCustomer-hosted project and issue management application from JetBrains.
- AWS
- Azure
- Google Cloud
- Oracle Cloud
- Jira Software Data CenterCommercial self-managed Jira Software edition deployed on customer-operated cloud or Kubernetes infrastructure. New Data Center subscriptions are restricted to eligible existing Atlassian customers.
- AWS
- Azure
- Google Cloud
- KanSelf-hosted kanban boards for projects and team tasks.
- Railway
- KaneoSelf-hosted project, board and issue management application.
- Railway
- Leantime Self-HostedCustomer-hosted project and task management application for cross-functional teams.
- Railway
- MantisBTSelf-hosted issue and bug tracking application.
- AWS
Showing 8 of 13 other listings in Project management. These products address related workflows; read their category-fit notes before comparing scope. See all of Project management →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Cloudron Store ↗www.cloudron.io
- Railway ↗railway.com
- MPL-2.0 LICENSE ↗github.com
- Releases v6.10.2 ↗github.com
- Cloudron customer-server and named-provider installation ↗docs.cloudron.io
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Cloudron Store ↗ · AWS, DigitalOcean, Linode, Vultr, Hostinger, LumaDock
Package platform documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
The reviewed Cloudron application package runs on the customer server. Pair it with Cloudron’s named-provider installation procedure; Cloudron subscriptions, package updates and upstream support are separate.
- Railway ↗ · Railway
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Taiga frontend, backend, database, task workers and persistent media. Cloudron packages Taiga 6.10.2 separately from its own package version; the Railway recipe is a separate deployment. OAuth and external integrations require their own credentials. This source is distinct from the Cloudron package.
- Cloudron Store ↗ · AWS, DigitalOcean, Linode, Vultr, Hostinger, LumaDock
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Community, governance or adoption evidence ↗github.com
- Upstream project ↗github.com