# ClickUp Alternatives: Validation Synthesis and Pilot Shortlist

## Decision at a glance

This synthesis reduces the validated deep dives to a shortlist for a small team seeking an alternative to ClickUp. It gives greatest weight to **true self-hosted open-source availability**, no mandatory recurring per-user Community licence, credible multi-user work management, a usable knowledge surface, and an operating model a small team can own. The labels are triage decisions, not claims of full ClickUp parity.

**OpenProject Community Edition is the top pilot.** It is the only contender that combines a GPLv3 unlimited-user Community edition with verified work packages, hierarchy, Kanban, calendar, Gantt and multi-project timelines, a versioned Markdown-based wiki, role permissions, API/webhooks, and a documented operating model. Its work-package/query model is not a literal ClickUp Space/Folder/List substitute, and its Documents module has no version history; the pilot must prove migration, mobile use, and knowledge-workflow fit.[1] [2] [3]

**The conditional-pilot group contains credible alternatives with a specific trade-off rather than a clean win.** Leantime is the closest all-in-one project/wiki option but places program roadmaps and several parity features behind proprietary plugins. Plane is a modern project tool but reserves workspace Wiki and several planning/governance features for paid tiers. Huly has the strongest collaborative Docs experience in the group but carries a heavy, immature self-hosted stack and lacks verified stable table/calendar/Gantt coverage. Taiga is excellent for agile execution but lacks verified planning views. The split stacks trade integration and operational simplicity for a stronger documentation surface.[4] [5] [6] [7]

The **reference-only** candidates are useful baselines for engineering or managed-cloud preferences, but conflict with the self-hosted, fully open-source, no-recurring-seat-cost direction. The **exclude** group contains hard licensing, access-control, capacity, or core-product-fit blockers. A hands-on proof of concept remains mandatory before production selection because several important claims are unverified, plan-gated, or materially dependent on the team’s data and operating practices.

> **Interpretation rule:** “Not verified” means the validated material did not establish the capability. It does not prove that a feature is absent. “Paid gate” means the cited evaluation identified it outside the relevant free/community entitlement.

## Decision criteria and reading key

The comparison assesses seven ClickUp-replacement dimensions. **Tasks/issues** covers work-item structure, comments, hierarchy, dependencies, and planning objects. **Views** covers Kanban and other requested operational views. **Roadmap** means a planning timeline, Gantt, or roadmap and does not imply dependency-aware critical-path planning unless stated. **Knowledge** covers rich documentation, Markdown interoperability, history, and collaborative editing. **Permissions** refers to multi-user role/access controls, not only the ability to invite users. **Cost** distinguishes product licence from infrastructure and operator time. **Operational burden** assumes a production-quality deployment with TLS, backup/restore testing, patching, monitoring, and access administration.

| Group | Candidate | Decision rationale | Decision condition |
|---|---|---|---|
| **Top pilot** | OpenProject Community Edition | Broadest verified GPLv3 Community coverage across work management, roadmap, wiki, permissions, and integrations. | Pass representative migration, Wiki/Docs workflow, mobile, and restore tests. |
| **Conditional pilot** | Leantime | Strong project-level execution and rich wiki; portfolio roadmap and several parity features require proprietary plugins. | Accept self-hosting and plugin/feature boundary; prove Markdown workflow. |
|  | Plane Community Edition | Strong modern work-item views and project Pages; workspace Wiki, advanced planning, and granular controls are paid. | Accept separate Markdown-first wiki or prove Pages are sufficient. |
|  | Huly self-hosted | Rich collaborative Docs and tracker, with ClickUp CSV import; stable planning-view and production-stack gaps remain. | Prove backups, recovery, operational stability, and replacement for missing views. |
|  | YouTrack Server Free | Mature issues, Gantt, Knowledge Base, permissions, and ClickUp importer. | Only if proprietary binary and 10 User/3 Agent cap are acceptable. |
|  | Taiga self-hosted | Excellent agile/Kanban/Scrum core and project wiki. | Only if calendar, Gantt, roadmap, and schedule timeline are not minimum requirements. |
|  | Vikunja plus Docmost | Strong open-source split stack: task views/Gantt plus rich collaborative docs. | Prove two-system identity, linking, search, migration, and recovery workflow. |
|  | Forgejo plus Docmost | Good code-centric issues plus excellent documentation portability. | Only if absence of free task Table/Calendar/Roadmap/Timeline/Gantt is acceptable. |
|  | Nextcloud Deck plus Collectives | Cohesive AGPL task/file/wiki layer with strong Markdown wiki and Deck Gantt. | Only if Kanban + Gantt can replace first-class task List/Table and deep hierarchy. |
| **Reference only** | GitLab Self-Managed Free | Strong engineering tracker and Git/Markdown wiki, but views/roadmap gaps, open-core licensing, and high operations weaken fit. | Consider only for GitLab-centred engineering workflows. |
|  | GitHub Projects plus Issues and docs/wiki | Strong cloud engineering workflow and Markdown portability; not self-hosted/open-source and private wiki requires paid cloud. | Consider only when managed GitHub and its pricing model are acceptable. |
|  | Notion Free | Excellent editor/database surface but proprietary SaaS with an unsustainable multi-owner Free cap. | Use only for a small, short cloud pilot. |
| **Exclude** | AFFiNE Community Edition | Current backend production licensing requires commercial authorization; task/issue fit is incomplete. | Reconsider only after written, version-specific licence clarification and work-management validation. |
|  | Jira Free plus Confluence Free | Proprietary cloud-only; Free permissions are unsuitable for normal multi-role use. | Reconsider only as a trusted ≤10-user cloud exception. |
|  | Linear Free | Proprietary SaaS and Free makes every member an Admin, with capacity limits. | No current fit for the stated direction. |
|  | AppFlowy current self-hosted offering | Supported multi-user server is commercial; Free self-host is one seat plus guests. | No current fit for a free, open-source multi-user deployment. |

