What Planka 2.2.0 changes — the facts
On August 9, 2026, the Planka team published version 2.2.0. Issue #1754 and the official release notes confirm that OIDC SSO moves from Community Edition to a paid feature in Planka Pro.
The change is immediate on update: no grace period is mentioned in the changelog. More critically, all accounts that authenticated exclusively via SSO are deactivated after the version upgrade — they have no local password. The administrator must manually reset each affected account before restarting the service. If the sole administrator of the instance has no local account, the instance becomes inaccessible.
The self-hosting community flagged this signal quickly: the selfh.st weekly newsletter of August 14, 2026 cites this removal among the week's notable events for OIDC administrators.
Why this removal creates a concrete problem
- Production immediately impacted — an instance coupled to an OIDC IdP can no longer authenticate after the update; SSO accounts are deactivated with no automatic fallback mechanism.
- No migration path announced — the release notes offer no transition path to an alternative login method for existing users.
- Risk of administrator lockout — if the sole admin uses SSO, the instance becomes inaccessible after the update without prior creation of a local account.
- Potential security gap — without SSO, some teams revert to local passwords that bypass centralised rotation and MFA policies.
- Unpredictable licence cost — Planka Pro does not publish public pricing; teams must request a quote with no visibility on future price changes.
Migrating Planka data: what is exportable, what is not
This is the legitimate objection before any migration: losing task history or GitHub integrations is unacceptable. Here is what Planka actually allows you to export — and what it does not.
What does not exist natively. Planka does not offer JSON or CSV export of your boards. Feature requests have been open for years (issues #22 and #670) without resolution.
What is possible. Planka supports importing Trello boards in JSON format — input only, not output. The only reliable extraction of your data is a direct PostgreSQL database dump (pg_dump).
How to limit migration risk.
1. Temporary double-run — run the new instance (Kaneo or Vikunja) in parallel with Planka for one to two weeks.
2. Database snapshot before cutover — take a full pg_dump of the Planka database the day before cutover.
3. Freeze new tasks during migration — communicate a freeze window (a few hours) during which no cards are created or moved.
GitHub integrations (commit links, webhooks) are configured at your Git provider level, not stored in Planka: they reconfigure in minutes in Kaneo or Vikunja after migration.
Kaneo and Vikunja: OIDC SSO status in the free edition
Kaneo v2.16.2 (MIT licence) — released August 10, 2026 on GitHub, this version maintains OAuth 2.0 and OIDC support in the free edition. Configuration is documented at kaneo.app/docs. The MIT licence permits commercial use and modification without conditions.
Vikunja v2.4.0 (AGPL-3.0 licence) — this version maintains OIDC SSO in the free edition. The Vikunja 2.4.0 release notes confirm explicitly: *"the things people often assume are enterprise upsells, SSO and LDAP, are still free and always have been."* OIDC configuration is documented at vikunja.io/docs/openid.
Both projects maintain their OIDC SSO in the free edition with no announced change of plan.
Comparison: Kaneo vs Vikunja to replace Planka
Both tools are open source task managers with free OIDC SSO, but their positioning differs. Choose Kaneo if your team is attached to Planka's clean Kanban interface and wants a like-for-like replacement (512 MB RAM, MIT licence). Choose Vikunja if your teams need multiple views (Gantt, calendar, list) or manage complex projects with task dependencies.
Three-step migration plan
Step 1 — Snapshot and double-run (D-7 to D-1). Take a full pg_dump of your Planka PostgreSQL database. Install the new instance on a temporary subdomain and configure OIDC SSO.
Step 2 — Manual data transfer (D). Planka has no JSON or CSV export. Identify the 2–5 most-used boards and plan a transfer session.
Step 3 — Cutover and DNS removal (D+7). Once teams are autonomous on the new instance, redirect the Planka subdomain DNS and schedule container shutdown at D+30. Keep the PostgreSQL snapshot for at least 90 days.
Activate this solution
Kaneo is the natural successor to Planka — same minimalist Kanban philosophy, MIT licence, free OIDC SSO. Deploy from the ServOrbit marketplace at marketplace/collaboration/kaneo.
Activate this solution
Kaneo is the natural successor to Planka — same minimalist Kanban philosophy, MIT licence, free OIDC SSO. Deploy from the ServOrbit marketplace at marketplace/collaboration/kaneo.
Activate this solution
Kaneo is the natural successor to Planka — same minimalist Kanban philosophy, MIT licence, free OIDC SSO. Deploy from the ServOrbit marketplace at marketplace/collaboration/kaneo.
