Ga naar hoofdinhoud

Competitor sources

One entry per system in the parity ledger, so a reader of competitor parity, September 2026 can open the code, the documentation, the API reference and the issue tracker behind a cell, and the corpus directory that holds the column. Generated from the ledger's sources register (data.family.sources in procest/_ledger/parity-ledger.html, ConductionNL/market-intelligence, development, ledger v10). Every link was fetched on 2026-09-13; a link marked to verify did not answer a plain fetch that day, and the note says what it answered instead. Gitea, Taiga, Tuleap and Huly were read from their own corpus READMEs when batches 11 and 12 were still ahead of the ledger; ledger v10 folded both batches, and the register now carries all 41 entries.

Corpus paths are relative to the market-intelligence repository. A column's ratings live in the system's round<N>/ directory; the cross-system files live in procest/_round<N>/compare/.

Evidence classes​

classmeaning
drivenThe system was installed, seeded and driven, and every rating carries a file path, a screen or a computation the live engine returned. This is the only class that may produce a new matrix row.
documentedClosed source and not driven: rated from the API reference, the documentation, the public tracker, the release notes and the price pages, every cell quoting the page it rests on. Printed under its own label, documented, not driven, wherever its number appears, and never in a driven count or a driven ranking. An upper bound: every driven batch found something the vendor's page did not say. A driven column replaces it if a licence and a clock are ever spent.
trialSelf-hostable only under a paid or time-limited licence. Can reach the driven standard, at a cost and with a clock on it.
docs onlyCloud only, so it cannot be installed and driven. Ratings would come from a feature page, which is the exact thing round 2 was built to stop. Include for landscape, never as evidence.

Driven: installed, seeded and driven​

GLPI​

version read11.0.8
familyITSM help desk
licenceGPL-3.0
open coreno, verified in round 3: the only commercial hook is a support key that changes the marketplace listing
codeglpi-project/glpi
documentationuser documentation; developer documentation
APIlegacy REST API, apirest.md; high-level API
issue trackerGitHub issues
corpusprocest/glpi/round3/ and procest/_round3/compare/
noteThe user documentation root resolves to the French build; /en/latest/ answered 404 on 2026-09-13.

Zammad​

version read7.1.3
familyhelp desk
licenceAGPL-3.0
open coreno, verified in round 3: zero hits for licence_key, licensed_feature or entitlement
codezammad/zammad
documentationadmin documentation; user documentation; system documentation
APIREST API
issue trackerGitHub issues
corpusprocest/zammad/round3/ and procest/_round3/compare/

OpenProject​

version read16.6.10
familyissue and project
licenceGPL-3.0
open coreyes: 32 features gated at runtime, four degrade silently. Verified on the running instance, GET /api/v3/configuration returned an empty availableFeatures
codeopf/openproject
documentationdocumentation
APIAPI v3 documentation
issue trackercommunity work packages; GitHub issues
named on a comparison pageEasy8, Atlassian Data Center alternatives; dev.to, OpenProject vs Jira
corpusprocest/openproject/round4/ and procest/_round4/compare/ (PR 104)
noteThe Atw measurement ran on its two calculators: procest/openproject/round4/op-engine*.rb.

Plane Community​

version readv1.4.2
familyissue
licenceAGPL-3.0
open coreyes, by omission: the paid features are absent rather than gated, and the seams are visible
codemakeplane/plane
documentationdocumentation
APIdeveloper documentation and API reference
issue trackerGitHub issues
named on a comparison pageEasy8, Atlassian Data Center alternatives; dev.to, OpenProject vs Jira
corpusprocest/plane/round4/ and procest/_round4/compare/ (PR 104)

Redmine​

version read7.0.1
familyissue
licenceGPL-2.0
open coreno: zero entitlement hits in 351 Ruby files. Commercial pressure sits outside the tree, in plugins and in Easy Redmine
codeofficial Subversion; GitHub mirror redmine/redmine
documentationguide
APIREST API
issue trackerredmine.org issues
named on a comparison pageEasy8, Atlassian Data Center alternatives
corpusprocest/redmine/round4/ and procest/_round4/compare/ (PR 105)

Forgejo​

version read16.0.4
familyforge issues
licenceGPL-3.0 on fork-authored files, MIT on the 2,458 inherited ones
open coreno: zero entitlement hits in 3,314 Go files
codecodeberg.org/forgejo/forgejo
documentationdocumentation
APIAPI usage; Swagger on Codeberg
issue trackerCodeberg issues
corpusprocest/forgejo/round4/ and procest/_round4/compare/ (PR 105)

osTicket​

version read1.18.4
familyticket
licenceGPL-2.0
open coreno: six entitlement greps, zero hits. Eight free capabilities live in a separate plugins repository last pushed nineteen months before the core
codeosTicket/osTicket
documentationdocumentation
APIAPI documentation in the tree
issue trackerGitHub issues; forum
corpusprocest/osticket/round4/ and procest/_round4/compare/
noteThe documentation build is titled 1.17.7, one release behind the version driven.

