vikunja
Vikunja is a self-hosted, open-source task management and to-do app written in Go with a Vue.js frontend. It allows teams and individuals to organize work without relying on third-party SaaS platforms, offering full control over data and deployment.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | go-vikunja/vikunja |
| Owner | go-vikunja |
| Primary language | Go |
| License | AGPL-3.0 — OSI-approved |
| Stars | 4.7k |
| Forks | 531 |
| Open issues | 207 |
| Latest release | v2.3.0 (2026-04-09) |
| Last updated | 2026-07-08 |
| Source | https://github.com/go-vikunja/vikunja |
What vikunja is
RESTful API-driven task manager built on Go backend with Vue.js UI, deployable via Docker or from source. Supports multi-user collaboration, custom workflows, and self-hosted infrastructure with AGPL-3.0 licensing.
Get the vikunja source
Clone the repository and explore it locally.
git clone https://github.com/go-vikunja/vikunja.gitcd vikunja# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- AGPL-3.0 copyleft obligations: any modifications or network-exposed derivative must be open-sourced; legal review strongly recommended before production use.
- Requires database backend (not specified in data; check documentation for supported databases) and reverse-proxy setup; Docker deployment simplifies initial roll-out.
- Multi-user authentication and authorization architecture exists but security posture requires independent audit; sensitive data encryption at rest/in-transit needs verification.
- API-first design enables custom UI frontends and integrations, but integration ecosystem scope is unclear from provided data.
- Active maintenance (last push July 2026, v2.3.0 current) with 207 open issues; evaluate issue resolution SLA against team expectations.
When to avoid it — and what to weigh
- Proprietary/closed-source requirement — AGPL-3.0 license requires derivative works and network-accessible deployments to open-source modifications. Commercial closed-source use is not permitted under this license.
- Enterprise SaaS support model expected — Vikunja is community-driven; no official enterprise support, SLAs, or commercial support contracts are indicated in the data.
- Lightweight standalone tool without infrastructure management — Self-hosting requires database, reverse proxy, and ongoing server administration. Not suitable for teams avoiding DevOps overhead.
- Deep integration with proprietary enterprise platforms — Known integrations with third-party SaaS platforms are not detailed in provided data; integrations require review.
License & commercial use
Dual-licensed: core repository AGPL-3.0-or-later; desktop app GPL-3.0-or-later. Background imagery from Unsplash under Unsplash License with photographer attribution requirements.
AGPL-3.0 is copyleft and incompatible with closed-source commercial deployments. Any internal use by a company as a network service requires making source code available to users under same license. Proprietary modifications or closed-source forks are NOT permitted. Commercial use requires explicit legal review and likely relicensing arrangement or strict compliance with copyleft obligations. Do not assume commercial use is permitted without legal counsel.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Moderate |
| DEV.co fit | Good |
| Assessment confidence | High |
No security audit, penetration test results, or vulnerability disclosure policy details provided beyond security contact link on website. AGPL copyleft design enables community code review. Self-hosting shifts security responsibility to operator (network hardening, database security, TLS/secret management, user authentication). Multi-user RBAC and data isolation mechanisms exist but independent security assessment required before handling sensitive organizational data.
Alternatives to consider
Nextcloud Tasks / Deck
Open-source (AGPL), self-hosted, part of larger ecosystem; lacks Vikunja's Go simplicity and dedicated task UX, but broader calendar/file integration.
OpenProject
Open-source project management (GPL), self-hosted, enterprise features; heavier than Vikunja with more overhead but stronger compliance/reporting.
Plane (Foss)
Modern open-source issue/task tracker; less mature than Vikunja, different UX; strong GitHub integration for dev teams.
Build on vikunja with DEV.co software developers
Review the installation docs, test the demo at try.vikunja.io, and consult your legal team on AGPL-3.0 obligations before production deployment.
Talk to DEV.coRelated on DEV.co
Explore the category and the services that help you build with it.
vikunja FAQ
Can we use Vikunja commercially in a closed-source product or as a proprietary SaaS?
What databases does Vikunja support?
Is there professional support, SLA, or enterprise license available?
What is the security posture and has it been audited?
Software development & web development with DEV.co
DEV.co is a software development agency delivering custom software development services to companies building on open source. Our software developers and web developers design, integrate, and ship production systems — spanning web development, APIs, AI, data, and cloud. If vikunja is part of your open-source devops roadmap, our team can implement, customize, migrate, and maintain it.
Ready to evaluate Vikunja for your team?
Review the installation docs, test the demo at try.vikunja.io, and consult your legal team on AGPL-3.0 obligations before production deployment.