[{"data":1,"prerenderedAt":222},["ShallowReactive",2],{"seo-verification":3,"blog-vikunja-vs-plane-which-self-hosted-tool-replaces-jira-in-2026-en":6},{"google":4,"bing":5},"EycwPY2XMyTkVzas3n1ygeNJFGAH513qrMjfDljzsMQ","",{"id":7,"slug":8,"slugs":9,"title":13,"excerpt":14,"readTime":15,"views":16,"isPinned":17,"publishedAt":18,"category":19,"categories":24,"featuredImage":26,"bgImage":27,"posterImage":28,"relatedSolution":26,"intro":29,"sections":30,"ctaTitle":159,"ctaBody":160,"ctaButton":161,"ctaUrl":162,"relatedPosts":163},325,"vikunja-vs-plane-which-self-hosted-tool-replaces-jira-in-2026",{"fr":10,"en":8,"ar":11,"es":12},"vikunja-vs-plane-gestion-projet-vps","vikunja-مقابل-plane-أي-أداة-تحل-محل-jira-عام-2026","vikunja-vs-plane-que-herramienta-open-source-reemplaza-jira","Vikunja vs Plane: which self-hosted tool replaces Jira in 2026","Jira Data Center no longer accepts new subscriptions: compare Vikunja and Plane CE to choose your self-hosted alternative on a VPS.",12,0,false,"2026-09-03T00:00:00+00:00",{"id":20,"name":21,"slug":22,"color":23,"icon":22},5,"Comparison","comparatif","bg-info\u002F10 text-info",[25],{"id":20,"name":21,"slug":22,"color":23,"icon":22},null,"\u002Fblog\u002Fcovers\u002Fbg.svg","\u002Fblog\u002Fcovers\u002Fvikunja-vs-plane-gestion-projet-vps-poster.svg","Atlassian has recently closed new subscriptions to Jira Software Data Center. Linear Enterprise has seen significant price increases this year. For agencies and technical teams looking to regain control of their project management tooling, Vikunja and Plane CE are two mature open-source alternatives you can host on your own VPS. This guide compares the two tools across nine criteria and provides precise installation steps to help you choose with confidence.",[31,35,77,79,89,111,113,124,147,150,153,156],{"type":32,"title":33,"body":34},"h2","Why replace Jira in 2026","Atlassian has recently closed new subscriptions to Jira Software Data Center. Teams already under licence can renew, but any organisation without an existing contract must now use Jira Cloud — a SaaS model with per-seat billing that removes your infrastructure control. Linear Enterprise, another benchmark for tech teams, raised its prices earlier this year, affecting mid-sized teams using it for sprints and GitHub integration.\n\nThis context is pushing a growing number of agencies to evaluate self-hosted open-source alternatives. Two projects stand out: Vikunja, a lightweight Go single-binary task manager under the AGPL-3.0 licence, and Plane CE (Community Edition), a more fully-featured project management platform built around five Docker services, also under AGPL-3.0. The two have very different profiles: understanding their VPS requirements and functional limits is the first decision to make before migrating.",{"type":36,"title":37,"headers":38,"rows":42},"comparison","Vikunja vs Plane CE — comparison table",[39,40,41],"Criterion","Vikunja","Plane CE",[43,47,50,54,58,62,65,69,73],[44,45,46],"RAM required","512 MB (light production)","≥ 4 GB (8 GB recommended)",[48,49,49],"Licence","AGPL-3.0",[51,52,53],"Kanban","Native (Kanban, list, Gantt views)","Native (Board view, customisable states)",[55,56,57],"Gantt","Native","Via modules and due dates",[59,60,61],"Sprints \u002F cycles","Not natively present — simulable with lists","Native cycles (start, end, progress)",[63,64,64],"REST API","Complete, OpenAPI documented",[66,67,68],"Git integrations","Outgoing webhooks, no native GitHub\u002FGitLab integration","Native GitHub and GitLab integration in settings",[70,71,72],"Multi-tenant \u002F workspaces","Yes — projects and teams separated by namespace","Yes — distinct workspaces, members and roles per workspace",[74,75,76],"Mobile application","Official native iOS and Android apps","PWA only (no published native app)",{"type":32,"title":78},"Vikunja — lightweight and versatile",{"type":80,"title":81,"items":82},"ul","Vikunja strengths",[83,84,85,86,87,88],"**Minimal memory footprint** — 512 MB of RAM is sufficient for production; an entry-level VPS can run Vikunja without resizing.","**Go single binary** — one binary bundles the API server and background task service; the Docker deployment reduces to a single application service and a database.","**Multiple native views** — Kanban, list, Gantt and summary table are available with no additional extension or plugin.","**Complete REST API** — every entity (task, list, project, user, label) is exposed via an OpenAPI-documented API, making agency workflow automation straightforward.","**Native mobile applications** — official iOS and Android apps are published in the stores, which is rare among open-source task management tools.","**AGPL-3.0 licence** — the source code is public, and community contributions are fast, particularly on security patches.",{"type":90,"title":91,"steps":92},"steps","Install Vikunja on a VPS with Docker Compose",[93,96,99,102,105,108],{"title":94,"body":95},"Create the working directory","Connect to your VPS and create a dedicated directory: `mkdir -p \u002Fopt\u002Fvikunja && cd \u002Fopt\u002Fvikunja`. This directory will hold the `docker-compose.yml` file, the `config.yml` configuration file, and persistent data.",{"title":97,"body":98},"Write the docker-compose.yml file","Create a `docker-compose.yml` file with two services: the database and Vikunja itself. Minimal example with PostgreSQL:\n```yaml\nservices:\n  db:\n    image: postgres:16\n    restart: unless-stopped\n    environment:\n      POSTGRES_USER: vikunja\n      POSTGRES_PASSWORD: changeme\n      POSTGRES_DB: vikunja\n    volumes:\n      - vikunja-db:\u002Fvar\u002Flib\u002Fpostgresql\u002Fdata\n  vikunja:\n    image: vikunja\u002Fvikunja:latest\n    restart: unless-stopped\n    ports:\n      - \"127.0.0.1:3456:3456\"\n    environment:\n      VIKUNJA_DATABASE_TYPE: postgres\n      VIKUNJA_DATABASE_HOST: db\n      VIKUNJA_DATABASE_USER: vikunja\n      VIKUNJA_DATABASE_PASSWORD: changeme\n      VIKUNJA_DATABASE_DATABASE: vikunja\n      VIKUNJA_SERVICE_PUBLICURL: https:\u002F\u002Fvikunja.your-domain.com\n    volumes:\n      - vikunja-files:\u002Fapp\u002Fvikunja\u002Ffiles\n    depends_on:\n      - db\nvolumes:\n  vikunja-db:\n  vikunja-files:\n```",{"title":100,"body":101},"Start the services","Start the stack with `docker compose up -d`. On first start, Vikunja applies database migrations automatically. The interface is available on port 3456 within seconds — Vikunja starts very quickly thanks to its Go binary.",{"title":103,"body":104},"Configure the HTTPS reverse proxy","Point Nginx or Caddy to `127.0.0.1:3456`. With Caddy, the configuration is:\n```\nvikunja.your-domain.com {\n    reverse_proxy 127.0.0.1:3456\n}\n```\nCaddy manages the Let's Encrypt certificate automatically. With Nginx, add `Upgrade` and `Connection` headers to proxy WebSockets correctly if you use real-time notifications.",{"title":106,"body":107},"Create the first administrator account","Open your subdomain in a browser. Vikunja displays a registration screen: the first account created automatically receives administrator rights. Then enable two-factor authentication (TOTP) from the account settings — essential if the instance is publicly exposed.",{"title":109,"body":110},"Verify backups","Schedule a daily backup of the PostgreSQL volume and the `vikunja-files` volume. A sufficient command: `docker exec vikunja-db-1 pg_dump -U vikunja vikunja | gzip > \u002Fbackup\u002Fvikunja-$(date +%Y%m%d).sql.gz`. Test restoration on a test environment before migrating your production data.",{"type":32,"title":112},"Plane CE — enterprise features in open source",{"type":80,"title":114,"items":115},"Plane CE strengths",[116,117,118,119,120,121,122,123],"**Native cycles (sprints)** — create cycles with start and end dates, track progress by points or issues, and archive completed cycles without losing history.","**Modules and cross-project groupings** — group issues from different projects in a thematic module, useful for agencies managing multiple clients in parallel.","**Native Jira importer** — Plane CE includes a Jira import connector in Settings > Importers, transferring issues, statuses, priorities, comments and members in a few clicks.","**Native GitHub and GitLab integrations** — link your repositories directly from workspace settings; commits and pull requests appear in the related issues.","**Clear Docker architecture** — five documented services (web, API, worker, PostgreSQL, Redis) and optional MinIO for file storage; each service scales independently.","**Integrated wiki pages** — each project has a structured documentation space, available without an external module.","**Complete REST API** — all Plane entities are accessible via a versioned API; Python and JavaScript SDKs are maintained by the community.","**AGPL-3.0 licence** — the source code is auditable, and the GitHub community counts several thousand active contributors.",{"type":90,"title":125,"steps":126},"Install Plane CE on a VPS",[127,130,133,136,139,141,144],{"title":128,"body":129},"Check system requirements","Plane CE requires at least 4 vCPU and 8 GB of RAM for a comfortable production deployment. Below this threshold, Celery workers compete for memory with PostgreSQL and Redis, causing unexpected restarts. Verify that Docker Engine ≥ 24 and Docker Compose ≥ 2.20 are installed: `docker --version && docker compose version`.",{"title":131,"body":132},"Download the official deployment script","Plane CE provides an installation script that generates the `docker-compose.yml` and `.env` files with random secrets:\n```bash\ncurl -fsSL https:\u002F\u002Fraw.githubusercontent.com\u002Fmakeplane\u002Fplane\u002Fmaster\u002Fdeploy\u002Fselfhost\u002Finstall.sh | bash\n```\nThe script creates an `\u002Fopt\u002Fplane` directory and places all required files there. Review the generated `.env` before continuing: `SECRET_KEY`, `DATABASE_URL` and `REDIS_URL` variables are pre-filled with secure random values.",{"title":134,"body":135},"Configure the domain in the .env file","Open `\u002Fopt\u002Fplane\u002F.env` and set `WEB_URL=https:\u002F\u002Fplane.your-domain.com`. If you use MinIO for file storage, also set `AWS_S3_ENDPOINT_URL`, `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`. Disable MinIO storage if you prefer to store files on the local volume — set `USE_MINIO=0`.",{"title":137,"body":138},"Start the five Docker services","From `\u002Fopt\u002Fplane`, run `docker compose up -d`. The five main services start: `web` (React interface), `api` (Django REST), `worker` (Celery), `beat` (Celery periodic tasks), and `db` (PostgreSQL). Redis is included as a sixth service for caching and message queuing. Wait approximately two to three minutes for Django migrations to complete before opening the interface.",{"title":103,"body":140},"Plane exposes the `web` service on port 3000 and the API on port 8000 internally. Your reverse proxy must route both: the React interface on `\u002F` and API requests on `\u002Fapi\u002F` and `\u002Fauth\u002F`. With Nginx, use two `location` blocks in the same `server` block pointing to `127.0.0.1:3000` and `127.0.0.1:8000` respectively. WebSockets are used for real-time updates — forward the `Upgrade` and `Connection` headers.",{"title":142,"body":143},"Create the first workspace","Open your domain in a browser. Plane displays a registration screen: create an administrator account, then follow the workspace creation wizard. Import your first project from Jira or create a blank project to validate the installation. Invite members from Settings > Members > Invite Members — each member receives an email invitation link.",{"title":145,"body":146},"Plan backups for the five stateful services","Plane has five stateful services to back up: PostgreSQL (volume `pgdata`), Redis (volume `redisdata`), and MinIO if enabled (volume `uploads`). Schedule daily PostgreSQL dumps (`pg_dump` from the `db` container), and archive Docker volumes with your preferred backup tool. Systematically test restoration on a test VPS before putting the main instance into production.",{"type":32,"title":148,"body":149},"Security — how quickly both projects respond","The question of security maturity in open-source tools is legitimate, and both projects offer concrete answers. Both projects have shown a quick patch turnaround, with fixes published within days of disclosure. A fix was integrated in Vikunja within ten days of public disclosure, demonstrating the fast-response capability of a well-organised open-source community. The practical lesson: keep Vikunja up to date via `docker compose pull && docker compose up -d` on a weekly cycle, and enable security notifications on the GitHub repository (Watch > Security alerts).\n\nPlane CE follows a monthly release cycle with a detailed public changelog. Security issues are handled in a private channel before publication, following a documented responsible disclosure process in the repository. For both tools, the audit trail of user actions (who changed what, when) is available in application logs — exportable to meet internal compliance requirements.",{"type":151,"body":152},"tip","To import from Jira into Plane CE: back up your Plane database before starting (`docker exec plane-db-1 pg_dump -U plane plane > backup-before-import.sql`). Then, in Plane, go to Settings > Importers > Jira. The importer asks for your Jira URL, a Jira Personal Access Token, and the project name to import. Issues, statuses, priorities, comments and members are transferred in a single operation. Also back up your database after the import and verify the total number of imported issues before revoking Jira access.",{"type":32,"title":154,"body":155},"Decision guide — when to choose each tool","**Choose Vikunja if** your team manages primarily tasks and lists without a formalised sprint process, if your VPS is limited to 1 or 2 GB of RAM, if you need native mobile applications for teams on the move, or if you prefer a simple architecture to maintain (a single binary, a single database). Vikunja is also an excellent choice if you host multiple client projects on the same instance thanks to its namespace system.\n\n**Choose Plane CE if** your team is coming from Jira and wants to find familiar concepts — cycles (sprints), customisable states, and a native Jira importer. Plane CE is better suited to agencies managing cross-functional workflows (multi-project modules), needing GitHub or GitLab integration directly in issues, or wanting a tool whose interface will be immediately recognisable to developers used to Linear or Jira. The 4 to 8 GB RAM requirement is the main constraint: verify your VPS before choosing.\n\n**In all cases**, start with a pilot project on a separate instance before migrating production. The effort of migrating a project management tool is rarely neutral for a team — planning two weeks of cohabitation between the old and new tool allows validation of status mapping, workflow habits and CI integrations without blocking deliveries.",{"type":32,"title":157,"body":158},"ServOrbit agency resources","ServOrbit offers Linux VPS with full root access, sized from 1 vCPU \u002F 1 GB RAM (sufficient for Vikunja) to 8 vCPU \u002F 32 GB RAM (comfortable for Plane CE with several dozen users). All VPS come with a Docker-ready image, secure SSH access, and high-bandwidth connectivity on internal traffic. For agencies managing multiple clients, our VPS offers include the ability to provision isolated instances per client from a centralised console.\n\nTo go further with your migration from Atlassian or Linear tools, consult our related guides: migrating from Jira to OpenProject or Plane, the context of Jira Data Center's closure and its implications for existing teams, and our full comparison of self-hosted project management tools including Huly.","Host Vikunja or Plane CE on a ServOrbit VPS","Our VPS are sized to accommodate both tools: from 512 MB for Vikunja to 8 GB for Plane CE. Root access, Docker image included, generous bandwidth. Your project management data stays in your infrastructure, with no member limits and no seat fees.","Discover ServOrbit agency offers","\u002Fsolutions\u002Fagences",[164,183,204],{"id":165,"slug":166,"slugs":167,"title":171,"excerpt":172,"readTime":173,"views":174,"isPinned":17,"publishedAt":175,"category":176,"categories":177,"featuredImage":26,"bgImage":27,"posterImage":179,"relatedSolution":180},310,"jira-data-center-closed-switch-to-plane-self-hosted",{"fr":168,"en":166,"ar":169,"es":170},"atlassian-eol-jira-plane-self-hosted-2026","إغلاق-jira-data-center-plane-بديلا-مستضافا-ذاتيا","jira-data-center-cerrado-migrar-a-plane-self-hosted","Jira Data Center closed: switch to Plane self-hosted","Atlassian closed Jira Data Center to new subscribers (March 2026) and raised renewals by 15%. Plane AGPL-3.0 covers the essentials with no per-seat subscription.",8,1,"2026-08-28T00:00:00+00:00",{"id":20,"name":21,"slug":22,"color":23,"icon":22},[178],{"id":20,"name":21,"slug":22,"color":23,"icon":22},"\u002Fblog\u002Fcovers\u002Fatlassian-eol-jira-plane-self-hosted-2026-poster.svg",{"categorySlug":181,"appSlug":182},"development","plane",{"id":184,"slug":185,"slugs":186,"title":190,"excerpt":191,"readTime":192,"views":174,"isPinned":17,"publishedAt":193,"category":194,"categories":199,"featuredImage":26,"bgImage":27,"posterImage":201,"relatedSolution":202},270,"migrating-from-jira-data-center-to-openproject-or-plane-on-vps",{"fr":187,"en":185,"ar":188,"es":189},"migrer-jira-openproject-plane-vps-2026","هجرة-jira-data-center-إلى-openproject-أو-plane-على-vps","migrar-de-jira-a-openproject-o-plane-en-vps","Migrating from Jira Data Center to OpenProject or Plane on VPS","Jira Data Center stopped selling new licenses in March 2026 and goes read-only on March 28, 2029. Migrate to OpenProject or Plane on your VPS in a single working day.",13,"2026-08-16T00:00:00+00:00",{"id":195,"name":196,"slug":197,"color":198,"icon":197},3,"Deployment","deploiement","bg-success\u002F10 text-success",[200],{"id":195,"name":196,"slug":197,"color":198,"icon":197},"\u002Fblog\u002Fcovers\u002Fmigrer-jira-openproject-plane-vps-2026-poster.svg",{"categorySlug":203,"appSlug":182},"collaboration-productivity",{"id":205,"slug":206,"slugs":207,"title":211,"excerpt":212,"readTime":195,"views":174,"isPinned":17,"publishedAt":213,"category":214,"categories":219,"featuredImage":26,"bgImage":27,"posterImage":221,"relatedSolution":26},221,"huly-replace-linear-notion-and-slack-on-your-vps",{"fr":208,"en":206,"ar":209,"es":210},"huly-gestion-projet-self-hosted-vps","huly-استبدل-linear-وnotion-وslack-على-خادمك-الافتراضي","huly-gestion-proyectos-self-hosted-vps","Huly: replace Linear, Notion and Slack on your VPS","Deploy Huly on your VPS to centralise issues, docs and chat in one open-source tool — no per-seat subscription required.","2026-08-04T00:00:00+00:00",{"id":215,"name":216,"slug":217,"color":218,"icon":217},2,"Automation","automatisation","bg-brand-action\u002F10 text-brand-action",[220],{"id":215,"name":216,"slug":217,"color":218,"icon":217},"\u002Fblog\u002Fcovers\u002Fhuly-gestion-projet-self-hosted-vps-poster.svg",1788446469864]