FreeScout​

version read1.8.240
familyticket
licenceAGPL-3.0
open coreyes: 72 of 75 modules priced, 539.73 dollars for the set, 33 matrix rows gated, and the paywall runs through the free half
codefreescout-help-desk/freescout
documentationGitHub wiki; module store
APIAPI documentation
issue trackerGitHub issues
corpusprocest/freescout/round4/ and procest/_round4/compare/
notefreescout.net/docs/ answered 404 on 2026-09-13; the wiki is the documentation.

Znuny​

version read7.3.6
familyticket
licenceAGPL-3.0 and GPL
open coreno: 37 vendor packages, none priced. Six entitlement greps over Kernel/ and bin/ return zero hits
codeznuny/Znuny
documentationdocumentation index; LTS administrator manual; developer manual
APIPerl API reference; web services, the generic interface
issue trackerGitHub issues
corpusprocest/znuny/round4/ and procest/_round4/compare/ (PR 107)
noteznuny.org timed out twice on 2026-09-13; the documentation host answers.

GitLab CE​

version read19.3.2
familyforge issues
licenceMIT
open coreyes, by subtraction: the paid code is removed at build time, leaving 1,616 no-op seams in 1,599 files. 22 rows need EE, each settled by a 404 or 400 from the running instance
codegitlab-org/gitlab, one tree builds both editions; gitlab-org/gitlab-foss, the CE-only mirror
documentationdocumentation
APIREST API
issue trackerwork items, formerly issues
named on a comparison pageLinear, the modern alternative to Jira; Easy8, Atlassian Data Center alternatives; dev.to, OpenProject vs Jira
corpusprocest/gitlab/round4/ and procest/_round4/compare/ (PR 107)
note/-/issues redirects to /-/work_items and answers 404 to a plain fetch, 200 in a browser.

OTOBO​

version read11.0.17, the vendor image rotheross/otobo at rel-11_0_17
familyticket
licenceGPL-3.0
open coreno: six entitlement greps over Kernel/ and bin/ return nothing that matters, and the four package repositories list 45 free packages, 44 GPL-3.0 and 1 AGPL-3.0, none priced. Four core capabilities ship switched off, and with Ticket::Service at 0 an SLA is accepted and ignored
codeRotherOSS/otobo; RotherOSS/otobo-docker
documentationdocumentation index; administration manual 11.0; installation manual 11.0
APIdeveloper manual, the generic interface (to verify)
issue trackerGitHub issues
corpusprocest/otobo/round4/ and procest/_round4/compare/ (PR 108)
noteThe documentation index renders by script, so a plain fetch finds no manual links, and every developer-manual path tried under doc.otobo.org/manual/developer/11.0/ answered 404 on 2026-09-13. The API is the generic interface, driven in the corpus at nph-genericinterface.pl.

iTop Community​

version read3.2.3-2 build 20678, built from the release zip iTop-3.2.3-2-20678.zip
familyITSM and CMDB
licenceAGPL-3.0
open coreyes, as a catalogue: the zip carries no key and no gate, 1,955 PHP files carry the AGPL header, and five entitlement greps return 0 hits. The store lists 103 extensions, 70 AGPL and 33 under the Combodo Software License, none in the tree, six matrix rows behind them
codeCombodo/iTop
documentationiTop Hub wiki; administrator guide; extension store, all extensions
APIREST/JSON services
issue trackerGitHub issues; SourceForge tickets (to verify)
corpusprocest/itop/round4/ and procest/_round4/compare/ (PR 108)
noteCombodo publishes no image of its own, so the column was built from the release zip. sourceforge.net/p/itop/tickets/ answered 403 to a plain fetch on 2026-09-13.

Odoo Community​

version read19.0, the vendor's own image, the database created from the command line with the Project app and its Community neighbours
familyproject management
licenceLGPL-3.0
open coreyes, by absence with a label. The Enterprise addons live in a private repository under OEEL-1 and are not in the tree; no key, no gate and no degraded path in Community, `grep -rliE 'license.?key
codeodoo/odoo on GitHub, branch 19.0. GitHub reports the licence as NOASSERTION; the LICENSE file says LGPLv3; addons/project on 19.0; odoo/addons/base/data/ir_module_module.xml, the 21 to_buy records; addons/resource/models/resource_calendar.py, the working calendar; addons/mail/models/mail_thread.py, the reply threading
documentationProject app, 19.0; editions comparison, table renders by script (to verify)
APIExternal API, XML-RPC, 19.0
issue trackerGitHub issues, about 3,800 open
corpusprocest/odoo/round4/ and procest/_round4/compare/ (PR 110)
noteSame family as OpenProject, Plane and Redmine. Not a ticket system: Community ships no addons/helpdesk, and Helpdesk is a to_buy record. Driven in batch 6 beside Nextcloud Deck, on port 8095, torn down before Deck came up.

Nextcloud Deck​

version read1.18.4, chosen by occ app:install deck on a throwaway Nextcloud 34.0.4 of its own; source read at the tag v1.18.4
familykanban
licenceAGPL-3.0
open coreno: appinfo/info.xml says agpl, the 188 PHP files carry AGPL-3.0-or-later headers, and `grep -rniE 'licen[cs]e
codenextcloud/deck on GitHub; the tag v1.18.4; lib/Service/FilesAppService.php, the attachment as a Files node
documentationapp store listing
APIREST API, docs/API.md at v1.18.4
issue trackerGitHub issues
corpusprocest/nextcloud-deck/round4/ and procest/_round4/compare/ (PR 110)
noteThe one candidate on the same host as dossiq, driven on port 8096 and never on the shared instance. The unified search provider ids are search-deck-card-board and search-deck-comment, not deck; an upload needs data=<filename> beside type=file or answers 400 with an empty body.

