Self-hosters are arguing about Infisical this weekend, and the whole dispute fits in one commit diff. The verified fact: commit e4880e71ed, titled "feat: custom roles as enterprise-only feature," added a license check to the Infisical secrets manager that blocks creating or updating custom roles on installations without an Enterprise plan.
Key facts
- The commit adds a plan check to role creation and update: without an Enterprise plan, the server returns "Failed to create custom role due to plan RBAC restriction."
- The frontend change adds an upgrade modal reading "Your current plan does not include custom roles."
- The change shipped in patch release v0.159.6, where users do not expect feature-level behavior changes.
- The r/selfhosted thread that surfaced it described operators caught after Renovate auto-upgraded their installs.
What's driving the conversation
The thread on r/selfhosted framed the change as a paywall sneaked into a patch. Infisical has not published a public response in that thread so far, so its side of the story is absent, and we present the finding as the code shows it rather than adopting either framing.
The substance
Walking the commit settles what actually changed. The backend adds a licenseService.getPlan check before role create and role update, returning a BadRequestError naming the Enterprise plan when the plan lacks the RBAC flag. The frontend swaps the plain role form for one gated behind an UpgradePlanModal. The practical consequence for free self-hosters: roles that already exist keep working, but the moment you need to edit one, you hit the gate.
Two facts sit behind the reaction. First, the commit itself is dated April; it reached most self-hosters through the v0.159.6 patch release, months later, and patch releases are where nobody reads release notes. Second, secrets managers are exactly the layer where access-control behavior matters most: an RBAC restriction that changes under an automated upgrade touches who can read production credentials.
Feature gating inside an open-core codebase is normal commercial practice, and nothing in the commit suggests a license violation. The legitimate complaint is narrower: the feature moved behind a paywall in a patch release, without a changelog line loud enough for the operators it affected.
Why builders are watching
This is the self-hosted trust thread again, from a different angle than the LiteLLM supply-chain compromise or the exposed AI endpoints sweep. Teams pinning secrets managers for AI infrastructure should read the actual diff, not the announcement, before letting Renovate merge the next bump, and check what else in their stack sits on the same open-core boundary.
Questions
- What changed in Infisical v0.159.6?
- Commit e4880e71ed, titled 'feat: custom roles as enterprise-only feature', added a license check that blocks creating or updating custom roles on installations without an Enterprise plan. Existing custom roles continue to function but can no longer be edited on free self-hosted installs.
- Is gating features in a patch release legal for open-source projects?
- It depends on the license. Most open-source licenses govern the code, not the feature-gating inside it, so vendors can generally restrict paid features. The dispute here is about disclosure and timing, not license compliance.
Sources
About DeAI
DeAI is an independent publication covering open-weight AI models, private inference, and decentralized infrastructure — the tools for running AI you actually control. We test providers on price, privacy, and refusal behavior and publish the numbers, not the vibes. DeAI is powered by Morpheus (mor.org), a decentralized inference marketplace, and covers it on the same terms as every other provider.
Powered by Morpheus and StrandCMS
Morpheus is a decentralized inference marketplace, covered on the same terms as every other provider — we rank it wherever the data lands. StrandCMS is the open-source, agent-first framework this site is built on.
