Vikunja

What Vikunja actually is

Vikunja is the open-source, self-hostable to-do app for people who want a task manager they actually own. It sits in the space normally occupied by Todoist, with some overlap into Linear for teams that need a more structured place to track work without handing their task database to another SaaS vendor. The pitch is straightforward: run Vikunja yourself, use the official cloud, and keep your tasks in a system you control. That makes it a plausible fit for individuals, small teams, and technically comfortable organizations that want a Todoist-like alternative without accepting that every checkbox needs a subscription account attached to it.

Live GitHub stats

Vikunja has 5,298 stars on GitHub and is licensed under AGPL-3.0. Its primary language is Go, and the repository’s last push was 2026-09-06. There are 226 open issues. Taken together, those numbers suggest a project with real adoption and ongoing development, but not one that has reached the boring, finished-product stage where nobody needs to file bugs anymore. The issue count is not automatically a problem; it is simply a reminder that popularity and polish are different measurements.

The GitHub description is “The task manager you actually own,” which is a better summary of the project’s value proposition than most open-source product copy manages. The meaningful signal here is not just the star count. It is that Vikunja has enough visibility to be considered a serious alternative while still being aimed at users who care about hosting and ownership.

What it's good at

Vikunja’s strongest use case is replacing a conventional task manager without requiring a philosophical conversion into project-management theater. If Todoist is the SaaS product you are trying to get away from, Vikunja gives you the obvious open-source path: a dedicated task manager that can be self-hosted instead of rented indefinitely. That matters for people who want their task data on their own infrastructure, need control over retention, or simply dislike the modern habit of turning basic personal organization into a recurring charge.

It also makes sense as a lighter alternative to Linear when the real requirement is tracking work rather than adopting an entire product-development workflow. That distinction is important. Vikunja’s stated identity is a task manager, not a claim that it reproduces every specialized planning and collaboration feature of Linear. If your team needs a flexible place for tasks and wants the deployment and data model under its own control, it is worth evaluating. If what you want is Linear’s complete opinionated workflow, pretending the two products are interchangeable would be the usual open-source comparison slop.

The project’s appeal is therefore less about promising a magical “everything app” and more about making ownership a first-class option. You can use the official cloud when convenience wins, or self-host when control matters more. That two-track model gives Vikunja a wider audience than a project that only works for people willing to maintain every part of the stack themselves.

What to watch for

The first thing to understand is the AGPL-3.0 license. This is an open-source license, but it is deliberately protective of users’ ability to receive corresponding source when modified software is offered over a network. That is a feature for some organizations and a legal-review trigger for others, especially if Vikunja is embedded into a larger hosted product or materially modified for internal or external users. Deployment difficulty is rated 2 out of 5, so this is not being presented as a particularly painful self-hosting project, but “easy enough to deploy” still means someone owns updates, backups, authentication, availability, and troubleshooting. The last push date, 2026-09-06, is a positive maintenance signal, while the 226 open issues show that active development does not mean every rough edge has already been sanded down.

How to deploy

Vikunja is available through both self-hosting and the official cloud. For the self-hosted route, Docker or Docker Compose is the practical expectation for many small deployments, assuming you already have a server and a reverse proxy setup you are comfortable maintaining. The official cloud removes most of that operational work and is the sensible choice if your priority is using the application rather than running it. For deployment details, configuration notes, and the supported paths, see the Vikunja deployment guide.

Related tools

• Looking for more open-source alternatives to Todoist? Browse the Todoist alternatives page.
• Comparing self-hostable options against Linear? See the Linear alternatives page.