[feature]: Move OIDC back to self-hosted OSS(Plane Free)

### Is there an existing issue for this? - [x] I have searched the existing issues ### Summary In version 1, OIDC support was included for self-hosted deployments under the Tier 1 (Plane Free) plan. However, in version 2, it appears this functionality has been moved behind a paywall. This change significantly restricts adoption, as organizations now face a steep $8.00 per seat subscription just to implement a core authentication feature in what was previously open source software. ### Why should this be worked on? As members of the open source community, we believe restoring OIDC access would empower more companies to adopt and contribute to your platform—just as they did with version 1. Unfortunately, the shift in version 2 sends a discouraging signal: features that were once freely available are now gated, making the project feel less open and more commercialized.

Posted by scoobs-mystery-bytes on Oct 31, 2025, 5:13 AM

Tags

• support (SaaS)

Related issues

• As I replied in another comment[1], it's their software, their choice.
• [Feature] Support external model integration via personal API keys and local LLMs (BYOK)
• > So when head of companies don’t care about quality, they’ll push hard no matter what to have speed.
• Feature request: support multiple named accounts per app/connector
• Support standalone Windows installer (`codex-setup.exe`)
• I was running about 1000 machines on VMware in my previous career.