OpenCase​

version read1.1.0, commit 1143dbea (2026-09-05)
familyDanish municipal case system on Nextcloud
licenceAGPL-3.0-or-later
open coreyes: the enterprise edition (AI, digital post, CPR and CVR) is a separate non-public package, gated on enterprise_version in lib/Service/Configuration.php:140 per the round 2 census
codelamotech/opencase
documentationdocs.opencase.dk; Nextcloud app store
APIno separate API reference found; the census read appinfo/routes.php (to verify)
issue trackerGitHub issues
corpusprocest/opencase/round2/ and procest/_round2/compare/
noteRepository last pushed 2026-09-12, 11 open issues.

GZAC / Valtimo​

version read13.4.1, demo Evenementenvergunning; monorepo next-minor at 51eddc25
familyDutch case and BPM platform
licenceEUPL-1.2
open corepartly: release builds pull two closed-published npm packages, @valtimo-plugins/freemarker and @valtimo-plugins/smtpmail, per the round 2 census
codevaltimo-platform/valtimo, the monorepo; valtimo-docker-compose; gzac-docker-compose
documentationdocs.valtimo.nl; docs.gzac.nl
APIno API reference page found under docs.valtimo.nl; a running backend serves its own OpenAPI (to verify)
issue trackerGitHub issues
corpusprocest/valtimo/round2/ and procest/_round2/compare/
notevaltimo-backend-libraries and valtimo-frontend-libraries are archived, last pushed 2025-10-08 and 2025-09-26. The monorepo was pushed 2026-09-11.

xxllnc Zaken (Zaaksysteem)​

version readmaster at b7354824, driven locally at the dev.zaaksysteem.nl hostname the compose file insists on
familyDutch case system
licenceEUPL-1.2
open corenot established
codegitlab.com/xxllnc/zaakgericht/zaken/start
documentationopen source wiki; community; frontend storybook; help.zaaksysteem.nl, bot wall on a plain fetch (to verify); docs.zaaksysteem.nl, 502 three times on 2026-09-13 (to verify)
APIthe census read backend/perl-api/share/apidocs in the tree; no public API site confirmed (to verify)
issue tracker/-/issues on the start project answered 404, so issues look disabled (to verify)
corpusprocest/xxllnc-zaken/round2/ and procest/_round2/compare/
notegithub.com/zaaksysteem/zaaksysteem answers 404 now; mintlab/Zaaksysteem was last pushed in 2020. The GitLab project was active on 2026-09-11.

Dimpact ZAC​

version readcommit 06b64668, tag zaakafhandelcomponent-1.0.316, image ghcr.io/infonl/zaakafhandelcomponent:latest
familyDutch case component on Open Zaak
licenceEUPL-1.2-or-later
open corenot established; nothing seen
codeinfonl/dimpact-zaakafhandelcomponent
documentationdocs in the tree, manuals included; development README
APIno API reference confirmed outside the tree (to verify)
issue trackerGitHub issues
corpusprocest/zac/round3/ on branch feat/round3-dimpact-zac, PR 100, open and unmerged on 2026-09-13. Round 1 material at procest/dimpact-zac/ on development
noteThe column is the zac key on every ledger row. It is unknown on the 19 rows round 3 added.

Kanboard​

