Self-Hosting Vikunja vs. Vikunja Cloud: What's the Difference?

The core difference is who runs the server. Self-hosting means you install Vikunja on your own infrastructure and control the data directly; Vikunja Cloud is a managed instance where updates, backups, and maintenance are handled for you. Both give you the same task management features — lists, Kanban, Gantt, and table views — and both support sharing projects, assigning tasks, and collaborating with a team. Choose self-hosting if you want full control and are willing to operate a server; choose Cloud if you want the software without the server work.

Self-Hosting Vikunja

Vikunja is open-source under the AGPLv3, and the self-hosted version is free. You run it on your own infrastructure, so your tasks and projects stay on hardware you control, and you can read every line of the code.

What you get:

• Full control over data, server, and configuration
• The same four task views (List, Kanban, Gantt, Table) and team collaboration features
• No dependency on a third-party host for availability

What you take on:

• Installing and maintaining the server yourself
• Handling updates and backups on your own schedule
• Being responsible for uptime and security of the instance

How to install: Vikunja supports Docker, native binaries for your platform, and an install wizard for guided setup. The general flow is: choose an installation method, run the installer or container against your server, complete the wizard, then create your first project and invite collaborators. Verify success by logging in and confirming that a test task appears in each view you plan to use.

Common sticking points: server and database configuration during setup, keeping the instance updated, and arranging backups — none of which the hosted option asks you to manage.

Vikunja Cloud

Vikunja Cloud is the paid hosted option. It gives you a fully managed instance with automatic updates, backups, and zero maintenance, and it's described as the easiest way to get started. It also directly supports continued development of the project.

What you get:

• A running instance without provisioning or administering a server
• Automatic updates and backups
• The same task management and collaboration features as the self-hosted version

What you give up: direct control of the underlying infrastructure and the ability to inspect and modify the deployment yourself.

Pricing details are published on the Vikunja pricing page; check there for current plans rather than assuming a cost structure.

Side-by-Side Comparison

Which Should You Choose?

• Choose self-hosting if data ownership and code transparency are priorities, you already have server capacity, and you're comfortable with installation, updates, and backups.
• Choose Vikunja Cloud if you want the features without operational work, or if you don't have a server and don't want to deal with one.
• Either way, migration is not a lock-in problem: Vikunja has built-in import support for Todoist, Trello, Microsoft To-Do, and other platforms, so you can move existing tasks in minutes.

A practical middle path: start on Cloud to evaluate whether the views and collaboration fit your workflow, then move to a self-hosted instance later if control becomes the priority. The feature set is the same, so the decision rests on how much server responsibility you want to carry.