Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 3 of 6 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? →

Link to this page

Vikunja: AI-assisted analysis on whats-best.ai Vikunja: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

Vikunja at a glance

Vendor
Vikunja (open source)
Headquarters
Not stated on the vendor’s pages as of 16 Nov 2026
Data hosting
In the EU by default source, captured 16 Nov 2026
Free plan
Not stated on the vendor’s pages as of 16 Nov 2026
Panel verdict
The AI panel rates Vikunja 3/5, the mean of 6 judges. Vikunja is open-source task management with lists, Kanban, Gantt and Table, self-hostable under the AGPLv3 or available as Vikunja Cloud from German controller Konrad Langenberg Software of Lübeck. how scores are made
As of
Vendor pages captured 15 Sep 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources

Vikunja alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The panel's verdict

Vikunja is open-source task management with lists, Kanban, Gantt and Table, self-hostable under the AGPLv3 or available as Vikunja Cloud from German controller Konrad Langenberg Software of Lübeck. It is strongest on onboarding effort, low and high both at 7, backed by a public demo at try.vikunja.io whose data is wiped every 24 hours and importers that pull Todoist or Trello work in minutes. Integrations score 6-7 on documented webhooks with HMAC-SHA256 signing, a Swagger-documented API, CalDAV, an MCP surface for AI clients and importers from Todoist to WeKan with custom migrators. Weakest are pricing transparency at 2-3 — the captured pages name a cloud and a Pro tier but no figures — and reporting at 4 low and high alike, a dashboard with no public information on time tracking, budgets or utilization. The genuine split is sovereignty, 5 to 7: judges weighed Hetzner hosting in Germany and Finland and the AGPLv3 self-host route against a privacy policy that commits only 'generally' to EU processing, contemplates SCC or EU-US Data Privacy Framework transfers, and has no public DPA we could find.

Report an error

Speaks for it

  • Onboarding effort scores 7 at both ends of the range, on a public demo at try.vikunja.io whose data is wiped every 24 hours and Todoist, Trello or Microsoft To Do imports.
  • Integrations score 6-7 on HMAC-SHA256-signed webhooks across twenty project event types and three user events, a Swagger-documented API, CalDAV, an MCP surface and custom migrators.
  • Collaboration depth scores 6-7 on project sharing to a single user, a team or a link share, with assignments, comments and eleven task-relation types including blocking and blocked-by.
  • The self-hosted path is free of licence fees, open source under the AGPLv3 and run on your own infrastructure.
  • Vikunja Cloud is hosted at Hetzner in Germany and Finland in ISO 27001-certified data centers, under a named German controller, Konrad Langenberg Software of Lübeck.

Report an error

Held against it

  • Pricing transparency scores 2-3: the captured pages name Vikunja Cloud and a Pro tier with no price figures, billing periods or tax treatment.
  • Reporting scores 4 low and high alike, a dashboard and saved filters with no public information on time tracking, budgets or utilization.
  • Webhooks are delivered once with no retries on failure, flagged by judges as a trap for production wiring.
  • The privacy policy commits only 'generally' to EU processing while contemplating transfers under standard contractual clauses or the EU-US Data Privacy Framework, and we found no public information on a DPA or a subprocessor list.
  • Support channels are a community forum and Matrix chat, with SLAs and priority support reserved for enterprise packages.

Report an error

Best for

  • Your team can run its own server and wants AGPLv3 software on its own infrastructure, which removes the vendor from the data path.
  • You are migrating from Todoist, Trello or Microsoft To Do and want documented importers plus a credible API-based exit path.
  • You want to evaluate hands-on before any commitment, via the public demo whose data is wiped every 24 hours.
  • You are comfortable building your own connectors — webhooks, API tokens, CalDAV, MCP and custom migrators are documented, while we found no public information on native Slack or Teams apps.

Report an error

