# Vikunja plus Docmost: self-hosted ClickUp replacement deep dive

_Assessment date: 24 September 2026. Scope: the combined, self-hosted Vikunja task system and Docmost knowledge base—not a comparison of other products._

---

## Executive verdict

**Verdict: Conditional pilot.** This is a credible, unusually well-aligned two-application replacement for a small team that prioritizes self-hosting, source availability under a real open-source license, and avoidance of recurring per-user charges. In the free self-managed configuration, Vikunja supplies the stronger work-management half: multi-user tasks, nested projects, task identifiers, assignees, comments, dependencies, List/Table/Kanban/Gantt views, a REST API, webhooks, CalDAV, and data export. Docmost supplies the missing wiki half: real-time collaborative rich pages, nested information architecture, comments, history and restore, rich tables, embeds, diagrams, Markdown import/export, and full-text search. Both community codebases are AGPLv3; the Docmost repository explicitly identifies separately licensed enterprise directories, so “Docmost” must mean its **Open Source/Community** edition unless the team elects to pay. [1] [2] [3]

The qualification is material. The composition is **two separate systems**, not one integrated ClickUp-style workspace. A native Vikunja-to-Docmost task/page link, unified search, unified permissions, unified notifications, or data synchronization was **not verified in the first-party documentation reviewed**. The free configuration also has two clear functional gaps against the stated target: Vikunja’s documented in-product views are List, Table, Kanban, and Gantt—not Calendar or a separate Timeline view—and Docmost Community excludes its Bases database/Kanban feature. Vikunja’s Gantt is a usable date-based roadmap/timeline substitute; CalDAV enables calendar clients, but that is not evidence of an in-product calendar UI. [4] [5] [6]

A pilot is warranted only if the team accepts clear boundaries: **Vikunja is the system of record for work; Docmost is the system of record for knowledge; links are maintained deliberately; and Calendar plus cross-tool workflow are tested before migration.** Do not buy either paid edition merely to start the pilot. The free versions cover the core proposed division of labor. Escalate to paid Docmost only if page-level restriction, SSO/MFA, API integration, or a wiki-side database/Kanban are requirements rather than nice-to-haves. [3] [6]

## Decision snapshot

| Decision dimension | Finding for the free, self-hosted pair | Confidence and implication |
| --- | --- | --- |
| Licensing and ownership | Vikunja’s repository is AGPLv3. Docmost Open Source is AGPLv3, while specified `ee` directories are under its enterprise license. Both can be self-hosted without a per-user Community license fee. | **Verified.** This meets the stated “true open-source” condition for the community components, subject to AGPL obligations if modified and offered over a network. [1] [2] |
| Task/issues | Vikunja has shared projects/teams, nested projects, task references, assignees, dates, labels, priorities, attachments, comments, checklists, relations/dependencies, global search, API tokens, and webhooks. | **Verified.** Strong task/work-management fit. It is not established as a replacement for every specialized engineering issue-tracker workflow. [7] [8] [9] [10] |
| Required views | Vikunja documents List, Table, Kanban, and Gantt. Gantt includes date bars, dependency arrows, and subtask grouping. | **Verified except Calendar.** No native Calendar or separate Timeline view was verified. Calendar is a pilot gate. [4] [5] |
| Roadmap | Vikunja’s Gantt is a roadmap-grade task timeline when start/end dates and relations are maintained. | **Verified.** It is not a separate portfolio roadmap product. [5] |
| Wiki/Docs | Docmost Community delivers real-time rich pages, hierarchy, comments, page history/restore, tables, attachments, embeds, diagrams, Markdown shortcuts, Markdown/HTML import and export, and full-text search. | **Verified.** This is the principal strength of the pair. [11] [12] [13] [14] |
| Permissions | Vikunja offers project user/team/link sharing at Read, Read & Write, or Admin. Docmost Community offers workspace roles and space roles, plus groups. Docmost page-level restriction is paid. | **Verified.** Reasonable coarse segmentation, but confidential-page controls are a paid Docmost gate. [15] [16] [17] |
| Integrations | Vikunja has documented REST API, API tokens, signed project/user webhooks, CalDAV, and a community integration catalog. Docmost Community supports rich embeds but its REST API, MCP/AI and SSO are paid. | **Verified.** The strongest automation surface is Vikunja. Cross-tool automation is not free in Docmost through its official REST API. [9] [10] [18] |
| Cost at the required baseline | Both Community/self-hosted cores are free with no documented user or task cap. The team still pays infrastructure, backups, email, and operator time. | **Verified.** This is the best economic case for the pair. [3] [19] |
| Operational burden | Two deployed applications mean at least Vikunja + database/storage and Docmost + PostgreSQL + Redis + storage, TLS/reverse proxy, backup testing, upgrades, monitoring, and account administration. | **Verified deployment requirements; operational conclusion is an assessment.** Low cash cost, medium-to-high operator burden. [20] [21] |