version read1.2.54, the project's own image kanboard/kanboard, SQLite; source read at the tag v1.2.54 the image reports over getVersion
familytask
licenceMIT
open coreno: LICENSE is MIT, and licen[cs]e, subscription, premium, enterprise, feature.?flag and `paid
codekanboard/kanboard on GitHub; the tag v1.2.54; app/Action/, the fifty event-to-action classes; app/Model/TaskRecurrenceModel.php, the calendar-day arithmetic; app/Model/LinkModel.php, link labels with an opposite
documentationdocumentation
APIJSON-RPC API reference
issue trackerGitHub issues
corpusprocest/kanboard/round4/ and procest/_round4/compare/ (PR 115)
noteDriven in batch 7 beside Vikunja on port 8091, both up together because each is one container. The Docker credential helper on the host (desktop.exe) refuses a pull from a shell; an empty DOCKER_CONFIG works. moveTaskPosition needs swimlane_id or answers invalid params. An automatic action on task.create fires on the task a recurrence creates.

Vikunja​

version read2.6.0, the project's own image vikunja/vikunja, API and frontend in one Go binary, SQLite; source read at the tag v2.6.0 the image reports on /api/v1/info
familytask
licenceAGPL-3.0
open coreyes, the tenth shape, a gate that hides. pkg/license/license.go:70-74 names three features, admin_panel, time_tracking and audit_logs; RequireFeature (pkg/routes/feature_gate.go:24) serves 404 for them "so gated routes are indistinguishable from unregistered ones"; licenseFeatureForRoute hides them from the token scope list, the audit listener drops events, the instance-admin flag is inert and the CLI refuses to set it. With a key, pkg/license/check.go:57-66 posts the key, the version, the database type, the counts of active, disabled and pending users, the host OS and a container flag to console.vikunja.io daily; without one nothing calls out. The free install creates license_status and time_entries. Verified live: enabled_pro_features: [], four gated routes 404, /admin "Not found"
codego-vikunja/vikunja on GitHub; the tag v2.6.0; pkg/license/license.go, the three features and the comment to whoever reads it; pkg/routes/feature_gate.go, the 404; pkg/models/task_relation.go, eleven kinds and the inverse; pkg/models/project_access.go, the recursive access query
documentationdocumentation
APISwagger 2 for v1, on any instance at /api/v1/docs.json; OpenAPI 3 for v2 at /api/v2/openapi.json
issue trackerGitHub issues
named on a comparison pagedev.to, OpenProject vs Jira
corpusprocest/vikunja/round4/ and procest/_round4/compare/ (PR 115)
notekolaente.dev/vikunja/vikunja asks for a sign-in; GitHub is the public copy. Driven in batch 7 beside Kanboard on port 8092. Every registered user gets an Inbox that takes the next project id, so probe the project you made, not project 2. A task POST and the user settings POST are full replaces. The image runs as uid 1000 and a fresh volume is root's; the log names the fix.

Request Tracker​

version read5.0.10, from netsandbox/request-tracker:5.0, which builds the vendor's signed tarball, on port 8097; no vendor image exists. Source read at the 5.0.10 tree the container reports
familyticket
licenceGPL-2.0
open coreno: nothing withheld. COPYING is the GPL version 2 and every file carries Best Practical's tagged block; six entitlement greps over lib share/html etc hit ten files, every one the GPL header, a dashboard subscription or the vendor's address. No option hides a feature for money, and assets, articles and approvals sit behind rights like every other screen. Nothing phones home: a headless run through five pages made requests to localhost only. The vendor publishes its own extensions on CPAN under the same licence
codebestpractical/rt
documentationdocumentation, resolves to 6.0.3
APIREST2
issue trackerGitHub issues
corpusprocest/request-tracker/round4/ (M1-column.md, lifecycles-and-scrips.md, journeys.md, open-core.md, install.md) and procest/_round4/compare/ (PR 120)
noteDriven in batch 9 beside Frappe Helpdesk, sequentially, each torn down before the next. issues.bestpractical.com redirects to a login page, so GitHub is the tracker read. The column rests on lib/RT/SLA.pm, lib/RT/Lifecycle.pm, lib/RT/Ticket.pm and etc/RT_Config.pm.in. Two traps a buyer will meet: every queue ships SLADisabled 1, so the SLA scrips set nothing until it is cleared, and a configuration saved through the editor reached one of five web workers until a restart.

Frappe Helpdesk​

version read1.30.1 on Frappe 15.120.1, built from the vendor's own docker/ recipe with the versions pinned, one bench build of twenty minutes, on ports 8095 and 8096; no published Helpdesk image exists
familyticket
licenceAGPL-3.0
open coreno: nothing withheld. Helpdesk and the framework under it are AGPL-3 (helpdesk/LICENSE, hooks.py, frappe/LICENSE), and `licen[cs]e.?key
codefrappe/helpdesk on GitHub; frappe/frappe, the framework the column counts a third of its cells against
documentationHelpdesk documentation; Frappe Framework documentation
APIthe framework REST API, which is what Helpdesk exposes
issue trackerGitHub issues
corpusprocest/frappe-helpdesk/round4/ (M1-column.md, journeys.md, open-core.md, install.md, the SLA probes) and procest/_round4/compare/ (PR 120)
noteDriven in batch 9 beside Request Tracker; the first build died with the host's Docker daemon and was rebuilt. The column rests on hd_service_level_agreement.py, hd_service_holiday_list.py, hd_ticket.py and the framework's workflow, webhook and user_permission doctypes. Three traps a buyer will meet: a fresh site has no time_zone and the framework counts in Asia/Kolkata until one is set, the browser fetches the vendor's telemetry client from pulse.m.frappe.cloud on every page with telemetry off, and search answers 500 until the scheduled index job has run.