Avoid if

  • You need a budget-ready figure for the hosted option before contacting the vendor — ask the vendor: the public pages we read do not show it
  • Your managers need time, budget or utilization reporting — reporting scored 4 with no public information on any of these.
  • You plan team capacity and need workload or capacity views — collaboration rationales found no public information on them.
  • You must have a data processing agreement and subprocessor list in hand before signing — we found no public information on either.

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median
Collaboration depth 3 of 5
Reporting 2 of 5
Integrations 3.5 of 5
Onboarding effort 3.5 of 5
European sovereignty 3.5 of 5
Support & documentation 3.5 of 5
Pricing transparency 1.5 of 5

Collaboration depth

Show 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.

Report an error

The Data Protection Officer

Projects can be shared with individual users, teams or link shares, tasks carry assignees, comments, labels and attachments, and eleven relation types including blocking and blocked-by provide genuine dependency handling alongside a Gantt planning view. Cross-project visibility runs through saved filters rather than dedicated portfolio views, and we found no public information on workload or capacity planning. 12 6 1 12

Report an error

The Bootstrapper

Sharing is real, not bolted on: you can share a project with a single user, a team, or a link share, assign tasks, and link work with eleven relation types including blocking and blocked-by, viewable as list, Kanban, table or Gantt, with saved filters giving cross-project views. We found no public information on workload or capacity planning, which keeps this short of first-class team-level planning. 1 12 6 12

Report an error

The Enterprise Architect

Projects are genuinely shared — assignments, comments, labels, attachments, team and link-share access, and eleven task-relation types including blocking and precedes — with cross-project visibility through saved filters plus Gantt, table and kanban views. Permissions even have their own help topic. We found no public information on workload or capacity views, which is exactly what a two-hundred-seat rollout needs to plan against. 6 12 1 12

Report an error

The UX Purist

Assignments, comments, labels and attachments live on tasks, projects share to a single user, a team or a link share, and eleven relation types — blocking, blocked-by, subtask — automatically write their opposite on the linked task. Gantt gives a timeline per project and saved filters stretch across projects, but we found no public information on any workload or capacity view, so team planning stops one level short. 12 6 12 1

Report an error

The Integrator

Shared projects with assignees, comments, team sharing and link shares are all documented, eleven task relation types including blocking and blocked-by are first-class, and Gantt gives a real shared timeline with cross-project saved filters on top. What the captured pages don't show is any workload or capacity view, so I can't place team planning above solid-but-gapped. 6 12 1 12

Report an error

The Skeptic

Shared projects with team and user sharing, link shares for guests, assignments, comments and eleven task-relation types including blocking give real multi-person planning, with a Gantt timeline as the team planning view. The only cross-project device documented is a saved filter, and we found no public information on workload or capacity views. Solid multi-person work, but capacity planning is nowhere visible in what we read. 12 6 12 1

Report an error

Reporting

Show 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.

Report an error

The Data Protection Officer

The documentation shows a dashboard of upcoming and recent work, a dedicated Upcoming view with date-range, overdue and no-date controls, and saved filters that can aggregate across projects — more than fixed per-project status views. Beyond a copy-as-markdown option and general data import/export for portability, we found no public information on time, budget or utilization reporting or on dedicated report exports. 7 12 12

Report an error

The Bootstrapper

The dashboard aggregates overdue and upcoming work across projects and saved filters act as persistent cross-project views, with import/export and copy-as-markdown to move data out. But we found no public information on time, budget, or utilization reporting — this reads as a personal progress surface rather than a management one. 7 12

Report an error

The Enterprise Architect

What is documented is a personal dashboard with overdue-first sorting, saved filters, and a Copy as Markdown action — lenses for one person, not reporting. We found no public information on time tracking, budgets, utilization or exportable aggregate reports. A budget owner will not get their answers out of this. 7 12 12

Report an error

The UX Purist

The dashboard answers a personal question — what is due — with overdue first and closest due date on top, saved filters can pull one view across projects, and Copy as Markdown plus a general export path get data out. We found no public information on time tracking, budgets, utilization or scheduled reports, so the reporting layer is a lens on your own tasks rather than an instrument panel for the work. 7 12 12

Report an error

The Integrator

What's documented is a dashboard of upcoming and recent work, saved filters that can cut across projects, and a Copy as Markdown escape hatch — I found no public information on time tracking, budget or utilization reporting, nor on scheduled or structured report exports. That's personal visibility, not a surface that answers team-level questions. 7 12