## Product boundary and architecture

The appropriate architecture is a **deliberately split stack**, not an attempt to recreate every ClickUp object in either component. Use Vikunja for project hierarchy, tasks, execution state, dates, dependencies, assignees, task discussions, and project-level automation. Use Docmost for durable specifications, team handbook pages, decisions, meeting notes, research, and embedded/reference material. Put a stable URL in the other system whenever a task needs a specification or a wiki page needs an execution tracker. This is an operating-model recommendation, not a feature claimed by either vendor.

```mermaid
flowchart LR
    accTitle: Recommended Vikunja and Docmost operating boundary
    accDescr: Vikunja holds execution work and Docmost holds knowledge. The applications remain separate and users maintain explicit links across the boundary.

    team["Team members"]
    vikunja["Vikunja\nprojects, tasks, dates, Kanban, Gantt"]
    docmost["Docmost\nspaces, pages, rich knowledge base"]
    automation["External automation\noptional, designed per use case"]
    backup["Backups and upgrades\nper application"]

    team --> vikunja
    team --> docmost
    vikunja -. "explicit task-to-page URL" .-> docmost
    docmost -. "explicit page-to-project URL" .-> vikunja
    vikunja --> automation
    vikunja --> backup
    docmost --> backup

    classDef application fill:#dbeafe,stroke:#2563eb,stroke-width:2px,color:#1e3a5f
    classDef operator fill:#fef3c7,stroke:#b45309,stroke-width:2px,color:#713f12
    class vikunja,docmost application
    class automation,backup operator
```

> **Boundary warning:** No first-party source reviewed documents a native bidirectional Vikunja–Docmost integration. Treat the arrows between them as a process to validate or build, not shipped product functionality.

This division avoids paying Docmost Business just to obtain its Bases/Kanban and avoids using task descriptions as a substitute wiki. It also avoids claiming that a two-app suite has one search index or one permission model when it does not. The resulting trade-off is real: the team gains ownership and a rich wiki at no per-seat price, but pays in context switching and administration.

## Licensing, editions, and actual cost gates

### Community/self-managed baseline

Vikunja is explicitly AGPLv3 and says its free self-hosted edition is fully functional for core work management. Its official pricing page states that self-hosting is free “forever,” with unlimited tasks and projects, List/Kanban/Gantt/Table views, reminders, repeating tasks, labels, filters, teams/shared projects, CalDAV, and imports. The repository metadata records a current AGPL-3.0 license and a v2.6.0 release published 31 August 2026. [1] [3] [22]

Docmost documents three self-hosted editions: Open Source, Business, and Enterprise. The Open Source edition is AGPL-3.0 and includes core documentation/collaboration. The official repository says the core is AGPL-3.0 but identifies `apps/server/src/ee`, `apps/client/src/ee`, and `packages/ee` as enterprise-licensed. That distinction matters: do not characterize the **entire distribution** as AGPL-only. The repository metadata shows v0.96.0 published 8 September 2026; its release contains active product and security work. [2] [23] [24]

