How to Self-Host code-server to Run VS Code in the Browser Behind a Reverse Proxy
code-server runs a VS Code-compatible editor on a Linux machine and displays it in a web browser. To make it available at…
If you want to replace Todoist with task software you control, choose based on how you manage tasks. Vikunja runs on a server you manage and organizes tasks into shareable projects. Super Productivity is a personal planner that stores data locally and helps you schedule work and track time.
For a conventional Todoist-style task service, Vikunja is the closer match: it supports project sharing and documents a Todoist migration route. Super Productivity fits better when you want an offline-capable personal planner with timers and focus tools. Here, “self-hosted” means you run software on a server you manage; it does not mean the two products use the same kind of server or sync.
Vikunja organizes work into projects and tasks. It includes reminders, recurring tasks, labels, saved filters, and subtasks. Users can view work as lists, Kanban boards, Gantt charts, or tables. Its project-sharing features let users share projects and assign tasks to other users or teams. Users can also create share links. Todoist-style quick-add shortcuts let users enter tasks in a familiar way.
Super Productivity helps one person plan and complete work. It combines tasks and projects with time tracking, timeboxing, focus sessions, work logs, and summaries. Timeboxing means setting aside a specific block of time for a task. It connects to tools such as GitHub, GitLab, Jira, and Gitea, and to calendars. Its product overview describes local data storage by default, offline use, and optional sync.
| Need | Better fit | Why |
|---|---|---|
| Replace Todoist with a server-based task manager | Vikunja | Projects, reminders, task views, sharing, and a documented Todoist migration |
| Share task projects with other people | Vikunja | Project sharing and task assignment are documented features |
| Plan personal work and track time spent | Super Productivity | Timers, timeboxing, focus sessions, and work summaries are central features |
| Work offline without first running a server | Super Productivity | The app stores data locally by default |
| Keep one person’s data in sync across devices | Super Productivity | It offers optional sync methods, including a separate sync server |
A feature checklist alone does not show how each product supports your work. Vikunja’s views and task controls support a shared project workspace. Super Productivity’s timers and work logs help one person plan and review how they spend the day.
Vikunja runs as a web service on a server. Its installation documentation covers options such as Docker and Linux packages, and lists MySQL, MariaDB, PostgreSQL, and SQLite as database choices. The server hosts the task workspace, so the person operating Vikunja needs to maintain the service and its data.
Super Productivity works locally without a server. A user who wants device sync can choose among several methods, including WebDAV, Dropbox, or SuperSync. WebDAV is a standard for accessing files over the web. SuperSync is a separate server component that syncs Super Productivity data between clients; it does not provide the same shared task workspace as Vikunja.
The SuperSync deployment documentation labels the component beta. Its tested setup uses Docker Compose, PostgreSQL, and Caddy. That setup calls for an AMD64 Linux host, a public domain, reachable ports 80 and 443, and an SMTP account. Those requirements apply to that documented SuperSync deployment, not to using Super Productivity locally.
The two products require different work to run. A Vikunja operator runs and maintains a task server. A Super Productivity user can avoid server administration, but anyone who wants self-hosted sync across devices must deploy SuperSync separately and meet its documented requirements.
Vikunja documents an OAuth-based Todoist migration. OAuth is a sign-in and authorization method that lets one service access data from another with the user’s permission. The setup requires configuring a Todoist app and Vikunja’s migration settings. Vikunja’s guides give different requirements for reaching the instance: one says it must be publicly accessible, while another says access through a browser may be enough. Check the instructions for the version and configuration you plan to use before exposing the service.
The official Super Productivity materials reviewed do not confirm a native Todoist importer. That does not establish that importing Todoist data is impossible; it means you should verify a suitable migration route before moving your task history.
Calendar connections also deserve a trial with the clients you intend to use. Vikunja supports CalDAV, a protocol for exchanging calendar and task data, but its CalDAV documentation describes the integration as early alpha and notes bugs and client compatibility issues. It also lists task fields that CalDAV does not support or supports in only one direction. Super Productivity’s calendar integrations connect calendars for planning; calendar access does not itself sync the task data between devices.
Choose Vikunja if you want a central task workspace, need to share projects, or value a documented Todoist migration path. Before switching, test the migration with your Vikunja configuration and confirm that the task views and calendar clients you rely on behave as expected.
Choose Super Productivity if you mainly manage your own work and want task planning tied to timers, focus sessions, and time reports. You can start locally without operating a server. If self-hosted sync is a requirement, evaluate SuperSync separately and account for its beta status and deployment requirements.
Licensing also differs. Vikunja’s core self-hosted version uses AGPLv3, while some features, including time tracking, are listed under Pro; its Pro documentation explains how those features are licensed. Super Productivity’s repository identifies the project as MIT-licensed. Infrastructure costs remain regardless of the software license. Server hosting and backups take time or money, as do updates and administration.
Give Vroni a GitHub issue, bug report, spec, or rough idea. It reads the repo, plans the change, writes code, runs checks, and works toward a review-ready pull request.
Take a look at vroni.com