## Top pilot

### OpenProject Community Edition

OpenProject Community Edition should run the first pilot. The GPLv3 Community edition is free for unlimited users and projects, subject to self-hosting rather than a free SaaS allowance. It verifies configurable work packages for tasks/issues, project and parent-child hierarchy, saved filtered list/table-like views, status-driven Kanban, calendar with iCalendar subscription, interactive Gantt and multi-project timelines, plus a version/release-oriented roadmap. This is the most complete verified operational-view set among candidates meeting the open-source and no-seat-fee baseline.[1] [2] [8] [9]

Its knowledge fit is substantial but needs a precise expectation. The project Wiki uses GFM with rich editing, tables, images, macros, internal embeds, history/diffs, locking, and Markdown export. The separate real-time Documents module does not have versioning. Manual Markdown transfer has image limitations, and lossless round-trip, Docs Markdown import/export, arbitrary external embeds, and some mobile capabilities remain unverified. Treat the Wiki as the primary knowledge candidate rather than assuming it is a ClickUp Docs clone.[3] [10]

The operating model is moderate and material: official guidance calls for Linux/container capability, PostgreSQL, TLS, secrets, email, backups of database/config/attachments, restore tests, patching, monitoring, and infrastructure-level security controls. OpenProject supplies application health checks, Prometheus export, and logs, but the team owns host, network, and file-integrity security. The POC should also prove migration because no first-party ClickUp importer was identified; test real hierarchy, comments, attachments, custom fields, and wiki images rather than only sample CSV rows.[11] [12]

| Dimension | Validated position | Pilot acceptance test |
|---|---|---|
| Tasks/issues | Configurable work packages, project/work-package hierarchy, roles, search, API/webhooks, and GitHub linkage are verified. | Map a representative ClickUp hierarchy, custom fields, comments, dates, attachments, and dependencies. |
| Kanban/views | Saved filtered table/list-like views, Kanban, calendar, and Gantt/multi-project timelines are verified. | Reproduce the team’s three busiest operational views and validate saved-query ergonomics. |
| Roadmap | Version/release-oriented roadmap and multi-project Gantt/timelines are verified; paid portfolios/resource management are outside Community. | Create a cross-project plan with dependencies and confirm the planning level is sufficient. |
| Rich knowledge/docs | GFM Wiki has history/diffs and Markdown export; real-time Documents lack versioning. | Import/export a representative document set, including images and tables; test Wiki vs Documents authoring. |
| Permissions | Role permissions are available; advanced paid gates include OIDC/SAML and some sharing/governance options. | Validate least-privilege roles, external access expectations, and authentication requirements. |
| Licensing/cost | GPLv3, unlimited users/projects, no Community seat fee. Infrastructure and operation remain costs. | Confirm operational budget and required paid gates are out of scope. |
| Operational burden | Moderate, self-hosted PostgreSQL/container administration. | Complete off-host backup/restore and upgrade rehearsal under the team’s ownership. |

## Conditional pilot candidates

### Leantime

Leantime offers a genuine AGPLv3 core with no mandatory recurring Community seat fee and a strong project-level model: To-Dos, parent/subtask hierarchy, dependencies, Kanban, Table, List, Calendar, milestones, sprints/backlog, and project-level Gantt/timeline. Its project wiki is rich, with hierarchical articles, tables, images, embeds, Mermaid, math, task lists, comments, mentions, activity, and project-scoped permissions. Cross-project program roadmaps, custom fields, recurrence, whiteboards, and MCP rely on proprietary, user-tiered plugins. The key POC gate is knowledge portability: source evidence establishes HTML persistence and audit activity, not canonical Markdown, lossless Markdown round trip, global wiki search, per-page ACLs, or restorable document-version history.[4] [13] [14]

Its Docker/PHP deployment requires persistent DB/file/config/plugin storage, cron, SMTP, TLS, backups, upgrades, and monitoring. The documented security-policy version wording is stale relative to the observed release, while releases include regression fixes; pin releases, stage upgrades, and ask the vendor to clarify API/SSO Community entitlements in the selected release. Hosted Pro pricing does not change the Community core assessment, but it confirms there is no free cloud fallback.[4] [15]

### Plane Community Edition

