Project Management & Collaboration
Vikunja
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 4 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Vikunja (open source) · vikunja.io
Report an error on this page Is this your product? →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Vikunja is an AGPLv3-licensed, self-hostable task manager with a hosted cloud, from Konrad Langenberg Software of Lübeck, Germany; Vikunja Cloud runs at Hetzner in Germany and Finland. The bench scores it strongest on collaboration depth, integrations, sovereignty and support documentation, each at 6 to 7: eleven task-relation types that set their opposites automatically, sharing with users, teams or link shares, HMAC-SHA256-signed webhooks across sixteen project and three user event types, importers from eight sources, and a help center of twenty-one topics with separate technical documentation. Reporting is the uniform floor at 4 — dashboard, saved filters and an Upcoming view give task-level visibility, and no public information appears on time, budget or utilization reporting. Onboarding effort spreads 5 to 7: higher scores credit Quick Add Magic and imports advertised in minutes, the lower score weighs self-hosted configuration such as the public-URL setting. No material disagreements were computed among the judges. No public prices appear for the hosted cloud or enterprise packages.
Speaks for it
- Webhooks ship with HMAC-SHA256 signing, JSON payloads and API-token management across sixteen project and three user event types.
- Eight import sources including OAuth paths from Todoist, Trello and Microsoft To Do, with custom migrators supported.
- Eleven task-relation types set opposite relations automatically, and projects share with a user, a team or a link share.
- A help center of twenty-one topics sits alongside separate technical documentation for server setup and API details.
- Self-hosting under AGPLv3 takes the vendor out of the data path, and the cloud runs at Hetzner in Germany and Finland in ISO/IEC 27001-certified data centers.
Held against it
- Reporting stops at the dashboard, saved filters and Upcoming view, with no public information on time, budget or utilization reporting.
- Only the hosting subprocessor is named, and no public data processing agreement appears on the vendor's pages.
- Webhooks are sent once and failed deliveries are not retried.
- No public information appears on native Slack, Teams, file-storage or automation-platform integrations.
- No public prices appear for the hosted cloud or the enterprise support packages, which are scoped by email.
Best for
- You want a self-hostable, AGPL-licensed task manager with the option of a hosted cloud at Hetzner in Germany and Finland.
- You are moving from Todoist, Trello or Microsoft To Do and want an OAuth import the vendor advertises as taking minutes.
- You build your own integrations and want documented, HMAC-signed webhooks with API tokens and support for custom migrators.
- You want fast first value — Quick Add Magic turns one typed line into a dated, prioritized task.
Avoid if
- You need time, budget or utilization figures for management questions — the reporting evidenced is dashboard, saved-filter and Upcoming task visibility.
- Your workflows depend on guaranteed webhook delivery — the documentation states failures are not retried.
- You will run a self-hosted migration hands-off — the import path requires a correctly set public URL and large imports can take up to several hours.
- Your procurement requires named subprocessors beyond hosting — the vendor's pages name only the hosting provider.
The scores
Collaboration depth
Show reasoningHide reasoning
How this is scored
How much real multi-person project work the tool carries: shared planning, assignments, dependencies, workload, comments, guest access.
0 — A personal task list; a second user has no defined place in it.
3 — Tasks can be shared and assigned, but planning stays per-person — no shared timeline, workload or dependency view.
5 — Solid shared projects with assignments, comments and at least one team-level planning view; gaps appear in cross-project or capacity planning.
8 — Team-level planning is first-class: cross-project views, workload/capacity, dependencies, guest or client access with sane permissions.
10 — Handles the full span from two freelancers to a structured department in one model — planning, capacity, permissions and client involvement all without workarounds.
The Data Protection Officer
Projects can be shared with a user, a team or a link share, tasks carry assignees, comments and attachments, and eleven relation types including blocking give real dependencies, with List, Kanban, Table and Gantt views providing a shared timeline. Cross-project visibility is achieved through saved filters rather than a dedicated view, and we found no public information on workload or capacity planning. 1 6 12
The Bootstrapper
Sharing with a single user, a team, or a link share, plus comments, assignees, and eleven relation types that automatically set their opposites (blocking/blocked-by) alongside a Gantt view gives real dependency-level team planning, and saved filters act as cross-project views. The captured pages show no workload or capacity planning, which is what would carry a 3-seat team into a 30-seat department without workarounds. 1 6 12
The Enterprise Architect
Real multi-person work is evidenced: sharing with users, teams and link shares, assignees, comments, and eleven relation types including blocking and blocked-by, with a Gantt view for a shared timeline. Cross-project visibility runs through personal saved filters rather than a team planning surface, and we found no public information on workload or capacity views, which is what I would need before putting two hundred seats on it. 1 6 7 12
The UX Purist
Assignments, comments, eleven task-relation types including blocking and subtasks, sharing with users, teams and link shares, and a Gantt view make team planning real, and saved filters give a cross-project view straight from the dashboard. We found no public information on workload or capacity views, which is the visible ceiling for a structured department. 1 6 7 12
The Integrator
Sharing runs the full ladder — single user, team, or link share — with eleven task relation types including blocking and subtask hierarchies that set their opposite automatically, and per-project Gantt for timeline planning. Cross-project visibility exists only as saved filters rather than a first-class team plan, and I found no public information on workload or capacity views or time tracking to feed them. 1 6 7 12
The Skeptic
Sharing with users, teams and link shares, assignees, comments, Gantt and eleven task-relation types with automatic opposites are all evidenced — real multi-person machinery, not a personal list. But we found no public information on workload or capacity views, and cross-project visibility rests on saved filters rather than any team-level planning surface, so this sits below the top band. 1 6 12
Reporting
Show reasoningHide reasoning
How this is scored
Whether the tool can answer questions about the work: progress, time, budgets, utilization — and export the answer.
0 — No reporting beyond looking at the board.
3 — Fixed per-project status views only; nothing aggregates across projects and nothing exports cleanly.
5 — Useful standard reports (progress, tracked time) with basic filters and CSV export, but limited customization and no budget/utilization depth.
8 — Configurable cross-project reporting incl. time, budgets and utilization, with dashboards and reliable exports.
10 — Reporting is a product in itself: custom report builder, scheduled delivery, API access to every metric the UI shows.
The Data Protection Officer
The dashboard, saved filters and the Upcoming view with a date range picker let a person see overdue and due work across projects, which goes beyond fixed per-project status. We found no public information on time tracking, budgets, utilization or report exports; the only export evidenced is copying as Markdown. 7 12
The Bootstrapper
What is evidenced is task-level visibility — a dashboard of upcoming and recent work, a saved-filter home screen, and an Upcoming view with date-range, overdue and no-date controls — not reporting in the business sense. We found no public information on time tracking, budgets, utilization or scheduled reports, and the only exports shown are Copy as Markdown and a general file export. 7 12
The Enterprise Architect
The dashboard aggregates upcoming and overdue work across all projects with custom saved filters, and output stops at copy-as-markdown. We found no public information on time tracking, budgets, utilization, or any exportable report format, so this cannot yet answer management questions about the work. 7 12
The UX Purist
The dashboard with overdue-first sorting, a date-range picker and saved filters is a decent progress surface, and Copy as Markdown is the one export touchpoint shown. We found no public information on time tracking, budgets, utilization, or any exportable cross-project report. 7 12
The Integrator
A dashboard with an overdue-first Upcoming view and custom saved filters answers what is due across projects, and data leaves cleanly through import/export and Copy as Markdown. Beyond that the pages go quiet: I found no public information on time, budget or utilization reporting, a custom report builder, or scheduled delivery. 7 12
The Skeptic
The dashboard, the Upcoming view with a date-range picker and cross-project saved filters give a filtered view of work across projects, which is more than per-project status. We found no public information on time, budget or utilization reporting, and the only export surfaced is copy-as-Markdown — no report export path appears on any captured page. 7 12
Integrations
Show reasoningHide reasoning
How this is scored
How well the tool connects to the rest of the stack: native integrations, calendar/comms hooks, API and webhooks, import/export paths.
0 — A closed box — no API, no integrations, CSV out if anything.
3 — A handful of marquee integrations, no public API or an API that covers a fraction of the product.
5 — The common set (calendar, Slack/Teams, file storage) plus a documented public API; automation platforms partially covered.
8 — Broad native catalogue, well-documented API and webhooks, first-class automation-platform support and real import paths from competitors.
10 — Ecosystem-grade: everything in 8 plus the tool is itself extensible (apps/plugins, AI/MCP surfaces) and exit via API export is complete.
The Data Protection Officer
Webhooks are genuinely deep — project and user webhooks across nineteen documented events, HMAC-SHA256 signatures, token-authenticated management — alongside CalDAV, a surface for AI clients, and importers from Todoist, Trello, Microsoft To Do, Planka, TickTick, WeKan, CSV and JSON with custom migrators supported. We found no public information on native integrations with chat or file-storage services or with automation platforms. 9 11 12
The Bootstrapper
The webhook surface is unusually well documented — sixteen project events and three user events, HMAC-SHA256 signing, API tokens and an API to manage webhooks — plus importers from Todoist, Trello, Microsoft To-Do, Planka, TickTick, WeKan and CSV, custom migrators, CalDAV, and MCP for AI clients. We found no public information on native Slack, Teams or file-storage integrations or on automation platforms, which is what keeps it out of the broad-catalogue band. 9 11 12
The Enterprise Architect
Webhooks are genuinely documented — nineteen events, HMAC-SHA256 signing, API tokens and an API reference — alongside MCP for AI clients, CalDAV, and importers from Todoist, Trello, Microsoft To Do, Planka, TickTick and WeKan with custom migrators supported. We found no public information on Slack, Teams or file-storage integrations, or automation-platform coverage, which caps this below the broad-catalogue tier. 9 11 12
The UX Purist
Webhooks are a first-class surface — nineteen documented events, HMAC-signed payloads, management via API tokens — plus eight import sources with support for custom migrators, CalDAV, and an MCP topic for AI clients. We found no public information on Slack, Teams or automation-platform integrations, and the docs state failed webhook deliveries are not retried. 9 11 12
The Integrator
The connective tissue is genuinely good: webhooks with a documented JSON payload, HMAC-SHA256 signing, and sixteen project plus three user event types manageable through the API with tokens; OAuth importers from Todoist, Trello and Microsoft To Do; a documented path to develop custom migrators; MCP for AI clients; and CalDAV. I dock it for a fire-once webhook with no retry, and I found no public information on native Slack or Teams integrations, file-storage connectors, or automation-platform support. 9 11 12 13
The Skeptic
Documented webhooks with nineteen event types and HMAC-SHA256 signing, API tokens, CalDAV, MCP for AI clients, and genuine importers from Todoist, Trello, TickTick, WeKan, Planka and CSV — with custom migrators — put this well above the basics. We found no public information on Slack or Teams connectors, file-storage integrations, or automation-platform support, so it stops short of the broad native catalogue. 9 11 12
Onboarding effort
Show reasoningHide reasoning
How this is scored
Time and friction from signup to first real value for a small team, without paid services.
0 — No self-serve path — onboarding starts with a sales call and an implementation project.
3 — Self-serve exists but the first project requires configuration a newcomer cannot judge yet (workflows, custom fields, permissions) before anything works.
5 — A team gets a first project running within a day; trial requires payment details or key steps live behind docs.
8 — Signup to working project inside an hour: guided setup, sensible defaults, templates, trial without payment details.
10 — Minutes to value even for non-tool-people, importers pull existing work in, and the tool teaches its own advanced features as the team grows into them.
The Data Protection Officer
The product begins as a personal to-do list with plain-text quick add, and cloud users can import from Todoist, Trello or Microsoft To-Do "in minutes" through a settings screen without a publicly reachable instance. Self-hosted migration carries configuration a newcomer must judge — a public URL setting for OAuth imports and a network-safety setting for local sources — and we found no public information on guided setup, templates or trial terms. 1 2 11
The Bootstrapper
The migration path is genuinely fast — OAuth import from Todoist, Trello or Microsoft To-Do advertised as taking minutes, a file-import fallback for everything else, and Quick Add Magic so a newcomer types "Buy groceries tomorrow!3" and gets a task with a due date and priority. We found no public information on trial length, whether cloud signup asks for payment details, or project templates, so I stop short of the top band. 2 11 12
The Enterprise Architect
Quick Add Magic, sensible defaults such as a default project, and importers that pull existing Todoist or Trello work in minutes point to fast first value on the hosted path. The migration tooling demands environment configuration a newcomer cannot yet judge — a public URL setting for OAuth, SSRF rules for LAN imports — and can run for hours on large accounts, and we found no public information on trial terms or whether signup asks for payment details. 2 7 11
The UX Purist
Quick Add Magic means a first task typed in seconds — the docs show "Buy groceries tomorrow!3" creating a dated, prioritized task — and importers pull existing work from Todoist, Trello and five more sources through a settings screen, which is minutes-to-value with the help pages teaching the syntax. Held below the top because the OAuth migration path hinges on a correctly configured public URL and blocks LAN sources by default, and we found no public information on guided setup, project templates, or trial payment terms. 2 11 12
The Integrator
The cloud path starts from a personal to-do list where Quick Add Magic turns one typed line into a dated, prioritized task, and the OAuth importers redirect through the browser so even a locally hosted instance needs no public exposure. Friction remains on the self-host side, where migrations hinge on a correctly set public-URL setting and large imports can take hours, and I found no public information on guided setup, templates, or trial terms. 1 11 12
The Skeptic
Cloud users get import-in-minutes paths from major competitors and quick-add syntax that creates structured tasks from one line of text. But we found no public information on guided setup, templates or trial terms, and the self-host path documented here requires environment variables and SSRF configuration a newcomer cannot yet judge — OAuth imports even fail on a wrong public URL until it is set. 2 11 12
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where the company and the data actually sit: legal entity, ownership control, data residency, and subprocessor exposure to non-EU jurisdictions.
0 — Non-European vendor, data on US infrastructure under US law, no DPA worth the name.
3 — DPA and GDPR language present, but hosting defaults to the US or ownership sits outside Europe — compliance paperwork over substance.
5 — EU data residency is available and contractually fixed, but the vendor or its controlling owner is non-European, or core subprocessors put data within CLOUD Act reach.
8 — European company under European control with EU-resident data and a public DPA; remaining exposure is limited to identifiable subprocessors (e.g. a US hyperscaler's EU region) and is documented.
10 — European company, European control, EU-only data residency on European infrastructure, subprocessor list free of extraterritorial reach — verifiable, not asserted.
The Data Protection Officer
The imprint names Konrad Langenberg Software in Lübeck with a German VAT ID, all of Vikunja Cloud runs at Hetzner in Germany and Finland under ISO/IEC 27001, and the privacy policy publishes user rights with a dedicated GDPR contact — plus self-hosting puts the data entirely on your own infrastructure. What holds this below the top is that only the hosting subprocessor is named, we found no public information on processors for email, support or payment, and no public data processing agreement for the cloud service appears on the captured pages; ownership control beyond the imprint is likewise not evidenced. 2 3 4 5
The Bootstrapper
A German imprint — Konrad Langenberg Software, Lübeck, with a VAT ID — and all of Vikunja Cloud hosted at Hetzner in Germany and Finland under an ISO/IEC 27001 certification is the substance I want, and AGPL source plus "Run Vikunja on your own infrastructure" is the ultimate escape hatch. It stops short of full marks because we found no public data processing agreement, and only the hosting provider is named — no disclosure of who processes payment, email or support data. 1 2 4 5
The Enterprise Architect
The imprint shows a German entity with a German VAT ID, the code is AGPL, and the cloud runs on Hetzner in Germany and Finland in ISO 27001-certified data centers — substance, not paperwork, with self-hosting as a clean exit. For procurement I still need a public data processing agreement, confirmation of ownership control and disclosure of non-hosting subprocessors such as email or payment processing, and we found no public information on any of the three. 2 4 5
The UX Purist
A German imprint with a named Lübeck entity and VAT number, every part of the cloud hosted at Hetzner in Germany and Finland under an ISO 27001 certification, plus an open-source licence and a self-host option, put the substance well above paperwork. We found no public information on a data processing agreement, and only the hosting subprocessor is named, leaving email, support and payment processors undisclosed. 1 2 4 5
The Integrator
The imprint names Konrad Langenberg Software in Lübeck with a German VAT ID, cloud hosting sits at Hetzner in Germany and Finland behind ISO 27001-certified data centers, and self-hosting removes the vendor from the data path entirely. What holds it back: I found no public information on a public data processing agreement, and only the hosting subprocessor is named — email, support and payment processing are undisclosed. 1 2 4 5
The Skeptic
A German imprint names Konrad Langenberg Software in Lübeck with a German VAT number, cloud hosting sits at Hetzner in Germany and Finland, AGPL code is inspectable, and self-hosting removes the vendor from the data path entirely. Two things keep it out of the top band: only the hosting subprocessor is named, with email delivery, support tooling and payment processing undisclosed, and no public data-processing agreement appears on any captured page. 1 4 5
Support & documentation
Show reasoningHide reasoning
How this is scored
Whether a stuck user gets unstuck: docs quality, support channels and their availability per plan, and the health of the learning surface.
0 — No docs beyond marketing pages; support is a contact form that may answer.
3 — Docs exist but are thin or stale; support on entry plans is effectively email-only with slow turnaround.
5 — Searchable help center covering the core product; chat or email support on all plans with reasonable response times.
8 — Deep, current docs incl. onboarding guides and templates; fast chat support not gated to top tiers; visible changelog.
10 — Docs, academy, community and support so good they are a reason to buy; SLAs published, support quality independent of plan.
The Data Protection Officer
The help center covers twenty-one topics from tasks and views through permissions and webhooks, backed by separate technical documentation for server setup, API details and development. Support runs by email with paid consulting, training and an enterprise tier bundling SLAs and priority access to the developers, but we found no public information on chat support, published response times or a visible changelog. 12 13
The Bootstrapper
The help center covers roughly twenty topics with real depth — relation types, webhook payload formats and signing, migration edge cases like SSRF settings — and the technical documentation covers server setup, API details and development guides, all free. Beyond that, support is email, and SLAs, priority support and direct developer access sit in enterprise packages with no published response times; we found no public information on chat support or a visible changelog. 12 13
The Enterprise Architect
The help center covers the core product from tasks and sharing to webhooks and permissions, technical documentation covers server setup and API details, and consulting, training, migration assistance and enterprise packages with SLAs and priority support are offered over email. We found no public information on chat support, published response times or a visible changelog, so I cannot verify the SLA terms an enterprise purchase would rest on. 12 13
The UX Purist
The help center is broad and genuinely deep — twenty-plus topics down to webhook payload formats and exact migration UI paths, with separate technical docs for server setup and the API — and current enough to reference version 2.3.0 behavior. Support runs through email, consulting and enterprise packages with SLAs; we found no public information on chat support, response times, or a public changelog. 7 9 12 13
The Integrator
Documentation is what I like to see: a help center spanning twenty topics from webhooks through MCP to import/export, separate technical documentation covering server setup, API details and development guides, and pages that reference current release versions. Support beyond the docs is consult-shaped — training, migration assistance, enterprise packages with SLAs — all arranged by email, and I found no public information on chat channels, published response times, or a visible changelog. 7 12 13
The Skeptic
A help center with some twenty topics plus technical documentation for server setup, API details and development reads deep, and the docs are honest about sharp edges — webhooks are sent once with no retry, and LAN imports fail by default — which is a good sign of currency. We found no public information on chat support, published response times or a visible changelog; the base channel is email, with consulting, training and SLA-backed enterprise tiers sold as services without numbers. 9 12 13
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Can a buyer determine the real, payable cost of the tool for their team before talking to anyone?
0 — No public pricing at all — every number sits behind "contact sales".
3 — Some tiers are public, but a deciding factor (seat minimums, mandatory add-ons, billing-period surcharge, tax treatment) only surfaces at checkout or in fine print.
5 — Self-serve tiers are publicly priced and the billing-period difference is stated, but the headline number still needs qualifying — e.g. annual-only headline, taxes excluded without saying so, or an opaque enterprise tier doing real work.
8 — Every self-serve tier is fully priced with billing periods and tax treatment plain on the page; only genuinely custom enterprise work lacks a number.
10 — Every tier including enterprise has a public price or published price formula, and the headline number is the number on the invoice.
The Data Protection Officer
The captured pages show no price for any tier of the hosted cloud offering, and the only payment information anywhere is sponsorship through GitHub Sponsors, Open Collective or Buy Me a Coffee, which funds development rather than purchasing the product. We found no public pricing for the cloud or the enterprise support packages, so the payable cost cannot be determined before contacting the vendor. 2 13
The Bootstrapper
We found no public pricing information on the captured pages — no per-seat number for Vikunja Cloud, nothing on a free tier's limits, and enterprise support packages offered with no figures. The only cost I can verify from these pages is the AGPLv3 license itself, which makes the self-hosted path free software on infrastructure I pay for; for the hosted service a card-carrying buyer has nothing to go on. 1 2 13
The Enterprise Architect
We found no public information on prices for the hosted cloud tiers or the enterprise support packages; the captured monetization is sponsorship channels and an invitation to email about enterprise support. Self-hosted costs are governed by the AGPL license, which is transparent, but I cannot budget two hundred seats from the captured pages. 2 13
The UX Purist
We found no public pricing information on any captured page — no tier prices for the hosted cloud, and enterprise support and consulting are offered by email consultation. A buyer cannot read a payable number anywhere in the captured material, so no cost can be determined before talking to someone. 2 13
The Integrator
I found no public information on pricing for the hosted cloud or rates for the enterprise support packages, which are scoped by email — 'Send us an email to discuss your needs.' The one public cost structure is the AGPLv3 license under which the software itself can be self-hosted. 2 13
The Skeptic
Not one price appears on any captured page — not on the hosted cloud page, not beside the enterprise support packages that include SLAs and priority support. AGPL self-hosting is visible as a licence-free path, but a buyer cannot determine what the hosted service costs before contacting the vendor, and we found no public information on billing periods or tax treatment. 2 13
European sovereignty — proven facts
2 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined ⚠ unverified | — | uncited Report an error |
| Data residency | EU only ⚠ unverified | 3/3 pts | 5 Report an error |
| Subprocessors | EU only ⚠ unverified | 2/2 pts | 5 Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 15 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Ownership, Legal entity. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Data residency. The statement covers Vikunja Cloud hosting only and does not say where ancillary services such as newsletter email or support tooling are processed.
- Weak sourcing — Subprocessors. Only the hosting subprocessor is named; other potential processors of customer data such as email delivery, support, or payment are not disclosed.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- We found no public information on pricing on the pages we read (vikunja.io, vikunja.cloud, vikunja.io/privacy, vikunja.io/imprint, vikunja.io/security, vikunja.io/help/task-relations and 7 more). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 1 product fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
Sources (13)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage vikunja.io Checked 15 Sep 2026 Details →
- 2 Hosted cloud vikunja.cloud Checked 15 Sep 2026 Details →
- 3 Privacy policy vikunja.io Checked 15 Sep 2026 Details →
- 4 Imprint vikunja.io Checked 15 Sep 2026 Details →
- 5 Security / trust page vikunja.io Checked 30 Sep 2026 Details →
- 6 Collaboration depth — found from sitemap vikunja.io Checked 1 Oct 2026 Details →
- 7 Reporting — found from sitemap vikunja.io Checked 1 Oct 2026 Details →
- 8 Integrations — found from sitemap vikunja.io Checked 1 Oct 2026 Details →
- 9 Integrations — found from sitemap vikunja.io Checked 1 Oct 2026 Details →
- 10 Onboarding effort — found from sitemap vikunja.io Checked 1 Oct 2026 Details →
- 11 Onboarding effort — found from sitemap vikunja.io Checked 1 Oct 2026 Details →
- 12 Support & documentation — found from sitemap vikunja.io Checked 1 Oct 2026 Details →
- 13 Support & documentation — found from sitemap vikunja.io Checked 1 Oct 2026 Details →