## 2026-09-02 — Research: can Plane (plane.so) replace Vikunja?

- User asked whether Plane could replace Vikunja, motivated by (a) preferring Plane's UI and (b) Plane bundling a wiki useful for requirements work.
- KB had no prior content on either tool (`grep` over `wiki/ raw/ workload/ linked/ libs/` found nothing) — answered from external web research only, not from the cascade.
- Key finding: the self-hosted **Community Edition** is a separate AGPL-3.0 codebase at ~parity with Cloud's *Free* tier, with **no Pro/Business features at all**. The features that motivate the switch are paid:
  - Workspace **Wiki** → Pro ($6/seat/mo)
  - **Nested pages** → Business ($13/seat/mo)
  - Work-item mentions in pages / convert text → work item → Business
  - **Recurring work items** → Business (Vikunja has these free)
  - Importers incl. CSV → Cloud/Commercial only (no migration path into CE)
  - Epics/initiatives, workflows/approvals, custom work-item types, SSO → paid
- CE does include project-level Pages (unlimited), five layouts, cycles, modules, intake, estimates, REST API, webhooks, no seat limit.
- Vikunja capabilities Plane lacks at any tier found: CalDAV (VTODO) two-way sync, Quick Add Magic.
- Ops delta: Vikunja = single Go binary + SQLite, ~1 GB RAM. Plane = ~13 containers, 4 GB RAM minimum / 8 GB recommended, ~1.8 GB idle; CE has no auto-upgrade and documented upgrade breakage (makeplane/plane#8708) plus contradictory seat-limit docs (#9086).
- Recommendation given: CE does not deliver the stated wiki benefit and is a net regression for personal task use; if the wiki is the real driver, either pay for Pro/Business, or keep Vikunja and pair it with a dedicated docs layer (this CKB, Outline, or BookStack).
- No `wiki/` writes made — offered to record this as a decision (`ckb-decide`) or ingest it as entity pages if the user wants it durable.