The AGPL is a genuine free/open-source license, but it is copyleft. The official license text specifically addresses software used over a network: an operator of a modified network-server version must offer its corresponding source to users of that server. An unmodified, internal deployment has no recurring license charge; legal review is sensible if the team will modify, redistribute, or offer the applications as a service. [1] [25]

### Paid gates that matter

The following table separates verified capabilities from marketing inference. “Free” means the documented open-source/self-hosted baseline, not an expiring trial.

| Component | Free/self-managed availability | Verified paid or cloud-only gate | Decision significance |
| --- | --- | --- | --- |
| Vikunja core | Unlimited tasks/projects, all four documented core views, teams/shared projects, imports, CalDAV, task API and webhooks. | Pro gates the admin panel and time tracking on all Pro plans; audit logs begin at Business. Pro is in private beta, uses a license key, and checks the license server at startup and daily; cached entitlement lasts up to 72 hours before reverting to Community mode. [3] [19] | **No paid gate for the requested task baseline.** Instance-wide admin UI/audit evidence are not free. |
| Vikunja Cloud | Not free: Personal €4/month with 10 GB, Family €10/month for up to 5 users, Organization €5/user/month with 50 GB; 14-day trial. [3] | Managed hosting, updates, backups and TLS are the service benefit, not a free tier. | Not aligned with the no-recurring-fee preference; admissible only as a deliberately paid operations alternative. |
| Docmost Community | Free, self-hosted core: real-time collaboration, spaces, full-text search, rich pages and core documentation workflow. Community spaces are listed as unlimited. [2] [6] | None shown for basic per-space collaboration. | **Viable for the wiki baseline.** No published community seat/storage/usage cap was found in official pricing/docs reviewed. |
| Docmost Business | N/A for the no-fee baseline. | $6/seat/month billed annually, **minimum 10 seats** ($720/year minimum before tax). Adds Bases/Kanban, SSO/LDAP, granular page permissions, AI/MCP, Confluence migration, attachment search/indexing, MFA, API keys/management and email support. [6] | A hard recurring paid gate for wiki-side structured databases/Kanban, API, SSO/MFA, page restrictions and attachment-content search. |
| Docmost Enterprise | N/A for the no-fee baseline. | Custom price; adds SCIM, audit logs, SIEM, security controls, verification/review workflow, read confirmation, and priority support. [6] | Not required for the stated small-team baseline, but required for formal governance features. |

Docmost paid features must not be inferred from the rich editor. In particular, **Bases**—the feature that gives Docmost database rows and Table/Kanban views—is explicitly commercial and unavailable in the free edition. Docmost’s public roadmap calls its Calendar base view planned, not shipped. This does not block the proposed design because Vikunja, not Docmost Bases, is the work database; it does block a plan that expects Docmost Community itself to be a Notion-style task database. [26] [27]

### Free-team viability and limits

For the requested small team, the free configuration has **no documented seat cap** in either product’s Community/self-hosted materials. Vikunja’s pricing says self-hosted use can be personal or company-wide at no cost. Docmost describes Community as free/open-source and lists unlimited spaces. Storage is controlled by the team’s own disks/object storage, backup policy, and deployment sizing rather than a vendor free-tier quota. This is an important economic advantage, but it is not zero cost: server, domain/TLS, off-site storage, SMTP if needed, and administration remain. [3] [6] [20] [21]

Two limits deserve special attention. First, Docmost’s default self-hosted configuration sets an editor upload limit of 100 MB and import limit of 200 MB; these are configuration defaults that can be adjusted, not cloud quotas. Second, the paid Docmost Bases feature advises a practical performance target below 5,000 rows and has field/view limits. Neither restricts the intended Community wiki, but the latter becomes relevant if the team later buys Business to use Bases as a secondary work tracker. [21] [26]