Plane CE is an AGPLv3 self-hosted project-management candidate with no stated user limit or per-seat fee. It verifies work items, parent/child sub-work items, cycles, modules, comments, history, attachments, List, Board/Kanban, Calendar, Table, and Timeline. Its project Pages support rich blocks, tables, code, images, lists, Markdown shortcuts, and Copy Markdown. The limitation is structural: workspace Wiki is Pro, while Free/CE material excludes real-time collaboration, versions, exports, enhanced search, work-item embeds, and Page comments. Generic Pages documentation describes some of those features, creating an explicit entitlement conflict; do not credit them to CE until the vendor or a deployed CE instance proves them.[5] [16] [17]

Plane’s timeline lacks Community dependency/critical-path planning, while initiatives, milestones, custom item types/properties, private views, advanced governance, and custom/granular roles are paid gates. It also has no verified native ClickUp importer in CE and no officially supported CE mobile app. A technically capable team can run the multi-service stack, but the documented setup and ongoing operation are non-trivial. Pilot only if a project-scoped Pages model plus a separate Markdown-first wiki meets the knowledge requirement.[5] [18]

### Huly self-hosted

Huly’s tracker verifies projects, issues/sub-issues, milestones, assignments, priorities, estimates, dates, attachments, comments, List, Kanban, filtering, and search. Its Docs surface is unusually strong: nested teamspace documents, live cursor editing, tables, images, code, Mermaid, drawing boards, backlinks, action items, comments, and space privacy. It also has an official ClickUp CSV importer and a Markdown/YAML Unified Import Format. Markdown syntax and bulk import are documented, but ordinary raw `.md` document import/export, lossless Markdown round-trip, general iframe/web embeds, and normal Docs revision diffs/rollback are not established.[6] [19] [20]

The POC must not assume a full ClickUp planning replacement. Tracker Table/grid, project month calendar, and a stable released Gantt are unverified; a comprehensive Gantt landed on develop after the cited latest production release. The official self-host distribution is a 14-service stack. The supplied CockroachDB/Redpanda configuration is explicitly not guaranteed production-ready, and default backup can omit blobs above 5 MB. Treat off-host, full-content backup/restore and a failure drill as hard gates, not documentation exercises.[6] [21]

### YouTrack Server Free

YouTrack offers strong verified issue management: parent/subtask hierarchy, table/list/tree views, Kanban/Scrum boards, a dashboard Due Date Calendar, and interactive Gantt with dependencies and resource constraints. Its project Knowledge Base supports WYSIWYG and CommonMark-plus Markdown, tables, selected embeds, live issue lists, Mermaid, comments, revisions/diffs/restore, and Markdown export. Granular issue/article/project permissions and a broad ClickUp importer are verified. The importer still omits issue history, article comments/history, Teams, and some custom fields, so migrated access roles and content need review.[22] [23] [24]

The conditional label is driven by a hard licensing caveat, not product weakness. The self-managed server binary is proprietary and free only for up to 10 Users and 3 Agents. It is not forkable or OSI-approved open source. It should be a pilot only if the team deliberately relaxes the true-open-source condition and confirms that both account categories and future scale fit. Calendar is proven as a dashboard due-date widget, not a first-class project Calendar, and a native Timeline was not established. Docker deployment is operationally moderate and still needs storage, TLS, backups, restore tests, staged migrations, and support ownership.[22] [25]

### Taiga self-hosted

Taiga’s mixed AGPL/MPL open-source stack provides a strong agile core: Epics, user stories/Kanban cards, tasks, parallel Issues, Scrum backlog/sprints/taskboard, configurable workflows, custom fields, roles, audit/history, REST API, webhooks, and repository/chat integrations. Its project Wiki offers Markdown or rich HTML authoring, tables, images, code, attachments, links, watchers, comments, and history. A team-operated self-hosted instance carries no recurring Taiga per-user licence fee in the validated material.[7] [26] [27]

This is a conditional, agile-first choice because the sources did not verify Calendar, Gantt, roadmap, or schedule Timeline. The documented timeline is activity/audit history, not planning. Markdown import/export, general embeds, real-time coediting, per-page wiki ACLs, full-body document-search quality, and a first-party ClickUp importer are also unverified. Its nine-service deployment requires PostgreSQL, RabbitMQ, media persistence, secure TLS/WSS and SMTP configuration, off-host database/media backups, restore drills, image pinning, and tested upgrades.[7] [28]

### Vikunja plus Docmost

Vikunja plus Docmost is the strongest free split-stack option for teams that value both task coverage and a serious document system. Both cores are AGPLv3. Vikunja provides shared projects/teams, nested projects, tasks, assignees, comments, attachments, dependencies, List, Table, Kanban, Gantt, search, CalDAV, API, and signed webhooks. Its Gantt is a credible roadmap substitute. Docmost Community provides real-time rich pages, nested pages, comments, history/restore, rich tables, embeds, attachments, diagrams, Markdown shortcuts/paste conversion, Markdown/HTML import/export, and full-text search.[29] [30] [31]

