Why Self-Hosted Apps Dey Charge SSO Tax
Some open source apps lock OIDC and SAML behind paid plans. See why maintainers do am and the checklist to use before you install anything.
Wetin SSO tax mean
SSO tax for self-hosted software na pattern wey application dey free, but na single sign-on (SSO) be the one feature wey you must pay for. You fit run the whole software for your own VPS without licence key and without seat limit. Then you open authentication page for the documentation and see OpenID Connect (OIDC) or SAML (security assertion markup language) under paid plan.
This matter pass ordinary feature wey dem lock behind payment, because na SSO dey make group of self-hosted services behave like one system. Identity provider (IdP) give each person one account, one password policy, one place to enable multi-factor authentication (MFA), and one place to disable person account. Without am, every app go keep small user database of its own, and you go manage each one by hand.
This pattern don old reach where public scoreboard dey exist. SSO Wall of Shame for sso.tax list vendors wey dey charge big extra money for single sign-on. The list get entries wey reach 2018, and the author set fair standard: "If your SSO support is a 10% price hike, you're not on this list." Most of the software for that list na closed software. Now, open source projects wey you host by yourself don start to use the same pricing logic.
Wetin make maintainers put single sign-on behind paid tier
Reasons dey two, and both honest. SSO dey cost plenty to support, and na one of the few features wey big organisation go pay for.
The support cost real because identity integration never really finish. Every IdP dey format its claims small differently. Group mapping, session lifetime, redirect URLs, and clock skew fit each cause login bugs. Login bug fit lock out every user at once, so those tickets urgent. After that, follow-up requests go come: nested groups, role mapping, automatic provisioning with SCIM (system for cross-domain identity management), and audit logs wey compliance team go read.
The revenue side na arithmetic, no be malice. Company wey no fit connect the app to its own IdP no go deploy am at all, so SSO dey mark clear line between user wey pay and user wey no pay. Open core project need put that line somewhere. SSO fit sit for that line more neatly than almost any other feature, na why plenty projects dey choose am.
Make we correct one common complaint: check the changelog before you assume say dem remove feature, because removal go show for release notes. For most of the projects wey I check for this post, dem build the paid SSO features for paid tier from the beginning. Planka na the exception. Its free Community edition ship with working OIDC until version 2.2.0, wey release on 9 August 2026. The release notes talk say "OIDC/SSO has been removed from PLANKA Community." The feature now dey inside Planka Pro, and the maintainers' own explanation agree with the point: "The fact that it ended up in Community never fit that model." Grafana typical of the others. Its SAML page get one-line note: "Available in Grafana Enterprise and Grafana Cloud", while generic OAuth against your own issuer dey work for the open source build.
SSO tax dey really cost how much
The money na the smaller part. Most paid tiers dey sell per user, so bill dey grow as your team grow, while hosting and upgrades still na your responsibility. n8n na one exception: the pricing page talk say all plans include unlimited users, and e dey charge based on monthly workflow executions instead.
The bigger cost na manual identity work, and e dey show for four places.
- One password store for each app, so one reused password become a hole for every app wey share am.
- Offboarding from memory. You must remember every service wey person ever use, and the one wey you forget na the one wey matter.
- MFA configured app by app, if the app support am at all.
- Shared logins, wey na wetin dey really happen for small teams under this pressure.
This last point deserve one sentence by itself. When team share one administrator account for document manager, audit trail dey record one name for everything, so you no fit know who delete the invoice. Per-user permissions stop to work too, because na only one user dey exist. Na this be the real damage from SSO tax: e push small teams toward one shared account, wey worse pass any of the alternatives.
Checklist wey you suppose run before you adopt anything
Run this before docker compose up, no be after the app don hold 400 documents.
- Open authentication page for the docs and read the tier note for top. Paid features dey carry badge or one-line availability sentence.
- Confirm say the app dey speak OIDC or SAML to your own issuer, instead of one fixed list of public providers.
- Check role and group mapping. To create the user na half the work, and to assign permissions by hand for ten apps na the half wey dey pain.
- Check whether the app dey accept authenticated username for header from trusted proxy, and whether you fit specify which proxy e trust.
- Read licence history for git, and check whether contributors dey sign CLA (contributor licence agreement).
- Check offboarding. Find out wetin happen to API (application programming interface) tokens and live sessions when dem disable the IdP account.
Item 2 na where most disappointment dey happen. A "Sign in with Google" button no be OIDC with your identity provider: na fixed integration with one vendor. Real support go ask you for issuer URL, and discovery go provide everything else. You fit confirm your provider side with one command.
curl -s https://id.example.com/.well-known/openid-configuration \
| jq '.issuer, .authorization_endpoint, .token_endpoint'Three URLs go return from healthy provider. Empty result or 404 normally mean say discovery path wrong, and that path dey provider specific: Keycloak dey publish am under /realms/<realm>/.well-known/openid-configuration. If the app no get field for issuer URL at all, e no fit talk to your IdP, no matter wetin feature list talk.
Item 6 dey catch people weeks after person don leave. Disabling the account for IdP dey stop new logins. E no revoke API token wey the app issue before, because the app dey validate that token by itself and e never ask IdP about am. So offboarding get two steps: disable the account for IdP, then delete the user or its tokens inside each app.
Wetín the tier badges really dey talk
Dem check all these against each project own documentation on 11 October 2026. Make we start with the paid side.
Grafana publish SAML as "Available in Grafana Enterprise and Grafana Cloud", together with team sync and SCIM provisioning. Generic OAuth, GitHub OAuth, LDAP (lightweight directory access protocol) and the auth proxy dey inside the open source build, so small self-hoster still fit log in through their own provider. The paid line start for SAML, no be for single sign-on as a whole. Na this nuance phrase "SSO tax" dey usually flatten.
Metabase talk am more directly. Its documentation say, "SAML authentication is only available on Pro and Enterprise plans (both self-hosted and on Metabase Cloud)." The open source edition still get password login and LDAP.
Passbolt mark its SSO documentation as Pro and Cloud, so community edition no get am. The documented providers include Keycloak and Entra ID.
n8n put everything behind payment. The self-hosted community edition free under a fair-code licence, but the documentation list SAML and LDAP login under the Business and Enterprise plans, while OIDC dey only for Enterprise. So no free single sign-on route dey at all. Na one item for the longer list of wetin the free n8n edition no get.
Now the other side, because this pattern no universal at all.
- GitLab Self-Managed carry "Tier: Free, Premium, Ultimate" for its SAML page, so SAML against your own GitLab cost nothing.
- Paperless-ngx configure OIDC through django-allauth with
PAPERLESS_SOCIALACCOUNT_PROVIDERS, hide the local login form withPAPERLESS_DISABLE_REGULAR_LOGIN, and map claims to groups withPAPERLESS_SOCIAL_ACCOUNT_SYNC_GROUPS. - Planka no longer belong for this side. Its Community edition take
OIDC_ISSUER,OIDC_CLIENT_IDandOIDC_CLIENT_SECRET, set its scopes toopenid profile emailby default, and promote administrators from a role claim withOIDC_ADMIN_ROLES, until version 2.2.0 on 9 August 2026 remove OIDC from Community and move am to Planka Pro. Older Community releases still get am, but the maintainers only support the latest release. - BookStack switch over with
AUTH_METHOD=oidc, then map provider groups to its own roles withOIDC_USER_TO_GROUPS=trueandOIDC_GROUPS_CLAIM. - Vaultwarden ship "support for SSO with OpenID Connect" for 1.35.0 on 27 December 2025, from a pull request by contributor wey don carry the feature for a fork.
- listmonk don get OIDC login together with its user roles since v4.1.0, wey release on 12 November 2024.
Use this information when you dey choose, no be after you don commit. A Planka kanban board and the other self-hosted Trello alternatives no treat identity the same way, and BookStack, Wiki.js and Outline no do so too. Free OIDC na feature wey you fit weigh like storage limits or mobile clients. If you still dey draw up the list, wetin to self-host for 2026 na reasonable starting point, and both the Paperless-ngx document manager and Vaultwarden give you free OIDC today.
Why reverse proxy wey dey in front of app no be single sign-on
The common workaround na forward auth. Your reverse proxy go hold each request, ask authentication service whether this browser don sign in, and na only then e go pass the request go app. authentik dey call this proxy provider, with forward auth mode for one application and another one for whole domain. Authelia and oauth2-proxy dey do the same work.
Caddy site block fit look like this, following authentik own example.
app.example.com {
forward_auth http://authentik-outpost:9000 {
uri /outpost.goauthentik.io/auth/caddy
copy_headers X-Authentik-Username X-Authentik-Email X-Authentik-Groups
trusted_proxies private_ranges
}
reverse_proxy app:8000
}Capitalisation of those header names matter for Caddy, because if the name no match, e go arrive empty. For every request wey e approve, the outpost dey set X-authentik-username, X-authentik-email, X-authentik-groups and some other ones.
This na wetin e give you. Nobody fit reach the app without first passing through your identity provider, so unpatched login form no longer dey exposed to internet, and MFA dey apply to everything behind the proxy at once.
This na wetin e no give you: identity inside the app. The app still get its own accounts and its own idea of who don sign in. If everybody pass the proxy and land for one shared administrator account, you get strong front door but one anonymous session behind am. Audit log still dey show one name. Permissions still no fit differ between people. To call this arrangement SSO na security mistake, because the offboarding story only true halfway: removing the person from your IdP go close the front door, but API token wey dem create inside the app go still work for anybody wey fit reach the app directly.
Header authentication make safe
Some apps dey accept username from proxy. This one fit give you identity for each user without paid SSO. Every project get different name for this setting.
Grafana dey call am auth proxy, and e dey disabled by default. Header name dey default to X-WEBAUTH-USER, but you fit point am to any header wey your proxy dey set.
[auth.proxy]
enabled = true
header_name = X-authentik-username
header_property = username
auto_sign_up = true
whitelist = 10.0.0.5whitelist na the line wey people dey skip. Grafana documentation talk clearly say e dey stop users from spoofing the header. So e suppose contain only the address of your proxy. Gitea get the same feature under different names, and e ship with safer default.
[security]
ENABLE_REVERSE_PROXY_AUTHENTICATION = true
REVERSE_PROXY_AUTHENTICATION_USER = X-WEBAUTH-USER
REVERSE_PROXY_TRUSTED_PROXIES = 10.0.0.5/32
REVERSE_PROXY_LIMIT = 1REVERSE_PROXY_TRUSTED_PROXIES dey default to 127.0.0.0/8,::1/128, while REVERSE_PROXY_LIMIT na the number of proxies wey Gitea go trust for the chain. If you set that limit to zero, e go turn off header handling completely.
Paperless-ngx get PAPERLESS_ENABLE_HTTP_REMOTE_USER together with PAPERLESS_HTTP_REMOTE_USER_HEADER_NAME. The documentation give this warning, and e apply to all these settings:
This go allow authentication just by adding Remote-User: <username> header to request. Use am carefully!
Two rules dey keep header authentication safe, and both concern reachability. First, nobody suppose reach the app except through the proxy. Anybody wey fit open socket to the app fit send that header and become any user. For Docker, ports: ["8000:8000"] dey publish for every interface. So bind am to loopback address with ports: ["127.0.0.1:8000:8000"], or remove the published port and put the proxy for the same Docker network. Second, the proxy must delete any copy of the header wey come from the client. That way, the only value wey the app ever sees na the one your proxy sets after authentication.
Check both ones. Run the first command from machine outside your VPS, and run the second one for the server itself.
curl -si -H "Remote-User: admin" http://203.0.113.10:8000/ | head -n 1
ss -ltnp | grep 8000The curl suppose fail to connect, and ss suppose print 127.0.0.1:8000 instead of 0.0.0.0:8000. Any status line at all, such as HTTP/1.1 302 Found, usually a redirect go login page, means the app dey answer the public internet directly. If header authentication dey enabled, this exposure fit allow anybody sign in as any user by putting the user name inside a header.
When free SSO no dey, make decision instead of complaining
These na four options, arranged for the order wey I go try dem.
- Choose the app wey include OIDC. If two projects dey do the same work and one fit connect to your identity provider for free, that one na real difference for running cost.
- Use forward auth honestly. For admin tool wey get one account and one operator, proxy for front dey enough. Per-user identity inside the app no dey add anything.
- Pay. If the app dey central to your work and per-seat price fit your team size, the money go help maintain the project. The alternative na to pay with your evenings.
- Ask upstream, after you search the issue tracker. Vaultwarden OIDC support come through contributor's fork and long-running pull request. So feature request wey get working implementation behind am fit sometimes enter the free edition.
None of this go work without your own identity provider. Na this one you suppose build first. Run authentik for VPS go give you OIDC and SAML provider, plus the forward auth outpost wey we use above. Comparison of Keycloak, authentik and Zitadel explain the trade-offs if you prefer make you no commit yet.
Licence history, and wetin make e dey for the checklist
The last checklist item na about the future, because today's tier arrangement na only one snapshot. Two well documented cases show how fast things fit change, for both directions. On 10 August 2023 HashiCorp moved future releases of all its products, plus several libraries, from MPL 2.0 (Mozilla Public License) to the Business Source License 1.1, while its APIs, SDKs and almost all other libraries remain under MPL 2.0. Redis move to the SSPL (server side public license) for March 2024, then announce on 1 May 2025 say Redis 8 also dey ship under the AGPLv3 (GNU Affero General Public License).
Read both as evidence about how the process work, not about the reason behind am. The licence wey you read today apply to the version wey you install today, and a project wey hold all its copyright fit change the terms for the next release by itself. Na why the CLA question dey for the checklist, because broad copyright assignment na wetin make unilateral relicence possible.
Check the history of any project by yourself before you build on top of am.
git clone --filter=blob:none https://github.com/paperless-ngx/paperless-ngx.git
cd paperless-ngx
git log --follow --oneline -- LICENSEShort list of commits, mostly from the first import, na good sign. If dem rewrite the licence file several times, you suppose read each commit message before you plan around the current terms.
FAQ
Wetin be the SSO tax?
SSO tax na when dem dey charge extra for single sign-on as premium feature, while the rest of the product dey free or cheap. For self-hosted software, e fit be open source application wey you fit run without licence key, but OIDC or SAML login dey only for paid tier. The name come from SSO Wall of Shame for sso.tax, wey dey track vendors wey dey charge plenty extra for am. For person wey dey self-host, the result be say every app still get im own user database, so na hand you go use create and remove accounts.
Forward auth for reverse proxy na the same thing as SSO?
No. Forward auth dey protect the front door: your proxy go check with identity provider before any request reach the app. The app behind am still dey use im own accounts, so if everybody enter through one shared login, you go get one anonymous session and audit log wey get only one name. E go become real per-user identity only when the app read the username from a header. Grafana's auth proxy, Gitea's reverse proxy authentication, and Paperless-ngx's PAPERLESS_ENABLE_HTTP_REMOTE_USER fit all do this. These settings safe only while clients no fit reach the app except through the proxy, because the header na ordinary string wey any client fit send.
Which self-hosted apps get OIDC for the free edition?
We check am against project documentation on 11 October 2026: Paperless-ngx, BookStack, Gitea, listmonk, and Vaultwarden all support OIDC for their free builds. GitLab Self-Managed list SAML under Tier: Free. Planka support am until version 2.2.0 for August 2026, when e move OIDC from Community edition go Planka Pro. Grafana's open source build handle generic OAuth against your own issuer, while SAML for Grafana na Enterprise feature. Confirm am for the project's own authentication page before you install, because these lists dey change with releases.
I suppose pay for the tier wey unlock single sign-on?
Use two numbers decide am: how many people need accounts, and how many apps you for otherwise maintain by hand. For one or two administrators, forward auth in front of local account dey enough, and the paid tier no buy you much. For team where people dey join and leave, one account wey you forget during offboarding fit cost pass the licence, and the payment dey fund the maintenance wey you dey depend on. If the price no fit your budget, the practical move na to choose app wey include OIDC instead of trying to work around one wey no include am.