Gitea​

version read1.27.3, one container on SQLite at localhost:8091; source census against a shallow clone at tag v1.27.3, commit 146cc3ee, the release the container ran
familyforge issues
licenceMIT, on 3,010 of 3,013 Go files
open coreno, nothing gated, and it is still a shape. Every open-core grep returns zero across .go, .tmpl, .ini, .ts and .vue: the single enterprise hit is a comment at modules/setting/ui.go:172, and the eighteen subscription hits are the repository watch API. Gitea Ltd sells Gitea Enterprise and Gitea Cloud, and the open tree holds no trace of either, which is the twelfth shape: the steward of the open core sells a closed product built on it
codego-gitea/gitea
documentationdocumentation
APIAPI reference
issue trackerGitHub issues
corpusprocest/gitea/round4/ (M1-column.md, gitea-vs-forgejo.md, open-core.md, code-census.md, screenshots/) and procest/_round4/compare/ (PR 124)
noteDriven in batch 11 and not in the ledger's sources register yet; this entry is from procest/gitea/round4/README.md. It answers all 206 rows exactly as Forgejo does, so the interesting file is the divergence table rather than the column. Three API endpoints write issue.due_date and store three instants for one date.

Taiga​

version read6.10.2, the official nine-container taiga-docker stack at localhost:8093; source census against a clone of taiga-back at commit eb0803da, byte-identical to the running build on the spot-checked files
familyagile project management
licenceMPL-2.0, on all 931 Python files
open coreno, and not a shape: every open-core grep returns zero, and Kaleidos sells hosting of this same code. What a buyer meets instead is telemetry, on by default: a persistent instance UUID, the version, the instance's own URL and 46 measured properties to https://telemetry.taiga.io/ every night, ENABLE_TELEMETRY = True read back from the running instance
codetaigaio/taiga-back
documentationdocumentation
APIREST API
issue trackerGitHub issues; tree.taiga.io
corpusprocest/taiga/round4/ (M1-column.md, agile-objects.md, open-core.md, screenshots/) and procest/_round4/compare/ (PR 124)
noteDriven in batch 11 and not in the ledger's sources register yet; this entry is from procest/taiga/round4/README.md. The licence is MPL-2.0, not the AGPL-3.0 the candidate table claimed from a vendor page. AUTH_PASSWORD_VALIDATORS read back from the running instance is empty, and 123456 was accepted on the superuser's own account.

Tuleap Community Edition​

version read17.5.99.1774534150, the project's own image tuleap/tuleap-community-edition:latest on Rocky Linux 9.7, at https://localhost:8091 with MySQL 8.0. The tree was copied out of /usr/share/tuleap in the running container, because there is no public repository any more
familyALM suite: tracker, documents, code and test management
licenceGPL-2.0
open coreyes, the thirteenth shape: the open edition ships the whole lock and none of the key. Twenty files under src/common/SeatManagement/ verify an Ed25519-signed licence, bind its audience claim to the SHA-256 of this instance's own hostname, and decide the edition on whether a keys directory exists. It does not, so every screen brands the product a Dev Build. The tree carries the sentence the paid edition shows at expiry, "All accounts will be in read only mode in %d days", and not the code that would do it. Nineteen plugins the vendor marks part of Tuleap Enterprise are absent from the 35 in the image, against two dangling listeners in 130
codegithub.com/Enalean/tuleap answers 404 and is not in the organisation's repository list (gone); tuleap.net/plugins/git/tuleap/tuleap/stable answers 403 to an anonymous client (gone)
documentationdocumentation; the plugin installation page, which marks nineteen plugins "part of Tuleap Entreprise"
APIthe instance serves its own REST explorer at /api/explorer; no public API reference page
issue trackerRequests tracker on tuleap.net
corpusprocest/tuleap/round4/ (usability.md, install.md, code-census.md, menu-tree.md, journeys.md, workflow.md, open-core.md, M1-column.md, screenshots/) and procest/_round4/compare/ (PR 127)
noteDriven in batch 12 and not in the ledger's sources register yet; this entry is from procest/tuleap/round4/README.md. The two dead links are the evidence and not broken references. On 2026-09-13 tuleap.net announced that "Tuleap Community Edition development and releases are no longer public", with 30 September as the last day to download what is left, so this is the first column in the corpus a reader cannot check with a browser.

Huly​