The product boundary is the risk. No native Vikunja–Docmost bridge, unified search, unified permissions, identity plane, or automatic cross-linking was verified. Vikunja has no verified native Calendar or distinct Timeline, and CalDAV is an integration rather than a documented calendar UI. Docmost Community excludes Bases/Kanban, API, page-level restrictions, SSO/MFA, templates, and attachment-content search. Also, the validated material did not find a dedicated Docmost backup/restore runbook and Vikunja webhooks have no retry. The pilot must test cross-app workflow, off-host restore for both systems, and reconciliation after a webhook failure.[29] [30]

### Forgejo plus Docmost

Forgejo plus Docmost is a code-centric alternative. Forgejo supplies GPLv3-or-later issues with assignees, labels, milestones, dependencies, time tracking, filtered lists, Kanban Projects, repository/team permissions, APIs, webhooks, and Git-backed Markdown wikis. Docmost adds a strong rich-doc surface with real-time collaboration, nested spaces/pages, tables, generic/named embeds, inline comments, history/diff/restore, search, diagrams, and Markdown/HTML import/export.[32] [33] [34]

The work-management gap is categorical. Forgejo’s documented Project view is Kanban only; Table/Grid, Calendar, Roadmap, Gantt, Timeline, and first-class parent/subtask hierarchy were not verified. Docmost Community’s Bases Table/Kanban, API, page-level permissions, SSO/LDAP/SCIM/MFA, templates, and several governance features are paid. There is no verified cross-product integration, shared identity, ClickUp importer, or official native mobile client. This option is viable only when code-linked issues and manual reciprocal links are sufficient, rather than ClickUp-style operational planning.[32] [33]

### Nextcloud Deck plus Collectives

This cohesive AGPLv3 stack joins Deck task planning with Collectives and Text for a file-backed Markdown wiki. Collectives supports collaborative hierarchical pages, Markdown files visible through Files/WebDAV, downloads, bulk Markdown import, rich editing, editable Markdown tables, comments, file versions/comparison, search, templates, and documented task-board/calendar/whiteboard embeds. Deck verifies shared cards, assignments, labels, comments, attachments, activity, start/due dates, dependencies, Kanban, CalDAV integration, advanced search, and native editable Gantt.[35] [36] [37]

Deck exposes Kanban and Gantt only in the validated stable controls. It does not establish a native task List or Table view, a general parent/subtask tree, portfolio roadmaps, deep custom work-item types/fields, or advanced automation. A POC must test Deck performance using representative attachment-heavy boards because upstream warns of heavy query counts. It must also test Calendar editing, Collectives mobile use, complex Markdown round trips, embedded-surface permissions, guests/public sharing, off-host backup, and app compatibility through upgrades.[35] [38]

## Reference only

### GitLab Self-Managed Free

GitLab Free provides capable issue/task tracking, hierarchy, comments, filtered work-item lists, project boards, API/webhooks, integrations, and an unusually portable Git-based wiki with Markdown/RDoc/AsciiDoc/Org, history, and PDF export. It remains a strong engineering baseline. It is reference-only because it has no verified native Free Table/Grid or calendar planning view, only one group board, no Free roadmap/Gantt or epics, and a weaker general collaborative-document model. Its canonical Self-Managed Free deployment is typically unlicensed EE with Free features, while the source landscape is open-core rather than an unequivocally wholly open-source product distribution.[39] [40] [41]

A realistic single-node baseline, patch cadence, and backup exclusions create high operational burden for a small ClickUp replacement. ClickUp migration is also materially lossy without API/mapping work. Use it only when existing GitLab engineering workflows outweigh ClickUp-like planning and docs requirements.[39] [42]

### GitHub Projects plus Issues and docs/wiki

GitHub Projects has excellent engineering-workflow coverage: Issues, sub-issues, dependencies, customizable Table and Board, custom fields, automation, APIs, and a date/iteration Roadmap. Git-backed wikis provide Markdown portability and full history. GitHub.com lowers operational burden, but this is not an open-source or self-hosted product. Free native wikis must be public; the private-wiki path is paid. GitHub Enterprise Server is a commercially licensed appliance with substantial infrastructure needs, not a community edition. There is no native Calendar, and Roadmap is not a verified dependency-aware Gantt scheduler.[43] [44] [45]

### Notion Free

Notion offers the closest managed all-in-one editor/database experience: rich blocks, embeds, comments, database task properties, subtasks, dependencies, Table, Board, List, Calendar, and Timeline. Its cloud service is proprietary and has no official self-managed deployment. Free is unsuitable as a durable multi-user workspace because a workspace with two or more owners has a 1,000-lifetime-block cap, uploads cap at 5 MB, guests cap at 10, and version history lasts seven days. Markdown/CSV export supports portability, but does not create a full-fidelity restorable workspace or lossless Git-like round trip.[46] [47]

## Exclude

### AFFiNE Community Edition

Exclude AFFiNE from the current free/open-source shortlist. The current backend production licence requires an Enterprise subscription or other agreement and correct seat entitlement. This conflicts with older README language, so the current licence/pricing interpretation is a material governance risk. Its rich document/canvas system and Table/Kanban are attractive, but it lacks a verified ClickUp-class issue system, stable List/Timeline/Gantt coverage, dependencies, assignees, subtask trees, sprints, and portfolio hierarchy. Even after legal clearance, its self-host stack needs PostgreSQL, Redis, blob persistence, TLS/WebSockets, SMTP, upgrades, and optional search indexing.[48] [49]

