Kiwi TCMS vs TestLink: Which Open Source Tool Fits Your Team

A QA lead evaluating open source test case tools eventually lands on the same two names in the Kiwi TCMS vs TestLink debate. Both show up in the same searches, both are free to self host, and most comparisons online are written by someone with a product to sell once you finish reading. That makes the actual decision harder, not easier, because the real differences between these two tools are specific, dated facts, not vibes.

This post has no stake in the outcome. It lays out what each tool actually is right now, checked against their own release notes and pricing pages, and names which team each one suits.

The honest summary up front

Both TestLink and Kiwi TCMS are real, maintained, open source projects. Neither is a dead end, and neither is obviously better than the other in the abstract.

The choice mostly comes down to your stack, what you need to integrate with, and how you feel about a free tier that carries ads and no version pinning. That is the whole post in one paragraph. Everything below is the detail behind that sentence, with dates and numbers so you can check the claims yourself.

TestLink, checked 25 August 2026

TestLink is GPL-2.0 licensed and written in PHP, with about 1.6k stars on GitHub. Version 1.9.20 is the final release in the 1.9.x line. A 2.x line is in active development, and the maintainer posted a progress update on 6 December 2025. That is aging software, not abandoned software, and the two are not the same thing.

The practical fact that matters most for a team planning to leave TestLink later is its export format. TestLink's XML export carries case structure reasonably well, including titles, steps, expected results and folder hierarchy.

It keeps almost no run history. If your team cares about historical execution data surviving a future migration, that is the detail to plan around now, not discover later when the export finishes and the pass and fail record from the last two years is simply gone.

Kiwi TCMS, checked 25 August 2026

Kiwi TCMS is also GPL-2.0 licensed, built on Django, with about 1.2k GitHub stars and over 500,000 container pulls. Version 16.3 shipped on 24 August 2026. This is a healthy, actively maintained project, and it is worth saying plainly rather than hedging.

A few specifics change the calculus for a team evaluating it:

• The free Community Edition container displays ads from EthicalAds inside the instance you host yourself
• Ad free images require the Self Support subscription, priced at 25 dollars a month according to kiwitcms.org's "Self Support Subscription Explained" page, dated 20 August 2025
• Community Edition builds are x86_64 only, so there is no aarch64 image on the free tier, which rules out an Apple Silicon laptop or a Graviton instance
• Community Edition is rolling release with no version-tagged images, so a free user cannot pin a specific version, and version tags come with the paid tier

The EthicalAds point deserves a beat of clarification, because it sounds worse than it is. Those ads are cookie free and the revenue goes to Open Collective, so this is not a privacy problem. It is simply the fact that advertising runs inside self hosted software, which surprises people the first time they see it in their own instance.

Where each tool wins

TestLink's advantage is accumulated history. Teams that have run it for years have a large installed base, a lot of institutional knowledge about how it behaves, and a PHP stack the organization already runs elsewhere. That familiarity has real value and should not be discounted just because the codebase is older.

Kiwi TCMS's advantage is a modern foundation. It runs on a current Django codebase, ships an actual API with personal access tokens, and offers roughly eleven bug tracker integrations along with automation framework plugins. A team already living in a modern Python or CI heavy stack will find it fits more naturally.

• TestLink fits a team with a long TestLink history, a PHP environment, and no near term plan to integrate with modern bug trackers
• Kiwi TCMS fits a team that wants an active API, wants bug tracker integrations, and can accept ads or pay 25 dollars a month to remove them
• Neither fits a team that needs multi tenancy on a free tier, since Kiwi TCMS reserves that for its Enterprise plan

A worked scenario: the migration nobody planned for

Picture a QA lead at a 12 person engineering team who adopted TestLink four years ago because the PHP stack made it an easy install. The suite has grown to 900 cases across 30 test plans. This year the team hired two backend engineers who live in Python and want an API to pull test results into a dashboard they already built.

TestLink has no equivalent API for that job. The QA lead evaluates Kiwi TCMS specifically because of its API and personal access tokens, and runs a trial on the free Community Edition. The ads are a minor annoyance during evaluation, and the team decides the 25 dollar Self Support tier is worth it once they commit, since a shared team tool with ads inside it looks unfinished to visiting stakeholders.

The harder problem is exit. The 900 TestLink cases export as XML with structure intact, but four years of run history does not come across. The team accepts that loss because the structure matters more to them than four year old pass and fail records, and writes that decision down before the cutover rather than discovering it as a surprise afterward.

The exit cost neither project advertises

Every tool a team adopts is also a tool a team might one day leave, and the exit cost rarely gets mentioned on a features page.

TestLink's XML export keeps case structure but drops run history almost entirely, so a team migrating away loses its execution record unless it archives that data separately first. Kiwi TCMS has a working API that can pull data out programmatically, but full SQL export sits behind a paid tier, so a free tier user planning an exit needs to budget time for the API route instead.

Neither of these facts is a reason to avoid either tool. They are simply the numbers nobody puts on the comparison page, and a QA lead planning a year out should know them before committing.

Kiwi TCMS's pricing ladder

For teams that expect to outgrow the free Community Edition, the paid tiers on kiwitcms.org's features page run 25, 75, 600 and 2000 dollars a month. Multi tenancy specifically sits at the 600 dollar Enterprise tier, not lower.

A team planning to run one instance per client or per department should factor that into the real cost of Kiwi TCMS well before they hit the limit. A team that only ever needs a single shared instance will likely never touch that tier at all.

Which team each one suits

A team with years of TestLink history, a PHP stack, and modest integration needs has little reason to switch. The 2.x line in development is worth watching, but the current 1.9.20 release still does its job for a team that already knows its quirks.

A team starting fresh, or one that wants a real API and bug tracker integrations, is better served by Kiwi TCMS. The ads and lack of version pinning on the free tier are real costs, and a team that finds those costs too high has a straightforward option: pay for the Self Support tier at 25 dollars a month, or look elsewhere.

Either way, the decision should rest on your stack and your integration needs, not on which project has the shinier landing page this month.

When it might be time to look past both

Some teams outgrow the open source category entirely, not because either tool is broken, but because they want case management without also managing a self hosted instance, its updates, and its ad configuration. That is a fair reason to look at a third option, and it is worth doing once you know exactly what you would be trading away.