Report an error

The Skeptic

The documented reporting surface is a dashboard of upcoming and overdue work plus saved filters that can span projects, with export via the Vikunja file export and Copy as Markdown. We found no public information on progress, time, budget or utilization reporting, or on CSV report export. That is a personal overview screen, not management reporting. 7 12 12 11

Report an error

Integrations

Show 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.

Report an error

The Data Protection Officer

The webhook surface is deep — twenty project event types plus user events, HMAC-SHA256 signed payloads, API management with SSRF protection and proxy configuration — and it sits next to API token authentication with Swagger-documented endpoints, CalDAV, an MCP surface for AI clients, and importers from Todoist, Trello, Microsoft To Do, Planka, TickTick, WeKan and CSV with documented custom migrator development. We found no public information on native Slack, Teams or automation-platform connectors. 8 9 11 12

Report an error

The Bootstrapper

The API is documented (API tokens, JWT, Swagger) and webhooks cover twenty project and three user event types with HMAC-SHA256 signing; importers pull from Todoist, Trello, Microsoft To Do, Planka, TickTick, WeKan and CSV, and custom migrators can be developed. CalDAV and an MCP surface for AI clients round it out. We found no public information on native Slack- or Teams-style app integrations or automation-platform support. 8 9 11 12

Report an error

The Enterprise Architect

The connective tissue is unusually serious for this category: a Swagger-documented API with tokens, signed webhooks for project and user events with HMAC verification and SSRF protection, MCP for AI clients, CalDAV, and migration paths from Todoist, Trello, Microsoft To-Do, TickTick, WeKan, Planka and CSV, with custom migrators developable in-house. We found no public information on native connectors for chat or file-storage services or on automation-platform support. The API-based exit path is credible, which matters to me. 11 8 9 12

Report an error

The UX Purist

The webhook surface is documented the way an engineer means it: twenty project event types plus three user events, HMAC-SHA256-signed payloads, API-token or JWT auth, SSRF protection, configurable timeouts and proxies, all manageable through a Swagger-documented API. Eight import sources from Todoist to WeKan plus a documented route to write your own migrator, CalDAV and an MCP surface for AI clients round it out; we found no public information on native Slack, Teams or automation-platform connectors. 9 8 11 12

Report an error

The Integrator

This is where the product earns its keep: project and user webhooks with around twenty project event types, HMAC-SHA256 signed payloads, full API management via tokens and Swagger docs, and real migrators from Todoist, Trello, Microsoft To Do, TickTick, WeKan, Planka and CSV, with custom migrators writable and MCP opening AI clients to the data. Webhooks are documented as delivered once with no retry, and I found no public information on native Slack, Teams or automation-platform connectors — that keeps it short of ecosystem-grade. 8 11 8 9 12

Report an error

The Skeptic

Webhooks are genuinely documented — project and user types, a long event catalogue, HMAC-SHA256 signing, API-managed via Swagger — alongside CalDAV, an MCP surface for AI clients and real importers from Todoist, Trello, TickTick, WeKan and others. We found no public information on Slack, Teams or automation-platform integrations. And note the trap: webhooks are delivered once with no retries on failure, which will bite anyone wiring this into production. 8 9 12 11

Report an error

Onboarding effort

Show 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.

Report an error

The Data Protection Officer

A public demo instance whose data is automatically deleted every twenty-four hours, an install path described as taking minutes across Linux, FreeBSD, Kubernetes and Helm, and imports that pull existing work in from Todoist, Trello or Microsoft To Do in minutes point to fast time-to-value. We found no public information on guided setup, templates, or whether the cloud trial requires payment details. 14 2 3 11

Report an error

The Bootstrapper

A demo instance with 24-hour data deletion lets you try without payment details, self-hosting is advertised as minutes across Linux, Kubernetes and Helm, and importers pull Todoist, Trello or Microsoft To Do tasks in minutes. Friction remains: OAuth imports need the public URL set correctly and LAN imports need a config flag, and we found no public information on guided setup or project templates. 14 2 3 11

Report an error