### Jira Free plus Confluence Free

Exclude this cloud-only proprietary bundle for the target direction. Jira Free verifies tasks/issues, hierarchy, Kanban, List, Calendar, a single-space Timeline/basic roadmap, dashboards, and history. Confluence Free offers rich collaborative pages, comments, history/restore, tables, macros, embeds, and search. However, Free permissions fail normal multi-role requirements: Jira Free does not allow configurable roles, permissions, or work-item security, while Confluence Free allows all logged-in users broad content/space access and no new restrictions. The plan also limits each product to 10 users and 2 GB, while advanced roadmapping/governance is paid.[50] [51] [52]

### Linear Free

Exclude Linear Free despite polished issues, projects, cycles, documents, roadmaps, and integrations. Linear is proprietary SaaS with no self-hosted product. Every Free member is an Admin; private teams and guests require higher tiers. Free limits the workspace to two teams and 250 non-archived issues, and the sources did not establish task Table/Grid, in-app Calendar, dependency-aware Gantt, a hierarchical wiki, granular document ACLs, or a complete restorable backup workflow.[53] [54]

### AppFlowy current self-hosted offering

Exclude the current offering. The desktop/mobile/Web clients are AGPLv3, but the supported collaborative backend is a proprietary commercial fork requiring a licence key. Free self-host supports one seat and only selected-page guests; normal workspace membership requires the paid Team plan. Its current product surface has rich docs and verified Kanban, Table/Grid, Calendar, List, and Timeline, but the licensing and team-capacity blockers are decisive for a free, open-source, multi-user deployment.[55] [56]

## Cross-contender coverage index

The matrix makes the trade-offs explicit. “Verified” covers only evidence supplied in the validated deep dives. A dash means the evaluation did not establish the capability, rather than a claim that it cannot exist.

| Candidate | Tasks/issues | Kanban and other views | Roadmap | Rich knowledge/docs | Multi-user permissions | Licence/cost position | Operational burden |
|---|---|---|---|---|---|---|---|
| **OpenProject CE** | Work packages, hierarchy, dependencies | Kanban, saved table/list-like views, calendar, Gantt | Version/release roadmap; multi-project timeline | GFM Wiki, history/diffs, Markdown export; Docs lack versioning | Roles/project permissions | GPLv3; unlimited users/projects; no seat fee | Moderate |
| **Leantime** | To-Dos, hierarchy, dependencies, sprints | Kanban, Table, List, Calendar, project Gantt | Cross-project program plans paid | Rich project wiki; Markdown round-trip unverified | Project-scoped permissions | AGPLv3 core; plugins user-tiered and proprietary | Moderate |
| **Plane CE** | Work items, child items, cycles/modules | List, Board, Calendar, Table, Timeline | Dependencies/critical path and strategic objects paid | Project Pages; workspace Wiki Pro; CE entitlement conflicts | Basic roles; granular roles Enterprise | AGPLv3; no stated CE user cap | Moderate |
| **Huly** | Tracker issues/sub-issues, milestones | List, Kanban; no verified grid/month calendar | Stable Gantt unverified | Live collaborative Docs; raw `.md` round-trip unverified | Space privacy/role controls | EPL-2.0; no stated self-host seat fee | High |
| **YouTrack Free** | Issues and parent/subtasks | Table/list/tree, Kanban/Scrum, dashboard calendar | Interactive Gantt | Knowledge Base, revisions, Markdown export | Granular roles | Proprietary; 10 Users/3 Agents | Moderate |
| **Taiga** | Epics, stories, tasks, Issues | Kanban, Scrum/taskboard, list-like Issues | No verified calendar/Gantt/roadmap/timeline | Project wiki; transfer/coediting unverified | Project roles | AGPL/MPL; no self-host seat fee | Moderate-high |
| **Vikunja + Docmost** | Shared tasks, nested projects, dependencies | List, Table, Kanban, Gantt; native calendar/timeline unverified | Vikunja Gantt | Strong real-time Docs + Markdown interchange | Separate project/space models | Both AGPLv3; no identified Community seat cap | Medium-high |
| **Forgejo + Docmost** | Code-centric issues/dependencies | Kanban only; no verified Table/Calendar/Gantt/etc. | None verified | Strong Docmost Docs + Markdown interchange | Separate repository/space models | GPLv3+ and AGPLv3 cores | Moderate |
| **Nextcloud Deck + Collectives** | Cards, dependencies; shallow board/stack/card hierarchy | Kanban + Gantt; no native task List/Table | Gantt, no portfolio roadmap | File-backed Markdown wiki, versions/search/import | Cohesive Nextcloud identities/sharing | AGPLv3; no identified Community seat cap | Material |
| **GitLab SM Free** | Issues/tasks/hierarchy | Lists, boards; no native table/calendar | Free roadmap/Gantt absent | Git wiki; rich live Docs parity unverified | Basic roles; custom roles paid | Open-core; $0 self-managed Free | High |
| **GitHub Projects** | Issues/sub-issues/dependencies | Table, Board; no Calendar | Date/iteration Roadmap | Git wiki; rich collaboration unverified | Project access; private wiki paid | Proprietary SaaS/GHES commercial | Low cloud / high GHES |
| **Notion Free** | Database tasks, subtasks, dependencies | Table, Board, List, Calendar, Timeline | Timeline, no verified advanced Gantt | Strong blocks/embeds; export not lossless | Limited Free permissions/guests | Proprietary SaaS; multi-owner 1,000-block cap | Low |
| **AFFiNE** | No verified task/issue system | Table/Kanban; Calendar evidence needs acceptance test | Gantt unverified; Timeline planned | Strong rich docs/canvas; free history/comments unclear | Owner/member only established | Backend production licence commercial | Moderate-high |
| **Jira + Confluence Free** | Jira tasks/issues/hierarchy | Board, List, Calendar | Single-space Timeline; advanced cross-team paid | Excellent rich wiki; no Markdown-native round-trip | Free controls inadequate | Proprietary SaaS; 10 users/app | Low |
| **Linear Free** | Issues/sub-issues, projects, cycles | Kanban/List; grid/calendar unverified | Project timeline, not verified Gantt | Rich contextual docs; wiki/archive limits | Every Free member Admin | Proprietary SaaS; quotas | Low |
| **AppFlowy current self-host** | Database modelling rather than proven issue system | Kanban, Table, Calendar, List, Timeline | Gantt unverified | Rich live docs, Markdown import/export | Team controls paid | Multi-user server commercial; Free one seat | Moderate-high |

