ZenTao: a PHP scrum and bug-tracking stack with a dual-licence split between the free and commercial builds
Zentao is an agile(scrum) project management system/tool, Free Upgrade Forever!
At a glance
- What is it?
- ZenTao is a self-hosted PHP project management system from EasySoft that bundles product, project, QA, document and organisation modules, licensed under AGPL or ZPL with paid Biz and Max editions layered on top. The interesting question is not whether it covers a lot of ground, but where the open source build stops and the commercial build begins.
- Who is it for?
- ZenTao Open Source suits teams that want an all-in-one, self-hosted scrum and bug-tracking system on PHP and are content with the feature boundary the vendor draws around the free build. It is the wrong tool for anyone who needs process definition, risk management, CMMI-oriented reporting, or OA and operations modules out of the box, because the README places those in Biz and Max rather than the open source edition.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository last received commits 26 days ago.
- What is it written in?
- Mainly PHP, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 15, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
The problem ZenTao solves: one PHP install instead of four tools
Most small engineering organisations end up assembling a stack: a tracker for bugs, a board for sprints, a wiki for documents, and something for release or test coordination. Each tool has its own accounts, its own permission model, and its own export format. ZenTao's pitch is consolidation. The README describes it as an all-in-one platform covering product management, project management, quality management, documentation management, organisation management, and office management, with the whole set shipped as one PHP application.
The intended audience is broad on paper. The README says ZenTao has been used by organisations in finance, telecoms, manufacturing, and software development since 2009. That history matters less than the shape of the product: it is a self-hosted web application, which means the buyer is whoever can run a LAMP-style stack and wants the data to stay on their own hardware. Teams that already have a managed SaaS workflow and no appetite for server maintenance are not the target.
The design choices are explicit rather than emergent. ZenTao separates the concepts of product, project, and QA so that product owners, developers, and testers share a system while keeping distinct responsibilities, and the README states that the three interact through stories, tasks, and bugs. If your team does not distinguish a product backlog from a project backlog, that separation will read as overhead rather than structure.
Scrum, Waterfall and Kanban as three built-in models
The README states that ZenTao's management concept is built on Scrum, Waterfall, and Kanban, and describes what each model is for. Scrum is presented as adaptable and suited to rapid iteration. Waterfall is presented as stage-divided with strict process control, aimed at projects defined in advance with few changes. Kanban is presented as value-flow and visualisation oriented, for teams whose process is already transparent.
What the README does not explain is the mechanism. It does not say whether these are templates chosen at project creation, whether a project can move between models, or what data structures differ underneath. That is a gap worth flagging, because in practice the model choice usually determines which fields, states, and reports you get, and migrating a live project between them is rarely free. Anyone evaluating ZenTao on the strength of supporting three methodologies should confirm the switching behaviour on the demo rather than assume it is a per-view toggle.
The three-model framing does tell you something about the product's ambition. A tool built only for scrum would not carry Waterfall stage control at all. ZenTao is trying to serve organisations that run different project types side by side, which is common in manufacturing and finance environments where software work sits next to fixed-scope delivery.
How you actually get it running
The README does not include an install command, a Docker invocation, or a configuration key. It points to the official website, the manual at zentao.pm/book, an FAQ page, and an extension directory. That is the honest starting point: installation instructions live in the manual, not in the repository README, and this article cannot reproduce steps that the supplied material does not contain.
What the repository metadata does give you is the constraint set. The primary language is PHP, and the README's badge declares PHP >= 5.6. The default branch is main, and the project is not archived. Releases are versioned with a date suffix, for example zentaopms_21.7.1_20250529 for release 21.7.1, published 2025-05-29, with 21.5 and 21.4 before it in the same year. That naming convention is useful operationally: it tells you the release cadence is roughly every few weeks to a couple of months, and it lets you pin an exact artefact rather than tracking a moving branch.
The README also lists three public demos: ZenTao Opensource, ZenTao Biz, and ZenTao Max. Evaluating the open source build against the Biz demo side by side is the cheapest way to find the feature boundary before you install anything. There is no stated support policy, no documented upgrade path, and no migration tooling in the supplied material, so treat the upgrade story as something to read in the manual before you commit data to it.
The licence is the least clear thing in the repository
This is the part to read carefully. The repository metadata reports the licence as NOASSERTION, which means the automated classifier could not resolve it to a single SPDX identifier. The README, by contrast, carries a badge reading AGPL or ZPL and links the COPYING file in the repository root, and the licence section states that ZenTao is licensed under AGPL and ZPL.
A dual licence of AGPL and ZPL is not the same as a permissive licence with an alternative. AGPL imposes network-use obligations: if you modify the software and let users interact with it over a network, the AGPL requires you to offer them the corresponding source. ZPL, the Zope Public License, is a different instrument with different conditions. Which one applies to your use, and whether you may choose, is a question the README does not answer and this article will not answer either. It is a question for your own legal review, and the COPYING file is the document to hand to that reviewer.
The practical consequence is that ZenTao is not a drop-in for teams that intend to embed a tracker inside a closed product. If you plan to modify the PHP source and expose it to customers, the AGPL branch of that dual licence is the branch that matters, and it is stricter than most teams assume when they see the word open source.
Where the open source build stops
ZenTao is not one product. The README's collapsed section describes three commercial editions. ZenTao Biz adds operations and maintenance management, OA office management, feedback management, and document version management with online preview, and the README frames it as covering roles and processes outside the development cycle. ZenTao Max adds process control, process definition, project measurement, issue management, risk management, quality assurance, and project reporting, and the README states it supports CMMI implementation and helping enterprises pass CMMI assessment. ZenTao Cloud is a SaaS offering with automatic updates, HTTPS, and automatic backups that users can download.
That list is the real limitation of the open source edition, and it is worth stating plainly rather than treating as a footnote. If your organisation needs formal risk registers, defined process models, or CMMI-oriented reporting, the README places those capabilities in Max, not in the free build. Similarly, OA and operations modules sit in Biz. The comparison page at zentao.pm/page/vs.html is the place to confirm exactly which modules fall on which side, because the README only summarises.
There is a second, quieter limitation. The README's marketing claims about productivity and transparency are not backed by any measurement in the material, and the project does not publish benchmark data here. Whether ZenTao reduces your coordination cost depends on whether your team adopts its product/project/QA separation, which is a process decision, not a software one.
How ZenTao differs from a tracker-first tool like Trac or Redmine
The obvious comparison is with tracker-first systems such as Redmine or Trac, which start from issues and grow outward through plugins. ZenTao inverts that. It starts from a defined model of product, project, and QA, and issues (stories, tasks, bugs) are the currency that moves between those roles. Redmine gives you a flexible issue schema and lets you shape workflow per tracker; ZenTao gives you a prescribed structure and expects you to work inside it.
That difference shows up in adoption cost. A Redmine deployment can begin as a bug list and expand. ZenTao asks you to decide what a product is, what a project is, and who owns QA before the tool is useful, because the README states those three concepts are how product owners, developers, and testers coordinate. Teams with a strong existing process will find that mapping effort straightforward. Teams without one will find the tool opinionated in ways that force conversations they may not be ready for.
The second axis is the commercial boundary. Redmine's plugin ecosystem is largely third-party and independently licensed. ZenTao's extended functionality is vendor-controlled and edition-gated, which makes the upgrade path predictable but also means the free build's ceiling is set by a business decision rather than a community one.
Maintenance, upgrades and the cost of staying current
The release naming gives a usable maintenance signal. Versions carry a date, and the supplied releases show 21.4 in January 2025, 21.5 in March 2025, and 21.7.1 in May 2025. That is a steady cadence rather than a burst, and the last push timestamp on the repository is recent. For an operations team, the implication is that you will be applying updates several times a year if you want to stay near the current release.
The material does not describe an upgrade procedure, a database migration tool, or a supported-version window. That absence is itself information: before you put production data in, read the manual's upgrade chapter and confirm whether jumps across multiple minor versions are supported or whether you must step through each release. Also confirm the PHP version your target release expects, since the README badge states PHP >= 5.6, which is a floor rather than a recommendation and is well behind current PHP releases.
On cost, the README's own framing is the relevant fact: the open source edition is free, and Biz, Max, and Cloud are separate paid offerings. There is no published price in the supplied material. Budgeting therefore means deciding in advance which edition your process actually requires, using the comparison page and the three demos, rather than discovering the gap after a migration.
Editorial conclusion
ZenTao Open Source suits teams that want an all-in-one, self-hosted scrum and bug-tracking system on PHP and are content with the feature boundary the vendor draws around the free build. It is the wrong tool for anyone who needs process definition, risk management, CMMI-oriented reporting, or OA and operations modules out of the box, because the README places those in Biz and Max rather than the open source edition. Before committing, read COPYING and the licence badges, since the repository metadata reports NOASSERTION while the README states AGPL and ZPL, and check the ZenTao Opensource demo against the specific modules you intend to run in production, particularly whether your intended workflow depends on anything the comparison page lists as Biz or Max only.
Community notes