version readv0.7.426, the vendor's own hcengineering/huly-selfhost compose at commit 8655845, fourteen containers, at http://localhost:8092. The clone was moved back from develop to the tag, because develop is two months ahead of the image
familyissue tracker and workspace
licenceEPL-2.0, seven LICENSE files, no second licence
open coreno gate of any kind, and still the fourteenth shape. Zero hits for a licence key, an entitlement or a feature flag, one repository, one public develop branch. What is withheld is not withheld at all, it is un-deployed: of the 22 directories under services/ the vendor's own self-host compose runs one, and of the 14 under pods/ it runs six. Mail, calendar, signing, printing, export, backup, GitHub, Telegram, the AI bot and the process worker are absent, and the app rail still offers Processes, Calendar and Office with nothing behind them
codehcengineering/platform; hcengineering/huly-selfhost, the compose this column ran
documentationdocumentation
APIdocs.huly.io/api/ answers 404; an examples repository exists (to verify)
issue trackerGitHub issues
corpusprocest/huly/round4/ (usability.md, install.md, code-census.md, menu-tree.md, journeys.md, process-engine.md, open-core.md, M1-column.md, screenshots/) and procest/_round4/compare/ (PR 127)
noteDriven in batch 12 and not in the ledger's sources register yet; this entry is from procest/huly/round4/README.md. It has the best type editor in the corpus, attached to Cards rather than to the Tracker where the issues live. It reads inside uploaded files, measured with a control word, and cannot see its own PublicHoliday calendar.

Documented, not driven​

Jira Service Management​

version readCloud, read 2026-09-13; Data Center 11.3 where Cloud and DC differ. Not driven: no account, no instance, no screenshot
familyITSM
licenceproprietary
open coreyes, by plan: the ninth shape. The paid half is a column in a plan table; there is no code to read, every capability is in every tenant's build, and the plan decides whether it renders. The column rates Standard, and eleven rows move by plan: custom objects, the customer record, skill routing, playbooks, the audit log, staff SSO, enforced two-factor, analytics, retention, the holiday import and S3. The boundary moves by date without a version: incident, change and problem management moved to Premium on 2024-10-16. Counted by script, 16 cells name Premium, 8 Enterprise, 5 Atlassian Guard and 2 Data Center. Read in procest/jira-service-management/round4/open-core.md
codeclosed source
documentationSet up SLA calendars; Categorize customer requests into request types; Create and edit SLA calendars, Data Center, last modified 2024-03-19; 108 URLs in this group, every one listed in procest/jira-service-management/round4/sources.md
APIRequest, the servicedeskapi group whose 72 operations hold no calendar resource; Customer, with the portal-only account; Jira Service Management Data Center REST API 11.3; 8 URLs in this group, every one listed in procest/jira-service-management/round4/sources.md
issue trackerJSDCLOUD-4685, merge, 1,237 votes, Future Consideration; JRACLOUD-69298, field-level security, 585 votes; JSDCLOUD-194, SLA reset, fixed 2026-04-02 after 640 votes; 10 URLs in this group, every one listed in procest/jira-service-management/round4/sources.md
named on a comparison pageALVAO, Jira Service Management alternatives
corpusprocest/jira-service-management/round4/ (M1-column.md, open-core.md, sources.md with 136 URLs in seven groups) and procest/_round4/compare/ (PR 113)
noteDocumented in batch 8, graded documented, not driven; a driven column replaces this one if a licence and a clock are ever spent. The Cloud pricing page renamed the product Service Collection in 2026; the documentation, the API and Data Center still say Jira Service Management.

YouTrack​

version readServer 2026.2, help pages dated July 2026 in their footers, read 2026-09-13; Cloud where the price pages differ. Not driven: no account, no instance, no screenshot
familyissue
licenceproprietary
open coreno: "The full feature set, support, and AI Assistance continue to be included at no additional cost". Ten users and three agents free with everything on, reporters unlimited and free; the one boundary is historical, the user-pack plans that cannot create helpdesk projects and closed to renewal on 2025-10-01. Shape one, closed: what a buyer does not get is the source, which the shapes do not measure. Read in procest/youtrack/round4/open-core.md
codeclosed source
documentationSLA policies, the whole calendar in three settings; Helpdesk projects; Show version history, the comment rollback; 125 URLs in this group, every one listed in procest/youtrack/round4/sources.md
APIIssues, POST /api/issues with its documented refusals; Commands, the same grammar as the dialog and the commit message; REST API URL and endpoints; 32 URLs in this group, every one listed in procest/youtrack/round4/sources.md
issue trackerJT-95867, SLA calendars, Collecting feedback, 3 votes; JT-62660, search inside attachments, Collecting feedback, 14 votes; JT-67234; 4 URLs in this group, every one listed in procest/youtrack/round4/sources.md
named on a comparison pageEasy8, Atlassian Data Center alternatives
corpusprocest/youtrack/round4/ (M1-column.md, open-core.md, sources.md with 171 URLs in seven groups) and procest/_round4/compare/ (PR 113)
noteDocumented in batch 8, graded documented, not driven; a driven column replaces this one if a licence and a clock are ever spent. The first closed product to score yes on pending 11.27, and the first system in the corpus with no holiday calendar at all.

