TestLink and Kiwi TCMS Alternatives: When to Move On

If you are searching for a TestLink alternative or a Kiwi TCMS alternative, you have already made the decision. Nobody types either phrase while still happy with what they have. What you actually need is not another reason to leave. You need to know exactly which situation you are in, because the two are different problems with different fixes and different costs to move. This post names the moment each tool stops fitting, then says plainly what to move to and what that move costs in practice.

Two good tools, two different reasons people leave them

TestLink and Kiwi TCMS are both real, useful, free tools, and this post is not going to pretend otherwise.

TestLink's problem is maintenance and interface. The tool still runs fine but the people who know how to operate it have moved on. Kiwi's problem is the free tier's shape. The project is healthy but the container you get for free is architecture limited, unpinnable, and carries ads.

Growing past that container means paying, which is a completely reasonable thing for a maintainer to ask. It is worth knowing before the migration weekend rather than during it.

TestLink: still maintained, just aged past what a new hire will accept

Checked on 25 August 2026, TestLink is still maintained, not abandoned. Version 1.9.20 is the final release of the 1.9.x family. A 2.x line is in active development. The maintainer posted a progress update on 6 December 2025. It is licensed GPL-2.0, written in PHP, and has about 1.6 thousand stars on GitHub. Most pages ranking for this term get this basic fact wrong, so it is worth stating plainly before anything else.

The real reason teams leave TestLink is not that it stopped working. It is that the interface and the underlying stack have aged past what a new hire joining in 2026 will accept without complaint. A junior engineer who has only ever used modern web tools spends her first week just locating where test suites live in a navigation structure that predates conventions she takes for granted.

The single most important practical fact for anyone actually leaving is the export. TestLink's XML export carries case structure across cleanly. It keeps almost none of the run history. A team migrating a suite built up over three years typically brings across the steps and definitions. They lose the record of which runs passed, which failed, and when.

Kiwi TCMS: healthy and shipping, but the free container has a shape

Kiwi TCMS is actively maintained and healthy. Version 16.3 shipped 24 August 2026. It is licensed GPL-2.0, has about 1.2 thousand GitHub stars, and its container images have been pulled over 500,000 times. Say this plainly before anything critical. It is true, and a reader who feels a tool is being unfairly trashed stops trusting the rest of the page.

Here is the free tier's shape, each fact sourced to the page it came from.

• EthicalAds served inside your own self-hosted container, with ad-free images available at $25 a month through the Self Support subscription (Self Support Subscription Explained, 20 August 2025).
• Images built for x86_64 only, with no Apple Silicon or Graviton build available.
• Rolling release only, with no version tagged images, meaning no way to pin the version you are running.
• Multi-tenancy, meaning separate isolated projects under one install, held at the Enterprise tier for $600 a month (kiwitcms.org features page and Community Edition Explained, 18 February 2026).

Kiwi publishes all of this openly, and charging for support is a legitimate business model, not a bait and switch. The only real question is whether the free tier is where a growing team can actually live day to day.

What leaving actually costs, beyond exporting the case list

Getting the test cases themselves out of either tool is the easy half of a migration. Cases are structured data, and structured data exports reasonably well in both tools.

The hard half is everything attached to the cases.

• Run history: the record of which run passed or failed and when. Both TestLink's XML export and a typical free tier migration tend to lose or badly compress this.
• Attachments: screenshots and logs linked to specific historical runs, which do not travel with a plain case export.
• Custom fields: any field a team added beyond the tool's defaults, which frequently has no equivalent field waiting on the other side.
• Traceability links: the connection between a test case and the requirement or ticket it covers. This is often stored as a loosely typed reference that does not map cleanly.

Two real situations with real numbers

A fourteen hundred case regression suite built over three years exports cleanly from TestLink as XML. The steps and case structure arrive intact in the new tool. The eleven months of run history recorded against those cases does not travel with the export. The team has to decide whether that history is worth reconstructing or worth losing entirely.

A six person QA team evaluating whether to keep growing on Kiwi TCMS's free tier runs into the architecture wall directly. Two of the six now have Apple Silicon laptops issued this year. The free container image will not start on either machine without extra work nobody had budgeted for. That forces the paid tier conversation earlier than the team expected.

What to actually look for in a replacement

Rather than pitching a specific product here, this is the checklist worth running against any candidate.

• The complete product self-hostable, with nothing functional held back for a paid tier.
• Architectures actually built and published, not just promised on a roadmap.
• Version pinning available, so you can answer what was running on any given date.
• An import path that carries run history along with case structure, not just the cases themselves.
• Clarity on where any AI features send data and whose API keys they use.

That last point matters more every year as tools add AI assisted case generation. Know whether your data leaves your infrastructure before you turn a feature like that on.

Where Tesbo fits, briefly

Tesbo is Apache 2.0 licensed. The full product runs self-hosted on your own Postgres database, using your own AI keys rather than a vendor's. It is worth being plain about what Tesbo does not do. It does not run or schedule the tests themselves.

Tesbo manages and documents test cases, which is a different job from execution. Conflating the two is where a lot of tool comparisons go wrong. Current plans and any limits are on the pricing page, since those details change more often than a blog post should try to track.

For background on the general problem of open source test tools quietly limiting their free tiers, our companion piece on the open source test case management trap covers the pattern in more depth, with the same sourcing standard applied throughout.