## Vikunja: task, issue, view, and roadmap fit

### Work objects and hierarchy

Vikunja’s project hierarchy is well suited to a small team’s work taxonomy. Projects can be nested, shared with users or teams, and have globally unique task-reference prefixes such as `MOVE-42`. Individual tasks include rich text descriptions, labels, priorities, manual percentage progress, multiple assignees, start/end/due dates, attachments, checklists, comments, and task relations. Relations cover subtasks, parent tasks, blockers, and related work; Gantt groups subtasks beneath parents and displays relation arrows. These features make Vikunja a credible lightweight issues/work tracker rather than a personal to-do list. [7] [8] [5]

**Verified task collaboration:** projects can be shared to a user, a team, or an optional link share at Read, Read & Write, or Admin. Team admins manage team membership separately from project rights. Comments support mentions and notifications; users can subscribe to tasks or projects. These are coarse project-level controls, which are usually sufficient for a small internal team. They are not evidence of field-level permissions, enterprise audit trails, or highly specialized issue workflow controls. [15] [16] [17]

**Do not assume without pilot verification:** custom fields, issue templates/forms, sprints, advanced portfolio aggregation, task-level audit history, and rule-based workflow automation were not established as free capabilities in the first-party sources reviewed. The presence of labels, filters, dates, relations, task identifiers, webhooks, and API endpoints is strong; it is not proof of all ClickUp issue-management semantics. Test the team’s actual backlog, dependency, approval, and reporting workflow using sample data.

### Views, calendar, and roadmap reality

Vikunja’s current help documentation says every project starts with **List, Table, Kanban, and Gantt**. List supports drag ordering and basic sorting; Table has configurable columns, filters and multi-column sorting; Kanban has manual or filter-based buckets, WIP limits, done/default states, task cards and drag/drop; Gantt places tasks on dates, supports visual rescheduling, parent/subtask grouping and dependency arrows. That is a strong match for List/Table/Kanban and a meaningful match for “preferably roadmap/Gantt/Timeline.” [5]

The key negative finding is equally important: the same official view documentation enumerates only those four view types. **A native Calendar view was not verified. A distinct Timeline view was not verified.** Vikunja includes CalDAV, which can put task calendar data into a compatible external calendar client, but that is an integration—not proof of a first-party work calendar surface. For a team that schedules by calendar more than by Gantt, this should be a go/no-go pilot test, not an assumed workaround. [3] [5]

### Search, integrations, and mobile

Vikunja offers global project/task search, scoped searching by project, label, assignee or priority, a command palette, notifications, a v1 Swagger API plus a v2 OpenAPI 3.1 direction, personal API tokens, CalDAV, and HMAC-SHA256-signed webhooks. Project webhook events include task creation, update/deletion, assignee changes, comments, attachments, relations, project changes, and sharing events. One material limitation: webhook delivery is single-attempt with **no retry**, so business-critical integrations require a reliable receiver/queue or periodic reconciliation. [9] [10] [28]

The official integration catalog primarily lists community-maintained clients and connectors, including command-line clients, Home Assistant and a native iOS/macOS client. Vikunja provides a desktop app, while its own installation page cautions that the mobile app currently supports only very basic features. Therefore, API/webhook/CalDAV coverage is strong, but mobile feature parity should not be assumed. [18] [20]

### Migration and portability

Vikunja offers an account-level ZIP export containing projects, tasks, attachments and more, and can re-import its own export. Importers include CSV with field mapping, TickTick, WeKan, Planka, Todoist, Trello, and Microsoft To Do. CSV maps title, description, dates, priority, labels, project, reminders and other documented fields. **ClickUp is not named as a native importer.** A ClickUp migration should therefore be planned as a field-mapped CSV/API conversion and sample-validated for comments, relationships, files, rich formatting and historical metadata; do not promise one-click parity. [29] [30]