Jira Software Data Center​

version read11.3, read 2026-09-13 from the Data Center documentation and the REST reference 11.0.1. Not driven: closed source, no licence, no instance, and since 2026-03-30 not for sale to a new customer
familyissue
licenceproprietary
open coreno, above the user tier: shape one, closed, with a boundary in time the shapes do not measure. "Upgrading from 500 users to 1,000 users will result in a total of 1,000 users, not 1,500 users" is the whole licence, and every capability is in every tier. The boundary went into the product line, where the portal, the customer, the SLA engine and the queue are Jira Service Management Data Center under a second licence, 18 of the 206 cells, and into the calendar: "Mar 30, 2026 End of license sales to new customers" and "Mar 28, 2029 End of life of Data Center products", on which day the apps go read-only. Read in procest/jira-data-center/round4/open-core.md
codeclosed source
documentationConfiguring working days, the board setting that no due date reads; Using the issue collector, the form embedded on somebody else's website; Archiving an issue, hidden and preserved; 154 URLs in this group, every one listed in procest/jira-data-center/round4/sources.md
APIIssue, with POST /api/2/issue and its documented 201 and 400; Configuration, whose TimeTrackingConfigurationBean is the only calendar-shaped setting on the reference; Webhooks, with the secret token; 13 URLs in this group
issue trackerJRASERVER-12400, comment history, closed Won't Do with 759 votes; JRASERVER-22506, working days in JQL, Gathering Interest, 560 votes, open since 2010; JRASERVER-3592, merge, Future Consideration, 533 votes; 20 URLs in this group
named on a comparison pageLinear, the modern alternative to Jira; Easy8, Atlassian Data Center alternatives; ALVAO, Jira Service Management alternatives; dev.to, OpenProject vs Jira
corpusprocest/jira-data-center/round4/ (M1-column.md, open-core.md, sources.md with 199 URLs in seven groups) and procest/_round4/compare/ (PR 119)
noteDocumented in batch 10, graded documented, not driven. A driven column cannot replace this one, because the edition stopped being sold on 2026-03-30. Every quote in both ratings files was checked against the fetched page by _round4/tools/quote-check.py and every URL by link-check.py.

Easy Redmine (Easy8)​

version read16.0, read 2026-09-13 from easy8.com. Not driven: the paid half is a source tree only a paying on-premises customer receives, and there is no public tracker to check a no against
familyissue and project
licenceGPL-2.0 core, ESCLv2.0 layer
open coreyes, the eleventh shape: a source-available proprietary layer on a GPL core, sold as open source. The core is Redmine, GPL-2.0 and complete. Everything Easy wrote is a separate tree under the Easy8 Commercial License, defined as all software "not created nor derived from the GNU/GPL2 licensed software (including Redmine)". The buyer on a server "is entitled to download the source code of the Elements"; the buyer in the cloud "has no right to obtain the source code to the Elements, nor to view it"; neither may pass it on, and a modification "shall, however, always be subject to a notification to the Licensor". GitHub holds the plugin platform (rys, GPL-2.0) and none of the feature plugins. Inside that tree a plan table decides what runs: the HelpDesk and its SLA on Platform, formulas and SSO on Business, the CRM, Assets, Knowledge Base and branding as priced add-ons; 22 matrix cells name Platform and 9 an add-on. Read in procest/easy-redmine/round4/open-core.md
codesource available to the paying on-premises buyer only, and not to be passed on; easysoftware/rys on GitHub, the plugin platform, GPL-2.0 and no feature plugin
documentationWorking time calendar, with holidays imported from a country ICS feed; HelpDesk, whose every SLA row is the Platform plan; Archiving and unarchiving projects, a project and never a ticket; 134 URLs in this group, every one listed in procest/easy-redmine/round4/sources.md
APIEasy Project API 3.9.0, on the api. host because SwaggerHub answers 404 to anything but a browser; GraphQL; the Redmine REST-like API
issue trackerno public tracker; the group is empty by finding, not by omission, and it is the second reason to read the column as a ceiling
named on a comparison pageEasy8, Atlassian Data Center alternatives
corpusprocest/easy-redmine/round4/ (M1-column.md, open-core.md, sources.md with 158 URLs in seven groups) and procest/_round4/compare/ (PR 119)
noteDocumented in batch 10, graded documented, not driven; a driven column would need a paid licence, because the paid half is not public. easyredmine.com redirects to easy8.com. quote-check.py found twelve loose fragments in 291 and sent eleven cells back to the page they cite.

Trial: self-hostable under a paid or time-limited licence​

ManageEngine ServiceDesk Plus​

version readnot driven
familyITSM
licenceproprietary
open corenot applicable
codeclosed source
documentationadmin guide; product page
APIv3 API; the page title says Cloud, check which edition it documents (to verify)
issue trackerno public tracker
named on a comparison pageALVAO, Jira Service Management alternatives
corpusnone
noteMoved from docs only to trial: an on-premises edition can be installed under licence.