The Enterprise Architect

Self-hosting is positioned as minutes across Linux, FreeBSD, Kubernetes and Helm, and a public demo resets every twenty-four hours with no payment details documented. Imports from Todoist, Trello and Microsoft To-Do are advertised in minutes, though the migration docs warn the process can take several hours for large accounts. Someone still has to pick an install path and stand up a server, so the first hour belongs to an engineer, not a newcomer. 2 11 3 14

Report an error

The UX Purist

Time-to-first-value looks genuinely short: a public demo at try.vikunja.io with data wiped every 24 hours and no signup wall, a quick-add bar on the dashboard whose inline syntax sets dates, labels and priorities as you type, and importers that pull Todoist, Trello or Microsoft To-Do work in minutes. A configurable default project is the right kind of sensible default; we found no public information on guided setup flows, templates, or whether the cloud trial asks for payment details. 3 7 2 11

Report an error

The Integrator

A demo instance wipes itself every 24 hours so a team can evaluate before any signup, quick-add magic syntax captures details without configuration, and importers pull Todoist, Trello or Microsoft To Do data in minutes. The self-host path promises setup in minutes but assumes someone comfortable with Linux, Docker, Kubernetes or Helm, and I found no public information on templates or guided setup flows. 2 7 14 3 14

Report an error

The Skeptic

Self-hosting is documented as minutes-to-setup across Linux, FreeBSD, Kubernetes and Helm, a public demo at try.vikunja.io wipes its data every 24 hours, and importers pull existing Todoist or Trello work in. The fine print tempers the promise: OAuth imports need the public URL set correctly and can take up to several hours depending on account size, and the Planka importer trips over SSRF protections on local-network installs. Same-day start for most teams, but not the frictionless hour the marketing implies. 14 3 2 11

Report an error

European sovereignty panel opinion

Show 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.

Report an error

The Data Protection Officer

The controller is a German entity, Konrad Langenberg Software of Lübeck, the security page states that all parts of Vikunja Cloud are hosted at Hetzner in Germany and Finland, data processors are to be bound by Art. 28 GDPR contracts, and the AGPLv3 licence with a self-hosting option offers a path where residency is entirely the buyer's. Against that, the privacy policy commits only "generally" to EU servers while contemplating third-country transfers under standard contractual clauses or the EU-US Data Privacy Framework — GitHub sign-in sits in San Francisco — and we found no public information on a DPA or a subprocessor list. 3 5 4 1

Report an error

The Bootstrapper

The controller is Konrad Langenberg Software in Lübeck with a German VAT ID, Vikunja Cloud runs at Hetzner in Germany and Finland with ISO 27001-certified data centers, and the AGPLv3 software can run entirely on your own infrastructure. The privacy policy commits only 'generally' to EU processing and explicitly contemplates third-country transfers with SCC or Data Privacy Framework safeguards, and we found no public data processing agreement or subprocessor list on the captured pages. 4 3 5 1

Report an error

The Enterprise Architect

The controller is Konrad Langenberg Software of Lübeck with a German VAT ID, all of Vikunja Cloud runs at Hetzner in Germany and Finland with ISO 27001-certified data centers, processors are bound under Article 28, and a self-host route under an AGPL license removes the vendor from the data path entirely. The privacy policy commits only 'generally' to EU servers and expressly contemplates third-country transfers under standard contractual clauses or the EU-U.S. Data Privacy Framework, and we found no public information on a data processing agreement or a public subprocessor list. I would sign only once that paperwork exists. 1 4 5 3

Report an error

The UX Purist

A named German controller — Konrad Langenberg Software, Lübeck, with a German VAT number — runs Vikunja Cloud at Hetzner in Germany and Finland, publishes the code under AGPLv3 and lets you run the whole thing on your own infrastructure. The privacy policy commits only 'generally' to EU processing and explicitly contemplates transfers under standard contractual clauses or the EU-US Data Privacy Framework, and we found no public information on a DPA or a subprocessor list. 4 3 5 2 1

Report an error

The Integrator

