Kaneo vs PLANKA
The PLANKA alternative with SSO included
PLANKA 2.2 moved SSO into its paid Pro tier, and self-hosters who signed in with OIDC woke up to deactivated accounts. Kaneo is MIT-licensed, self-hostable, and ships SSO to everyone at no cost.
Why teams choose Kaneo
SSO is not a premium feature
Connect Google, GitHub, Discord, or any OIDC provider on the free, self-hosted build. We think authentication is part of running software safely, not an upsell, and we don't plan to move it.
Genuinely MIT
Kaneo is MIT end to end, with no Pro-only files carved out of the repository. You can fork it, run it, and change it without checking which licence a given file falls under.
Your data stays portable
Every project exports to JSON from the UI, and the whole API is public and documented. Getting out of Kaneo is as easy as getting in, which is rather the point.
PLANKA has no export feature, so we wrote an importer that reads your boards straight from its API and recreates them in Kaneo: lists, cards, labels, assignees, checklists, and comments. Start with a dry run, which writes nothing. Read the migration guide.
When PLANKA is the better choice
PLANKA is a good piece of software with a real team behind it, and paid tiers are a legitimate way to fund open-source work. If you're happy on the Community edition with password logins, or SSO is worth the Pro licence to you, there's no reason to move. Kaneo is for teams that need SSO and don't want it behind a paywall.