## Hands-on proof-of-concept plan

Run the POC on **OpenProject CE first**, with one backup conditional candidate selected from the team’s dominant risk: **Leantime** if an integrated rich project wiki matters most; **Huly** if live collaborative Docs matter most; **Vikunja plus Docmost** if Markdown-first docs are non-negotiable; or **Nextcloud Deck plus Collectives** if a unified files/wiki/calendar identity plane matters most. Do not run a generic feature tour. Use the same representative workload and acceptance tests on each candidate.

| Gate | Evidence to collect | Failure condition |
|---|---|---|
| Work migration | Import or map 25–50 representative ClickUp items across hierarchy, statuses, assignees, comments, dependencies, dates, custom fields, attachments, and permissions. | Loss of required hierarchy, discussion, attachment, or status semantics without an acceptable mapping. |
| Operating views | Recreate the team’s active Kanban, list/table, calendar, and roadmap/Gantt workflows. Use actual filtered views and a cross-project plan. | A required daily view does not exist, is plan-gated, or imposes unacceptable manual work. |
| Knowledge workflow | Migrate pages with nested structure, tables, images, code, diagrams, links, comments, and history. Execute an export/re-import where claimed. | No acceptable Markdown/file portability, version recovery, search, or collaboration model. |
| Permissions | Test administrator, project manager, contributor, reader, and any external/guest roles against real task and document boundaries. | Cannot enforce the team’s least-privilege boundaries without paid features or a separate identity model. |
| Resilience | Take an off-host backup, restore into a clean environment, validate DB + files/attachments + configuration, and rehearse an upgrade/rollback. | Restore omits user content/configuration or cannot meet the team’s recovery target. |
| Operations | Measure deployment components, RAM/CPU/storage, log/health workflow, TLS/SMTP/auth setup, patch steps, and routine backup burden. | The team cannot name an owner and feasible operating cadence. |
| Migration exit | Export a full representative project/wiki and document what does not restore. | The team cannot leave with usable task and document data. |

## Source gaps and conflicts requiring explicit confirmation

Several uncertainties are decision-relevant. Resolve them in the POC or through a written vendor/upstream statement before a selection.

| Candidate | Conflict or gap | Required confirmation |
|---|---|---|
| OpenProject CE | No first-party ClickUp importer identified; Documents lack version history; mobile beta is incomplete. | Perform representative migration; decide Wiki vs Documents usage; test mobile self-host connectivity. |
| Leantime | HTML wiki persistence is verified, while canonical Markdown, round trip, global wiki search, page ACLs, and restorable history are not. API/SSO wording also conflicts across official pages. | Test actual wiki export/import and recovery; confirm Community entitlements in the selected release. |
| Plane CE | Generic Pages documentation conflicts with CE/Free matrix for collaboration, versions, export, search, embeds, and comments. | Obtain a CE feature matrix for the selected version and prove behaviour in a local deployment. |
| Huly | Latest stable release lacks verified Tracker grid/month calendar/Gantt; Markdown docs round trip and web embeds are not established. | Pilot only the production tag; test backup completeness for large blobs and recovery. |
| YouTrack Free | Calendar is a dashboard due-date widget, not a confirmed project calendar; concurrent KB coauthoring is unverified. | Validate core calendar workflow and licence account definitions against headcount. |
| Taiga | Planning views, Markdown interchange, full document search, page ACLs, realtime coediting, and ClickUp import are unverified. | Treat required planning views as unavailable until a deployment demonstrates them. |
| Vikunja + Docmost | No unified identity/search/permission bridge or dedicated Docmost restore runbook was found; native Vikunja calendar/timeline are unverified. | Build two-system backup/restore and identity design; test manual/API links and webhook reconciliation. |
| Forgejo + Docmost | Task view/hierarchy gap is known; public-sharing entitlement documentation is inconsistent. | Confirm sharing controls and reject if Table/Calendar/Roadmap/Timeline/Gantt are required. |
| Nextcloud | Deck performance warning; calendar editing, mobile Collectives workflow, Markdown round trips, and embedded permissions need validation. | Load-test representative boards and test full backup/app-upgrade workflow. |
| AFFiNE | Current backend licence conflicts with legacy CE/MIT messaging. | Do not pilot for production without written version-specific commercial authorisation terms. |
| Jira/Confluence Free | Free access control is too broad for standard multi-role collaboration. | Only consider under a documented all-trusted-user exception. |
| AppFlowy | Current plan naming and self-host commercial entitlements have documented inconsistency. | Do not treat client-source licensing as a licence for the collaborative server. |

