How to Install or Get Started with Vikunja

You can get started with Vikunja in one of three ways: self-host it with Docker, install it from native binaries for your platform, or sign up for Vikunja Cloud if you don't want to manage a server. All three paths lead to the same task manager with list, Kanban, Gantt, and table views. The right choice depends on whether you want full control of the infrastructure or a managed instance with automatic updates and backups.

Choose Your Path First

Vikunja is open source under the AGPLv3 and free to self-host. Vikunja Cloud is the paid hosted option; the site presents it as the easiest way to get started and as a way to directly support continued development. Pricing details are on the pricing page, so check there before committing.

Self-Host with Docker

Docker is the most direct route if you already run containers.

1. Confirm prerequisites. You need a machine you control (local or remote) with Docker installed, plus a way to reach the web interface (a browser on the same machine or network access to the host).
2. Run Vikunja as a container. Use the official Vikunja Docker image and expose its web port to your host. The exact image tag, port mapping, and volume configuration are documented in Vikunja's install docs — follow those rather than guessing, since the container needs persistent storage for its database and files.
3. Complete the install wizard. On first access, Vikunja provides a guided setup. Expect to create the initial admin account and confirm general configuration. The wizard is the intended path for a first run, so use it instead of configuring by hand.
4. Verify. Log in, create a test project, and add a task. Switch between list and Kanban views to confirm the app is fully working, not just serving a page.
5. Then plan persistence. Decide where your data lives and how you'll back it up before you put real tasks in.

Common sticking points: the container starting but the web UI being unreachable (usually a port or network issue), and data disappearing after a restart (usually a missing persistent volume). Both are configuration problems, not Vikunja bugs.

Install from Native Binaries

If Docker isn't an option, Vikunja publishes native binaries for supported platforms.

1. Download the binary for your platform from the official release source.
2. Place it somewhere stable and make it executable where your OS requires it.
3. Run it and open the web interface, then complete the same install wizard described above.
4. Verify with a test project and a view switch, as with Docker.

The trade-off versus Docker is that you manage the runtime environment yourself — dependencies, service supervision, and upgrades are your responsibility. If you're unsure, Docker is the safer default.

Use Vikunja Cloud Instead

If you don't have a server or don't want to deal with one, Vikunja Cloud gives you a fully managed instance with automatic updates and backups and zero maintenance. Sign up, and you land in the same application — no install wizard, no infrastructure. This is the option to pick when your priority is getting organized today rather than running software.

After You're In: Importing and Scaling Up

Whichever path you chose, the first useful step is often bringing existing tasks over. Vikunja has built-in migration support for Todoist, Trello, Microsoft To-Do, and other platforms, so you can import in minutes rather than rebuilding by hand.

Vikunja is also designed to grow from a personal to-do list into shared work: when your team needs it, you share projects, assign tasks, and collaborate without switching tools. Start with a single list, then add Kanban or Gantt views as your planning needs become clearer.

Quick Decision Guide

• You have a server and want ownership and code transparency → self-host with Docker.
• You have a server but can't or won't use Docker → native binaries.
• You don't have a server, or don't want the maintenance → Vikunja Cloud.
• You're migrating from another tool → any path works; use the built-in importers right after setup.