## Docmost: knowledge, editor, collaboration, and permissions fit

### Wiki structure and collaboration

Docmost has the right conceptual model for the knowledge half: a Workspace contains Spaces, and Spaces contain nested Pages. Pages can be nested/reordered by drag-and-drop, commented on inline, publicly shared when allowed, copied/moved between spaces, restored from trash, and versioned. Its history saves snapshots every minute during the first five minutes after creation and every five minutes during an edit session, supports version diff highlights, and can restore a prior version. The product documents real-time multi-user editing without overwrites. [11] [12] [31]

For normal internal collaboration, Community offers workspace Owner/Admin/Member roles; space rights are Full Access, Can Edit, and Can View. Groups can receive a space role, simplifying team access. This is a reasonably capable departmental wiki permission model. **Page-level restriction**, inheritance, and page-specific View/Edit grants are commercial Business/Enterprise features, so Community cannot be treated as a confidential-document system with granular page ACLs. [16] [17] [32]

### Rich editing, tables, embeds, and Markdown

Docmost’s WYSIWYG editor has strong verified coverage for the requested Docs surface. It supports headings, lists, to-do lists, quotes, code, callouts, toggle blocks, file/image/video attachments, KaTeX math, Mermaid/Draw.io/Excalidraw diagrams, @mentions, page links, inline comments, and drag/reorder blocks. Its table implementation supports insertion/deletion/reordering of rows and columns, header rows/columns, resize, merge/split, alignment and cell background colors. Its explicit embed list includes iframe URLs, Airtable, Loom, Figma, Typeform, Miro, YouTube, Vimeo, Framer, Google Drive, Google Sheets and Google Docs. [13]

Markdown interoperability is not merely a claim: Docmost supports Markdown input shortcuts, converts pasted Markdown into rich text, lets users copy a page as Markdown, imports `.md` files or Markdown/HTML ZIP archives, and exports a page or whole space as Markdown or HTML; space exports can include attachments and preserve the page-folder hierarchy in a ZIP. This makes Docmost comparatively portable for a rich wiki, although teams should not assume lossless round-tripping of every rich embed/diagram without a migration sample. The official documentation describes the formats and operations but does not state a universal fidelity guarantee. [11] [13] [14]

### Search, integrations, and knowledge portability

Docmost Community’s documented full-text search covers pages and attachments as objects, with workspace/space and type filters. Search result filtering of restricted pages is documented in the page-permissions article, but page restriction itself is paid. Attachment **content** search in PDFs/DOCX is a paid feature, as are API keys and REST API access. Thus, Community gives a sound page-title/body lookup experience but should not be positioned as a free enterprise document-search platform or automation hub. [18] [32] [6]

The rich embeds above are verified. Native Slack integration and GitHub/GitLab integrations are listed as **planned** on the public roadmap, not shipped capabilities. Docmost’s REST API, AI/MCP, SSO/LDAP, MFA, Confluence importer and templates are paid feature gates. For this pair, that has a direct consequence: free Docmost does not provide an official API bridge to automate task-page synchronization. Manual links are the safe baseline; any undocumented database-level integration would create upgrade and support risk. [6] [18] [27]

Docmost can import Markdown, HTML, DOCX, Notion exports and Confluence exports, and export pages/spaces as Markdown or HTML. The documentation identifies Confluence import as capable of preserving formatting, tree hierarchy, internal links, images, attachments and Draw.io diagrams, but that importer is a commercial feature according to the edition/pricing materials. Markdown/HTML import/export remains the free portability route. For ClickUp Docs migration, no native ClickUp importer was verified; export ClickUp Docs to a compatible intermediate format and sample-test it. [14] [6]

## Deployment, security, backups, and operations

### What must be run