## Evidence index

The table links each synthesis entry to its deep dive and the primary official sources used in that validated record. The synthesis relies only on the structured results supplied for this task; it does not add new product research.

| Candidate | Validated deep dive | Primary evidence routes |
|---|---|---|
| Leantime | [01-leantime.md](01-leantime.md) | Pricing, source licence, deployment, marketplace, wiki source, API, releases [4] [13] [14] [15] |
| OpenProject CE | [02-openproject-community.md](02-openproject-community.md) | Community/pricing, source, work packages, boards, Gantt, Wiki, roles, API, operations [1] [2] [3] [8] [9] [11] [12] |
| Plane CE | [03-plane-community.md](03-plane-community.md) | Open-source/editions/pricing, self-hosting, layouts, Pages, Wiki, importer, mobile [5] [16] [17] [18] |
| Huly self-hosted | [04-huly.md](04-huly.md) | Platform/self-host repos, architecture, Docs, Tracker, pricing, backup, Gantt PR [6] [19] [20] [21] |
| YouTrack Server Free | [05-youtrack-server-free.md](05-youtrack-server-free.md) | Licence, pricing, Docker, Gantt, editor, importer, export, permissions, backup [22] [23] [24] [25] |
| Taiga self-hosted | [06-taiga.md](06-taiga.md) | Deployment, source repos, agile modules, Wiki, API, backup, upgrades, GitHub/importer [7] [26] [27] [28] |
| GitLab Self-Managed Free | [07-gitlab-self-managed-free.md](07-gitlab-self-managed-free.md) | Pricing/licensing, requirements, work items/boards/wiki/roadmap, backup/import-export [39] [40] [41] [42] |
| GitHub Projects | [08-github-projects.md](08-github-projects.md) | GHES/licensing/pricing, Projects, roadmap, sub-issues, wikis, access, server install [43] [44] [45] |
| Vikunja + Docmost | [09-vikunja-docmost.md](09-vikunja-docmost.md) | Pricing, task/views/install, Docmost pricing/editions/editor/install/source [29] [30] [31] |
| Forgejo + Docmost | [10-forgejo-docmost.md](10-forgejo-docmost.md) | Forgejo licence/install/projects/upgrade/webhooks; Docmost editions/editor/bases/import-export [32] [33] [34] |
| Nextcloud Deck + Collectives | [11-nextcloud-deck-collectives.md](11-nextcloud-deck-collectives.md) | Server/apps, pricing, Deck controls/Gantt, Collectives Markdown, backup/hardening [35] [36] [37] [38] |
| AFFiNE CE | [12-affine-community.md](12-affine-community.md) | Current licences/pricing, self-host docs, quotas, database/editor, backup/indexer [48] [49] |
| Jira + Confluence Free | [13-jira-confluence-free.md](13-jira-confluence-free.md) | Pricing, Free-plan access controls, licence, Data Center EOL, roadmap/wiki, cloud operations [50] [51] [52] |
| Notion Free | [14-notion-free.md](14-notion-free.md) | Pricing/block usage, views/tasks/timelines, editor/export/import/permissions/API [46] [47] |
| Linear Free | [15-linear-free.md](15-linear-free.md) | Pricing/terms, roles, display/projects/docs/export/security/API/webhooks [53] [54] |
| AppFlowy current self-hosted offering | [16-appflowy-self-hosted.md](16-appflowy-self-hosted.md) | Self-host plans, commercial server/licence, archived cloud, compose/config/docs, app import/export [55] [56] |

## References