Docs only: cloud only, landscape not evidence​

Linear​

version readcannot be driven
familyissue
licenceproprietary
open corenot applicable
codeclosed source
documentationdocumentation
APIdevelopers; API and webhooks
issue trackerno public tracker
named on a comparison pageLinear, the modern alternative to Jira; Easy8, Atlassian Data Center alternatives; dev.to, OpenProject vs Jira
corpusnone
notedevelopers.linear.app redirects to linear.app/developers.

GitHub Issues​

version readcannot be driven as a service
familyforge issues
licenceproprietary
open corenot applicable
codeclosed source
documentationissues documentation; Enterprise Server 3.16 admin documentation
APIREST API, issues
issue trackerpublic roadmap; community discussions
named on a comparison pageLinear, the modern alternative to Jira; dev.to, OpenProject vs Jira
corpusnone
noteEnterprise Server would move it to trial.

TOPdesk​

version readcannot be driven
familyITSM
licenceproprietary
open corenot applicable
codeclosed source
documentationSaaS documentation; product page
APIdevelopers
issue trackerno public tracker
named on a comparison pageALVAO, Jira Service Management alternatives
corpusnone

Zendesk​

version readcannot be driven
familyticket
licenceproprietary
open corenot applicable
codeclosed source
documentationhelp centre
APIAPI reference
issue trackerno public tracker
named on a comparison pageLinear, the modern alternative to Jira
corpusnone

Freshservice​

version readcannot be driven
familyITSM
licenceproprietary
open corenot applicable
codeclosed source
documentationsupport portal
APIAPI
issue trackerno public tracker
named on a comparison pageALVAO, Jira Service Management alternatives
corpusnone

HaloITSM​

version readcannot be driven
familyITSM
licenceproprietary
open corenot applicable
codeclosed source
documentationguides; product page
APIAPI documentation
issue trackerno public tracker
corpusnone
noteNone of the four comparison pages named it in a plain fetch.

InvGate​

version readcannot be driven
familyITSM
licenceproprietary
open corenot applicable
codeclosed source
documentationproduct page; docs.invgate.com answered 503 on 2026-09-13 (to verify)
APIno API reference found (to verify)
issue trackerno public tracker
named on a comparison pageALVAO, Jira Service Management alternatives
corpusnone

TeamDynamix​

version readcannot be driven
familyITSM
licenceproprietary
open corenot applicable
codeclosed source
documentationproduct page; documentation site not found (to verify)
APIWeb API, Swagger
issue trackerno public tracker
named on a comparison pageALVAO, Jira Service Management alternatives
corpusnone

ALVAO​

version readcannot be driven
familyITSM
licenceproprietary
open corenot applicable
codeclosed source
documentationdoc.alvao.com; product page
APIno API reference found (to verify)
issue trackerno public tracker
named on a comparison pageALVAO, Jira Service Management alternatives
corpusnone
notePublishes one of the four comparison pages.

ServiceNow​

version readcannot be driven
familyITSM
licenceproprietary
open corenot applicable
codeclosed source
documentationdocumentation
APIdeveloper portal
issue trackerno public tracker
corpusnone
notewww.servicenow.com refused a plain fetch; the documentation host answers. None of the four comparison pages named it in a plain fetch.

The comparison pages that seeded the candidate set​

Four vendor or community comparison pages were read to find candidates the rounds had not named. The last column counts how often each product is named on the page.

keypageproducts named
LLinear, the modern alternative to JiraJira 14, GitHub 14, Zendesk 3, GitLab 3, Notion 2
EEasy8, Atlassian Data Center alternativesJira 113, Linear 21, GitLab 5, OpenProject 2, YouTrack 1, Tuleap 1, Redmine 1, Plane 1, Asana 1
AALVAO, Jira Service Management alternativesJira 14, Azure DevOps 2, TeamDynamix 1, TOPdesk 1, ManageEngine 1, InvGate 1, Freshservice 1
Ddev.to, OpenProject vs JiraOpenProject 41, Jira 40, Linear 7, GitHub 3, Vikunja 1, Taiga 1, Plane 1, GitLab 1

Where the corpus files are​

whatpath
the ledger, source of recordprocest/_ledger/parity-ledger.html, with procest/_ledger/README.md on how to work with it
the 206-row matrix, four Dutch columnsprocest/_round2/compare/M1-functionality.md
round 3, GLPI and Zammad, and the 21 proposalsprocest/_round3/compare/
round 4, batches 1 to 12, the tallies and the enginesprocest/_round4/compare/, index in its README.md
the counting and ranking scriptsprocest/_round4/tools/corpus-tally.py, count-column.py, render-column.py, render-extra.py
the gap registerprocest/_gaps/README.md, gap-register.md, gap-register.json, ownership-rules.md