Vikunja is compact: its API and frontend ship in one binary/container. A quick Docker path can use SQLite, while its documented Compose deployment uses PostgreSQL (with MySQL/MariaDB also supported), a persistent files directory, public URL, and service secret. It supports binary, Docker, packages, Kubernetes and Ansible-style installation paths. Production should use a reverse proxy/TLS, a durable database and mounted file storage; the official Docker guidance also calls out the container’s UID 1000 ownership requirements and writable `/tmp` for exports. [20] [33]

Docmost recommends Docker Compose. Its supplied design requires the Docmost container plus PostgreSQL and Redis, with persistent volumes for Docmost storage, PostgreSQL and Redis. It requires a correct `APP_URL`, a minimum 32-character `APP_SECRET`, database credentials, and a WebSocket-capable reverse proxy for real-time editing. Default files are local, with S3-compatible or Azure Blob support; sending invitations requires SMTP or Postmark. This is a normal small-team stack, but substantially more than a single binary. [21] [34]

A pragmatic production topology is one maintained Linux host or VM with Compose, a reverse proxy issuing TLS certificates, separate persistent volumes, outbound SMTP where invitations/reminders are wanted, and **off-host encrypted backups**. Do not expose either database or Redis directly to the Internet. This topology is an assessment based on the documented components, not a claimed vendor reference architecture.

### Backup, restore, and deletion controls

Vikunja’s backup documentation is unusually explicit: back up both the database and attachments/files. It gives restore paths for MySQL, PostgreSQL and SQLite, and warns that project deletion is permanent with no recycle bin. The application update procedure automatically runs database migrations after backup, so a tested pre-upgrade restore point is mandatory. [35] [20]

For Docmost, the installation materials establish durable Docmost-storage, Postgres and Redis volumes but the first-party documentation reviewed did **not** yield a dedicated backup/restore runbook. The operations team should therefore document and test its own recovery procedure before relying on it: PostgreSQL logical/physical backup, Docmost file storage backup (local volume or object store), configuration/secrets backup, and an explicit decision whether Redis persistence is included or reconstructed. This is a cautious operational recommendation—not a claim that every listed component is equally authoritative data. Docmost offers per-space Markdown/HTML export with attachments as a useful content-level portability fallback, not as a substitute for a database-consistent disaster-recovery plan. [21] [17]

### Security and compliance posture

Vikunja publishes a security reporting process and states it uses dependency/code scanning and security patching. The free version can run with local credentials and, according to Vikunja’s Pro FAQ, already includes SSO/LDAP; however, security controls are still the operator’s responsibility. Its paid audit logs are not a free feature. [36] [19]

Docmost states that its fully self-hosted deployment can run air-gapped without external dependencies. Its default configuration describes anonymous telemetry consisting of version and aggregate user/page/space/workspace counts, with `DISABLE_TELEMETRY=true` to turn it off. SSO/LDAP/OIDC/SAML, MFA, SCIM, audit logs, SIEM and granular page permissions are commercial gates. A small team that does not need those controls can operate Community safely with TLS, patching, least-privilege space membership, backups, and a restricted network; a team whose policy mandates them should budget for paid Docmost or choose a different architecture. [18] [21] [6]

## Maturity, governance, and risk assessment

Both projects show current release activity as of the assessment date. Vikunja’s GitHub repository was created in 2018, lists 5,497 stars, and released v2.6.0 on 31 August 2026; that release says it contained 380 commits, including 18 security fixes. Docmost’s GitHub repository was created in August 2023, lists 21,775 stars, and released v0.96.0 on 8 September 2026 with security fixes and editor/search/history improvements. These are useful signs of active maintenance, not a service-level commitment or independent security certification. [22] [23] [24]

The governance risk is concentrated rather than hidden: both systems are AGPL-governed community cores, while both also have a commercial path. Vikunja’s Pro features are technically public according to the vendor but are capability-gated by an active license check; Docmost’s enterprise code is separately licensed. The team should record this now in its architecture decision: use only published Community features as the no-fee baseline, pin images/releases, read release notes before upgrades, and keep export/restore tests current. [19] [2]

