Vikunja is the kind of productivity story the subscription economy didn’t want: a fully open-source, self-hostable task manager that replicates many of Todoist’s best features without a recurring vendor lock‑in—and with an official hosted option that costs roughly what a coffee costs each month. For users and small teams tired of paying for “premium” checkboxes, Vikunja promises control of your data, familiar task-management primitives (lists, Kanban, Gantt, filters, recurring tasks), and multiple hosting paths: run it yourself on a VPS or Raspberry Pi, deploy with Docker/Kubernetes, or buy a managed Vikunja Cloud account for a small monthly fee. But the choice to leave Todoist isn’t purely financial: switching also trades a huge developer and integration ecosystem for greater privacy and ownership. This feature examines what Vikunja delivers today, how it compares to Todoist in practical terms, and the trade-offs — technical, operational, and community-related — you should weigh before migrating a live workflow.
Background / Overview
Vikunja began as an open-source project focused on speed, privacy, and flexible views for task data. The project’s frontend is written in
Vue.js and the codebase is maintained in a single monorepo that includes API, frontend and desktop/packaged clients; the team explicitly describes the main repo as go-vikunja/vikunja and documents development and release activity there. The project is licensed under the
GNU Affero General Public License (AGPL‑3.0) for the web frontend and API, a deliberate choice that preserves user freedoms and requires downstream network deployments to publish source changes under the same terms. The project changelog and frontend repositories reflect that license decision. Vikunja offers two broad consumption models:
- Self‑hosted: deploy the official images or build from source and run on your hardware, cloud VM, or in Kubernetes.
- Hosted: subscribe to Vikunja Cloud (entry personal plans advertised at ~€4–5/month), an official managed offering that funds development while keeping the core product open-source.
What Vikunja actually offers — features and technical basics
Core task features (what you get out of the box)
Vikunja packs the task primitives users expect — not as gated features — including:
- Recurring tasks, subtasks, priorities, due dates, and reminders (email reminders supported).
- Labels / tags, task attachments, and task relationships to link related items.
- Multiple views: list, Kanban, table, and Gantt chart.
- Smart filters and saved filters for complex queries and dashboards.
- Collaboration: namespaces/projects, shareable projects, role-based team access and per-task assignees.
- CalDAV integration so many calendar and tasks apps can synchronize with Vikunja.
These are the same features many people pay a subscription for in SaaS offerings; Vikunja exposes them as part of the open-source product, with the caveat that some advanced workflow conveniences (extensive third‑party integrations, polished mobile clients) are still catching up.
Architecture and supported platforms
- The project is a unified stack with an API backend (Go-based tooling in the go-vikunja ecosystem) and a Vue.js frontend. The main repo houses API, frontend, and desktop shells; maintainers provide Docker images, Helm charts, and example Docker Compose setups.
- Official Docker images and Helm charts simplify deployment; supported databases include SQLite, PostgreSQL and MySQL/MariaDB, with recommended database versions documented on the official site. Redis is optional for caching.
- Multi‑platform packaging: an Electron-based desktop build and a cross‑platform “app” repo exist, and the frontend can be used as a PWA for mobile access. The project also publishes community-maintained images for ARM/arm64, enabling Raspberry Pi deployments—though historically this required specific tags and attention to image variants.
Importing from Todoist, Trello, Microsoft To‑Do
Migration tooling is a first-class feature. Vikunja provides built-in importers and explicit migration guides for
Todoist, Trello, and Microsoft To‑Do, with OAuth flows and background import processing described in the docs. The Todoist migrator and Trello/Microsoft options require app registration or configuration for OAuth redirect URIs when self-hosting. Migration is typically straightforward but can take longer for large accounts.
How Vikunja compares to Todoist — strengths
1) Ownership and privacy (the decisive advantage)
When you self-host Vikunja, your tasks live on infrastructure you control. There’s no vendor lock‑in for core data, and the AGPL licensing ensures transparency into code and behavior. For people who prioritize data governance — freelancers, researchers, privacy-conscious users, small businesses — that control is a real operational and ethical win. The official site explicitly frames Vikunja as a project that “will never look at your tasks,” and the hosted plan exists to support development rather than harvest data.
2) Feature parity for everyday task work
Vikunja supports recurring tasks, subtasks, filters, priorities, attachments, and calendar syncing — everything most individuals need from a daily task manager — without pushing a paywall. The list/Kanban/Gantt/table parity is unusual in open-source task apps and makes Vikunja flexible across many workflows.
3) Cost structure and sustainability
If you self-host, the software is freely available indefinitely. If you prefer a hosted solution, the official Vikunja Cloud personal plan is priced to be modest (≈€4/month personal / €5/user for organizations), which is cheaper or on par with many competing SaaS products and supports continued project maintenance. Using the hosted plan is an economical trade-off for people who value convenience but still prefer an open-source product.
Real risks and limitations — what reviewers and users consistently report
1) Integration and polish gaps
Vikunja’s ecosystem is smaller than Todoist’s. That means fewer first‑party integrations, fewer polished mobile clients, and less third‑party plugin coverage. The official importers and CalDAV bridge a lot of gaps, but if you rely on deep integrations (Zapier, Slack apps, hundreds of productivity tools), you might hit limits or need to DIY an integration using the API. Official docs show supported imports, but the broader ecosystem is a work in progress.
2) Mobile experience — mixed reports
Although Vikunja ships a cross‑platform app and supports PWA usage, community threads indicate
mobile syncing and client stability—particularly on iOS—can be uneven. Many self-hosters combine Vikunja with CalDAV clients (Tasks.org on Android) to achieve reliable push/reminder behavior, but native mobile parity with Todoist’s polished apps is not universal. If mobile-first UX is critical, plan to test workflows on your devices before migrating.
3) Bulk editing / large-scale operations
Some active users report painful workflows when performing bulk moves or edits; a limited bulk-edit UI has been raised as a long‑running request in community threads. For organizations migrating large historic task sets, this limitation can create friction unless you script changes with the API. That trade-off is material: without bulk operations, reorganizing existing tasks may be tedious.
4) Self-hosting responsibility
Self-hosting removes subscription fees but adds operational responsibilities: TLS, backups (database + attachments), updates, security patching, and monitoring. The docs provide backup and Docker examples, and the product supports easy deployment patterns—but you’re now responsible for availability, performance, and security. That’s a benefit for control, but a potential hazard for teams lacking ops experience.
5) Raspberry Pi & ARM edge cases
Running Vikunja on small ARM devices (Raspberry Pi) is possible and frequently done, but community threads document image selection, exec-format errors, and occasional Alpine base-image quirks. The project publishes Linux/ARM build targets in CI, but real-world Pi deployments occasionally require specific image tags or small troubleshooting steps. Plan to validate the image architecture and test before committing to Pi for production.
Technical checklist for WindowsForum readers (practical migration guide)
Pre-migration: inventory and decide
- Audit your current Todoist usage: which projects, labels, recurring rules, reminders, and integrations are critical?
- Identify mobile clients and any automation (IFTTT/Zapier) that you rely on.
- Estimate attachment storage needs — Vikunja Cloud personal plan includes 10GB attachments; self-hosting requires you to size storage accordingly.
Choose a hosting model
- Self-host (Docker Compose / Helm / plain binary): best for control and zero software subscription.
- Managed Vikunja Cloud: best for low maintenance and fast setup; priced per user for organizations.
Quick self-hosted steps (Docker Compose)
- Prepare a host (VPS, local server, or Pi). Ensure Docker and Compose are installed.
- Pick a database: SQLite for tiny single‑user setups, PostgreSQL or MariaDB for multi‑user production.
- Use the project's “full docker example” compose file, configure VIKUNJA_SERVICE_PUBLICURL and JWT secrets, mount a persistent files volume for attachments. Restart and watch logs. The docs include a tested Compose example and explicit file-permission notes.
Migration
- Register a Todoist app (for self-hosting), configure OAuth redirect URI per Vikunja docs.
- In Vikunja, go to Settings → Import from other services and start the Todoist/Trello/Microsoft importer.
- Verify imported tasks, labels, and dates; test recurring rules and reminders.
- If bulk reorganization is required, consider scripting with the API rather than relying on the UI.
Security & compliance considerations
- The codebase is open-source (AGPL): you can audit it and run it in environments that require code transparency.
- Self-hosted deployments must secure endpoints with TLS, rotate JWT secrets, and maintain database backups; Vikunja docs include explicit backup instructions for database and attachments.
- For organizations under privacy regulations (GDPR), the hosted Enterprise tier offers contractual data processing terms and dedicated instances.
Community maturity and support
Vikunja has an active core team and a community forum. The public repos, release notes, and Docker/Helm artifacts indicate ongoing development — including a recent desktop app release and active migration/import improvements in recent changelogs. Still, compared with Todoist’s commercial scale the community is smaller; expect community-driven support channels and issue-tracking rather than enterprise SLA-level support unless you buy an appropriate hosted plan. Community forum and subreddit threads reflect a pragmatic user base: many enthusiastic adopters praise the feature set and privacy model, while the most common criticisms center on mobile polish, bulk-edit functionality, and occasional deployment edge cases. These pattern-matched reports are valuable for planning but also show active issue triage and community-driven improvements.
Who should consider Vikunja — and who should not
- Choose Vikunja if:
- You want to own your task data or avoid monthly vendor lock‑in.
- You or your team can handle simple self-hosting operations, or you will pay for the modest hosted plan.
- You rely on lists, Kanban boards, Gantt views, and structured subtasks more than deep proprietary integrations.
- Reconsider Vikunja if:
- You need the broadest possible ecosystem of third‑party integrations and polished mobile apps without any trade-offs.
- You cannot accept manual operational overhead and prefer the convenience of SaaS SLAs.
- Bulk editing and enterprise-grade change-management workflows are mission‑critical today (unless you plan to script via the API).
Final verdict — a pragmatic recommendation
Vikunja is not merely “another to-do app”: it’s an intentionally open, developer-friendly alternative to subscription-based task managers. For privacy-minded users, small teams, or those who enjoy the control that self-hosting brings, Vikunja can reduce ongoing costs and remove data‑ownership anxieties while delivering robust task features that mirror much of Todoist’s day-to-day value. The official hosted plans make a compelling middle ground for people who want the convenience of managed hosting while still funding an open project.
That said, the trade-offs are real: a smaller ecosystem, occasional mobile and bulk-edit rough edges, and the operational responsibilities that come with self-hosting. Those trade‑offs are manageable and well documented, but they should be actively weighed against the convenience of a mature commercial SaaS if you depend on instant, polished cross-device behavior with extensive third‑party integrations.
For WindowsForum readers who value privacy and control, the pragmatic path is simple:
- Try the hosted Vikunja Cloud free trial to confirm UI and feature fit.
- If you like it, either keep the hosted plan or spin up a lightweight Docker Compose instance (SQLite for single user) and migrate a small project via the Todoist importer to validate reminders, recurring rules, and mobile behavior.
- Only migrate mission‑critical projects once you’ve validated push/reminder behavior and, if needed, scripted bulk adjustments via the API.
Vikunja is a mature, practical, and affordably hosted alternative to Todoist for users willing to accept a slightly smaller ecosystem in exchange for ownership, transparency, and a lower long‑term cost of ownership. For many workflow-conscious Windows users, that trade will feel less like sacrifice and more like finally putting the user — not the subscription — back in control.
Note: community discussion and forum threads corroborate user experiences with mobile clients and bulk-edit limitations; these first‑hand reports are valuable but reflect individual setups and can change as the project evolves. For the most recent release notes, release-specific fixes, and confirmed build artifacts (including ARM image tags), consult the project’s documentation and releases before deploying in production. For readers who want to experiment quickly, the documentation’s full Docker Compose example and migration guides contain step-by-step instructions to get a trial instance running in a few minutes. (Also: the broader discussion about ditching paid productivity subscriptions and migrating to open-source alternatives in Windows communities helps explain why users are turning to self-hosted options like Vikunja; community posts repeatedly weigh cost vs. convenience as the primary adoption factor.
Source: MakeUseOf
Vikunja is the open-source Todoist alternative that doesn’t charge you a monthly fee