[1]: https://www.openproject.org/community-edition/ "OpenProject Community Edition"
[2]: https://www.openproject.org/pricing/ "OpenProject pricing"
[3]: https://www.openproject.org/docs/user-guide/wiki/ "OpenProject Wiki user guide"
[4]: https://leantime.io/pricing/ "Leantime pricing"
[5]: https://developers.plane.so/self-hosting/editions-and-versions "Plane self-hosted editions and versions"
[6]: https://github.com/hcengineering/huly-selfhost "Huly self-hosted deployment"
[7]: https://taiga.io/deployment-pricing-options/ "Taiga deployment and pricing options"
[8]: https://www.openproject.org/docs/user-guide/work-packages/ "OpenProject work packages"
[9]: https://www.openproject.org/docs/user-guide/gantt-chart/ "OpenProject Gantt chart"
[10]: https://www.openproject.org/docs/user-guide/documents/ "OpenProject Documents"
[11]: https://www.openproject.org/docs/installation-and-operations/operation/backing-up/ "OpenProject backup operations"
[12]: https://www.openproject.org/docs/installation-and-operations/system-requirements/ "OpenProject system requirements"
[13]: https://github.com/Leantime/leantime "Leantime source repository"
[14]: https://marketplace.leantime.io/product/leantime-program-plans/ "Leantime Program Plans marketplace listing"
[15]: https://docs.leantime.io/installation/docker "Leantime Docker installation"
[16]: https://docs.plane.so/core-concepts/issues/layouts "Plane work-item layouts"
[17]: https://docs.plane.so/core-concepts/pages/overview "Plane Pages overview"
[18]: https://developers.plane.so/self-hosting/plane-architecture "Plane self-hosted architecture"
[19]: https://docs.huly.io/task-tracking/viewing-issues/ "Huly issue views"
[20]: https://docs.huly.io/knowledge-management/documents/ "Huly Documents"
[21]: https://github.com/hcengineering/platform/blob/develop/docs/guides/backup-restore.en.md "Huly backup and restore guide"
[22]: https://www.jetbrains.com/legal/docs/youtrack/license/ "JetBrains YouTrack Server licence agreement"
[23]: https://www.jetbrains.com/help/youtrack/server/gantt-charts.html "YouTrack Gantt charts"
[24]: https://www.jetbrains.com/help/youtrack/server/import-from-clickup.html "Import from ClickUp into YouTrack"
[25]: https://www.jetbrains.com/help/youtrack/server/youtrack-docker-installation.html "YouTrack Docker installation"
[26]: https://github.com/taigaio/taiga-front "Taiga front-end repository"
[27]: https://community.taiga.io/t/the-epics-wiki-meetup-icing-on-the-cake/126 "Taiga Epics and Wiki overview"
[28]: https://github.com/taigaio/taiga-docker "Taiga Docker deployment"
[29]: https://vikunja.io/help/views/ "Vikunja task views"
[30]: https://docmost.com/docs/editions "Docmost editions"
[31]: https://docmost.com/docs/user-guide/editor "Docmost editor"
[32]: https://forgejo.org/docs/v15.0/user/collaboration/project/ "Forgejo Projects documentation"
[33]: https://docmost.com/docs/user-guide/import-export "Docmost import and export"
[34]: https://codeberg.org/forgejo/forgejo "Forgejo source repository"
[35]: https://github.com/nextcloud/deck "Nextcloud Deck source repository"
[36]: https://docs.nextcloud.com/server/stable/admin_manual/collectives/index.html "Nextcloud Collectives administration"
[37]: https://docs.nextcloud.com/server/stable/user_manual/en/collectives/markdown_files.html "Collectives Markdown files"
[38]: https://docs.nextcloud.com/server/stable/admin_manual/maintenance/backup.html "Nextcloud backup documentation"
[39]: https://about.gitlab.com/pricing/ "GitLab pricing"
[40]: https://docs.gitlab.com/administration/license/ "GitLab licence administration"
[41]: https://docs.gitlab.com/user/project/wiki/ "GitLab project wiki"
[42]: https://docs.gitlab.com/administration/backup_restore/backup_gitlab/ "GitLab backup and restore"
[43]: https://github.com/pricing "GitHub pricing"
[44]: https://docs.github.com/en/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/changing-the-layout-of-a-view "GitHub Projects layouts"
[45]: https://docs.github.com/en/communities/documenting-your-project-with-wikis/about-wikis "About GitHub wikis"
[46]: https://www.notion.com/pricing "Notion pricing"
[47]: https://www.notion.com/help/understanding-block-usage "Notion block usage"
[48]: https://github.com/toeverything/AFFiNE/blob/canary/packages/backend/server/LICENSE "AFFiNE backend server licence"
[49]: https://affine.pro/pricing "AFFiNE pricing"
[50]: https://www.atlassian.com/software/jira/pricing "Jira pricing"
[51]: https://support.atlassian.com/jira-cloud-administration/docs/what-is-the-free-jira-cloud-plan/ "Jira Cloud Free plan"
[52]: https://support.atlassian.com/confluence-cloud/docs/manage-permissions-in-the-free-edition-of-confluence-cloud/ "Confluence Free permissions"
[53]: https://linear.app/pricing "Linear pricing"
[54]: https://linear.app/docs/members-roles "Linear members and roles"
[55]: https://appflowy.com/docs/Self-hosted-Plans-and-Pricing "AppFlowy self-hosted plans and pricing"
[56]: https://github.com/AppFlowy-IO/AppFlowy-SelfHost-Commercial/blob/main/SELF_HOST_LICENSE_AGREEMENT.md "AppFlowy SelfHost commercial licence agreement"