| Risk | Severity for this team | Evidence-based mitigation / pilot test |
| --- | --- | --- |
| No native Calendar UI in Vikunja | High if calendar is a hard minimum; otherwise medium | Verify a realistic due/start-date workload in Gantt and CalDAV calendar client. Do not accept “CalDAV exists” as native Calendar satisfaction. [3] [5] |
| Two systems, no verified native bridge | High | Create a link convention, test a clickable task↔page flow, and decide whether manual linking is acceptable. Do not build on undocumented Docmost Community API access. [18] |
| Docmost Community lacks granular page ACLs, SSO/MFA, API and Bases | Medium to high depending on policy | Segment sensitive material by Spaces/groups; price Business only if requirements are mandatory. Business has a 10-seat annual minimum. [6] [17] [32] |
| Split search and notifications | Medium | Include two-search workflow and task/page notification scenarios in acceptance testing; no unified search/notification feature was verified. |
| Self-hosted recovery burden | High | Automate off-site backups for every persistent component; perform a full restore and permission test before migration. [20] [21] [35] |
| Vikunja webhook non-retry | Medium for automation | Put a durable receiver/queue in front of business-critical automation, or reconcile via API. [10] |
| Migration loss | Medium | Export a representative ClickUp workspace, map a sample manually, and formally sign off on fields that will not migrate. Neither product verified a ClickUp-native importer. [14] [29] |

## Pilot design and acceptance criteria

Run a **time-boxed, non-production Conditional pilot** on self-managed Community editions. The pilot should have a named operator and use no paid feature as a dependency. Load a representative subset: one multi-level project, 30–50 tasks with owners/dates/relations/comments/files, one Gantt schedule, two role-separated teams, and a Docmost space with a nested handbook/specification, rich tables, embeds, diagrams, comments and history.

| Pilot question | Pass criterion | Why it matters |
| --- | --- | --- |
| Does Vikunja replace the core work loop? | Users complete task creation, assignment, comments, attachments, relation/dependency, Kanban movement, Table filtering and Gantt scheduling without a spreadsheet shadow system. | These are the verified core strengths. [5] [8] |
| Is Calendar acceptable? | The team explicitly approves either Gantt plus CalDAV client workflow or accepts that a native Calendar is absent. | This is the main view gap. [3] [5] |
| Does Docmost replace Docs/wiki? | Users jointly edit one page, comment, inspect/restore history, create a complex table, embed at least two real resources, and export/import a Markdown space sample. | Validates the knowledge surface, not just a feature checklist. [11] [12] [13] [14] |
| Are Community permissions sufficient? | The team can isolate spaces using Full Access/Can Edit/Can View and groups without needing restricted individual pages. | Page restriction is a paid gate. [17] [32] |
| Is the two-tool boundary tolerable? | Every pilot task needing documentation has a maintained Docmost URL and every pilot page needing execution has a Vikunja project/task URL; users can find both within the team’s agreed workflow. | No native bridge was verified. |
| Can the team operate it? | TLS reverse proxy is working; registrations are controlled; backup completes; a restore into a clean environment recovers both Vikunja and Docmost sample content; upgrades are rehearsed. | Self-hosting, not licensing, is the principal ongoing cost. [20] [21] [35] |

**Promote only if all six questions pass.** If Calendar is a strict non-negotiable, or if the team requires unified work/wiki search and page-level confidentiality without a recurring fee, this solution should not advance beyond a reference deployment. If those needs are flexible, the pair offers a well-aligned, low-license-cost owned stack.

## References

[1]: https://github.com/go-vikunja/vikunja "go-vikunja/vikunja repository: AGPL-3.0 license and project metadata"

[2]: https://github.com/docmost/docmost "docmost/docmost repository: AGPL core and enterprise-directory licensing"

