What it is

Vikunja is a self-hosted task and project management application that carries the tagline "The task manager you actually own." It lives in the Go and Vue.js ecosystem: the backend is written in Go, the frontend uses Vue.js, and the project ships a documented OpenAPI interface with Swagger docs published against the hosted demo instance. The repository sits on GitHub under the go-vikunja organization, is licensed AGPL-3.0-or-later across most of the codebase with the contents of desktop/ under GPL-3.0-or-later, and is published as the Docker image vikunja/vikunja with the current release marked as v2.6.0.

The concrete problem it solves is ownership of task data and workflow definition. Commercial task managers in this space — Jira, Linear, Trello, ClickUp, Monday.com, and Asana — all position Vikunja as the open alternative, and the project's topic list names self-hosted, todo, todoapp, and todolist directly. Teams and individuals who want boards, lists, and project tracking but who do not want their work items held by a vendor can run Vikunja on their own infrastructure, wire it into other systems through the API, and keep the deployment under their own control.

Key capabilities

• Task and project management with boards, lists, and to-do tracking, as named in the repository topics.
• REST API with OpenAPI documentation, published as Swagger docs against a live instance at try.vikunja.io/api/v2/docs.
• Self-hosted deployment, with the official Docker image published on Docker Hub as vikunja/vikunja.
• Go backend with a Vue.js frontend, both visible in the language and topic metadata.
• Roadmap and issue tracking dogfooded on Vikunja itself, hosted at my.vikunja.cloud.
• Build-from-source and development workflows, documented through a Magefile, a development setup guide, and a testing guide.
• Desktop client code kept in a separate desktop/ directory under its own GPL-3.0-or-later license.

Who uses it and how

• Individuals and teams replacing commercial task managers who want their task data on infrastructure they control.
• Self-hosters running the vikunja/vikunja Docker image in their own environment.
• Developers integrating task creation and tracking into other tools through the documented API.
• Contributors building from source, following the development setup, Magefile, and testing documentation.
• Users evaluating the product on the public demo at try.vikunja.io before deploying.

Getting started

Install documentation lives at vikunja.io/docs/installing, and the README advertises the `vikun