The vendor is a German entity, Konrad Langenberg Software in Lübeck, and Vikunja Cloud runs at Hetzner in Germany and Finland with ISO 27001-certified data centers. But the privacy policy commits only 'generally' to EU servers while explicitly contemplating third-country transfers under SCCs or the EU-U.S. Data Privacy Framework, with GitHub sign-in a documented US touchpoint, and I found no public DPA in the captured pages. Self-hosting under the AGPLv3 is the strongest sovereignty play here — your infrastructure, your rules — and it lifts what would otherwise be compliance paperwork. 1 4 5 3

Report an error

The Skeptic

The entity is German — Konrad Langenberg Software, Lübeck, with a German VAT ID — Vikunja Cloud runs at Hetzner in Germany and Finland under ISO 27001, and the AGPLv3 self-host path is the ultimate residency guarantee. But the privacy policy commits only 'generally' to EU servers while explicitly contemplating third-country transfers under standard contractual clauses or the EU-U.S. Data Privacy Framework, with GitHub sign-in one such U.S. service. We found no public DPA and no subprocessor list, so the residual exposure is asserted away rather than disclosed. 4 5 3 1

Report an error

Support & documentation

Show 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.

Report an error

The Data Protection Officer

A help center covering twenty-one topics from task relations to MCP, alongside technical documentation for server setup, API details and development guides, reads current and deep. The support channels named on the captured pages are the community forum and Matrix chat, with SLAs, priority support and direct developer access reserved for enterprise packages, and we found no public information on published response times or a visible changelog. 12 13 12 14

Report an error

The Bootstrapper

The help center covers twenty-one topics from core tasks through webhooks, MCP and accessibility, backed by technical documentation for server setup, API details and development guides that track current versions, plus an open community forum and Matrix chat. Paid consulting, training, migration help and enterprise packages with SLAs and priority support exist. We found no public information on vendor-run chat with published response times on standard plans, or on a visible changelog. 12 12 13 14

Report an error

The Enterprise Architect

The help center covers the core product from permissions and task relations to webhooks and accessibility, with separate technical documentation for server setup, API details and development guides, a community forum and Matrix chat, plus paid enterprise packages offering SLAs, priority support and direct developer access. We found no public information on response times, a visible changelog, or vendor-run support outside the community channels and the paid packages. Acceptable for a pilot, thin for production assurance. 12 13 12 14

Report an error

The UX Purist

Twenty-one named help topics from Quick Add Magic to Webhooks, separate technical docs for server setup, API and development, and webhook pages that cite version numbers — documentation that teaches the product instead of selling it. Humans come as a community forum, Matrix chat and email consulting, with SLAs reserved for an enterprise package; we found no public information on response times for ordinary users or a visible changelog. 12 12 9 13 14

Report an error

The Integrator

The help center covers twenty-one topics from accessibility to webhooks, technical documentation handles server setup, API details and development guides, and the webhook pages show signature headers, retry semantics and SSRF defaults — that is current, deep documentation. Support is community-first via forum and Matrix chat, with email-based consulting, migration assistance and an enterprise tier promising SLAs and priority support, but I found no published response times and no changelog. 12 13 14 12

Report an error

The Skeptic

The help center covers some twenty topics from tasks to webhooks, backed by separate technical documentation and Swagger API references, and the docs are version-stamped in a way that reads as actively maintained. Support on ordinary terms is a community forum and Matrix chat, with setup, training, migration help and enterprise SLAs sold only through an email exchange. We found no public information on response-time commitments for non-enterprise users. 12 13 14 8

Report an error

Pricing transparency

Show 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.

Report an error

The Data Protection Officer

The captured pages name Vikunja Cloud, a Vikunja Pro tier and enterprise support packages but give no price for any of them, so a buyer cannot determine the payable cost of the hosted offering from this documentation. The AGPLv3 licence does make the self-hosted path free of licence fees. 14 13 2 1

Report an error

The Bootstrapper

Self-hosting is the transparent route: the software is open source under the AGPLv3, so there is no license fee to discover. But we found no price figures, billing periods, or seat terms on the captured pages for hosted Vikunja Cloud or Vikunja Pro — as a buyer I cannot total the hosted cost at three or thirty seats from what was captured. 14 2 1