[3]: https://vikunja.io/pricing/ "Vikunja pricing: free self-hosting, Cloud plans, and feature comparison"

[4]: https://vikunja.io/features/ "Vikunja features: project hierarchy, task views, collaboration and CalDAV"

[5]: https://vikunja.io/help/views/ "Vikunja Help: List, Table, Kanban, and Gantt views"

[6]: https://docmost.com/pricing "Docmost self-managed pricing and Community, Business, Enterprise comparison"

[7]: https://vikunja.io/help/projects/ "Vikunja Help: project hierarchy, identifiers and project controls"

[8]: https://vikunja.io/help/tasks/ "Vikunja Help: task detail, rich descriptions, assignees, attachments, relations and comments"

[9]: https://vikunja.io/docs/api-documentation/ "Vikunja API documentation: tokens, Swagger and OpenAPI"

[10]: https://vikunja.io/help/webhooks/ "Vikunja Help: webhook events, signing, and delivery behavior"

[11]: https://docmost.com/docs/user-guide/pages "Docmost documentation: pages, comments, history, sharing and exports"

[12]: https://docmost.com/docs/user-guide/import-export "Docmost documentation: import and export formats"

[13]: https://docmost.com/docs/user-guide/editor "Docmost documentation: WYSIWYG editor, tables, diagrams and embeds"

[14]: https://docmost.com/docs/user-guide/search "Docmost documentation: full-text workspace search"

[15]: https://vikunja.io/help/sharing-and-teams/ "Vikunja Help: sharing, teams and link shares"

[16]: https://vikunja.io/docs/permissions/ "Vikunja documentation: project permission levels"

[17]: https://docmost.com/docs/user-guide/spaces "Docmost documentation: spaces, membership roles and exports"

[18]: https://docmost.com/docs/ "Docmost introduction: core features and paid edition features"

[19]: https://vikunja.io/docs/pro/ "Vikunja documentation: Pro feature gates, entitlement checks and user limits"

[20]: https://vikunja.io/docs/installing/ "Vikunja installation documentation: deployment options, mobile scope and storage"

[21]: https://docmost.com/docs/installation "Docmost Docker installation: PostgreSQL, Redis, volumes, secrets and WebSockets"

[22]: https://github.com/go-vikunja/vikunja/releases/tag/v2.6.0 "Vikunja v2.6.0 release"

[23]: https://github.com/docmost/docmost/releases/tag/v0.96.0 "Docmost v0.96.0 release"

[24]: https://docmost.com/docs/editions "Docmost license and editions"

[25]: https://raw.githubusercontent.com/go-vikunja/vikunja/main/LICENSE "Vikunja AGPLv3 license text"

[26]: https://docmost.com/docs/user-guide/bases "Docmost Bases: paid availability, table/Kanban views and limits"

[27]: https://docmost.com/roadmap "Docmost public roadmap: planned and shipped features"

[28]: https://vikunja.io/help/search-and-navigation/ "Vikunja Help: global search, scoped search, notifications"

[29]: https://vikunja.io/help/import-and-export/ "Vikunja Help: data export and supported imports"

[30]: https://vikunja.io/docs/migration-from-third-party-services/ "Vikunja documentation: supported migration sources and setup"

[31]: https://docmost.com/docs/user-guide/workspace "Docmost documentation: workspace hierarchy and roles"

[32]: https://docmost.com/docs/user-guide/pages/page-permissions "Docmost documentation: paid granular page permissions"

[33]: https://vikunja.io/docs/docker-walkthrough/ "Vikunja Docker Compose walkthrough"

[34]: https://docmost.com/docs/self-hosting/configuration "Docmost self-hosted configuration: storage, email, search and telemetry"

[35]: https://vikunja.io/docs/what-to-backup/ "Vikunja documentation: database and attachment backup"

[36]: https://vikunja.io/security/ "Vikunja security practices and vulnerability reporting"