Report an error

The Enterprise Architect

The captured pages name a hosted cloud and a Pro tier and stop there; we found no public information on prices, seat minimums, billing periods or tax treatment for either. I cannot budget two hundred seats against a button that reads 'Get Vikunja Pro'. 2 14 14

Report an error

The UX Purist

The self-hosted path is priced by the AGPLv3 license — read the code, run it yourself — but we found no price figures on the captured pages for Vikunja Cloud or the Pro tier: no per-seat number, no billing period, no tax treatment. A buyer sizing the hosted option gets a button that says 'Get Vikunja Pro' and nothing to put in a budget. 14 14 2 1

Report an error

The Integrator

The captured pages show a hosted cloud offering and a 'Get Vikunja Pro' tier, but I found no public price for either anywhere I read. The self-hosted route is fully determinable — open source under the AGPLv3, run on your own infrastructure — so the cost question only stays open for the hosted offering. 1 2 14

Report an error

The Skeptic

The captured pages name a Pro tier and a hosted cloud but attach no figures, billing periods or tax treatment to either. The one cost that is plain is the self-hosted software itself, open-source under AGPLv3, with support and consulting quoted only after an email conversation. A buyer cannot price the paid offering from anything we read. 14 14 13 1

Report an error

European sovereignty — proven facts

3 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location EU by default unverified
Why unverified?

The privacy policy only commits 'generally' to EU servers and explicitly contemplates transfers to third countries and to U.S. services, while the security page separately states that Vikunja Cloud itself is hosted at Hetzner in Germany and Finland.

2/4 pts 3 Report an error
Hosting options Self-hostable 1/1 pts 1 Report an error
Open source Not determined unverified
Why unverified?

Not confirmed on the vendor’s own pages as captured.

— uncited Report an error
Data processing agreement Not determined — uncited Report an error
Transfer impact assessment Not needed, no transfer outside the EU/EEA unverified
Why unverified?

The sentence addresses Vikunja Cloud hosting only and says nothing about subprocessors, support systems or other transfers.

1/1 pts 5 Report an error

Questions about Vikunja

Is Vikunja European?

Yes. whats-best.ai classifies Vikunja as EU-Made.

Where does Vikunja store data?

Vikunja stores customer data in the EU by default, though not exclusively, per the vendor’s page captured 16 Nov 2026.

Does Vikunja have a free plan?

Not stated on the vendor’s pages as of 16 Nov 2026.

What are the best alternatives to Vikunja?

As of 18 Nov 2026, the panel rates Kantree (4/5), awork (4/5) and InLoox (3.5/5) highest among the other 72 Project Management & Collaboration products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Kantree (EU-Made, France). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Vikunja alternatives.

Where this could be wrong

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.

Sources (14)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage vikunja.io Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 15 Sep 2026 Details →
  2. 2 Hosted cloud vikunja.cloud Checked 16 Nov 2026 Details →
  3. 3 Privacy policy vikunja.io Checked 16 Nov 2026 +1 earlier capture: 15 Sep 2026 Details →
  4. 4 Imprint vikunja.io Checked 16 Nov 2026 Details →
  5. 5 Security / trust page vikunja.io Checked 16 Nov 2026 Details →
  6. 6 Collaboration depth — found from sitemap vikunja.io Checked 16 Nov 2026 Details →
  7. 7 Reporting — found from sitemap vikunja.io Checked 16 Nov 2026 Details →
  8. 8 Integrations — found from sitemap vikunja.io Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
  9. 9 Integrations — found from sitemap vikunja.io Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
  10. 10 Onboarding effort — found from sitemap vikunja.io Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 1 Oct 2026 Details →
  11. 11 Onboarding effort — found from sitemap vikunja.io Checked 16 Nov 2026 Details →
  12. 12 Support & documentation — found from sitemap vikunja.io Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
  13. 13 Support & documentation — found from sitemap vikunja.io Checked 16 Nov 2026 Details →
  14. 14 Self-hosting / on-premises installation docs — found from the homepage vikunja.io Checked 16 Nov 2026 +1 earlier capture: 1 Nov 2026 Details →