The cost of SSO in open-source applications

Budget SSO across open-source and source-available apps by protocol, edition, provisioning, logout behavior and upstream licence requirements.

Last updated

In short

  • An identity provider does not unlock paid authentication features in an application.
  • OIDC or SAML login is different from provisioning, group synchronization and session revocation.
  • Build an app-by-app feature and licence matrix before quoting a shared SSO rollout.
On this page (5)

Costs and savings · Part of SSO and identity

Editable CSV with a worked example and fields for your own assessment. Example rows are illustrative, not measured results.

Download the SSO cost and entitlement worksheet

The cost of single sign-on has two sides: operating the identity provider and enabling the required behavior in every application. A free identity server does not remove an application’s paid SSO entitlement. A managed service fee pays for agreed operating work; it is not automatically an upstream software licence.

Ask what “SSO” means in this project

A procurement form often has one checkbox. An operating design needs several answers.

Capability The question it answers Separate evidence needed
OIDC or SAML login Can the user authenticate through the identity provider? Supported protocol and edition
Account creation When and how does an account appear? Just-in-time behavior or provisioning
Group/role mapping Which permissions follow identity claims? Supported claim mapping and precedence
Deprovisioning What happens when someone leaves? Account/session behavior and timing
Federation Can another directory remain the source? Trust and failure boundaries
Recovery access How does an administrator recover from IdP failure? Tested emergency access procedure

An app can support federated login while requiring an administrator to remove access elsewhere. That residual work is part of the budget.

A checked starting matrix

The following observations are based on upstream documentation checked on 17 November 2026. They are entry points for a quote, not a promise that every version or deployment has the same terms.

Application Upstream evidence Budget implication
BookStack Its OIDC guide documents federated authentication Budget configuration and lifecycle tests; check the installed release
Metabase Its SAML guide identifies the feature and plan availability Confirm the required paid edition, not just server operation
Mattermost Its edition documentation separates identity and governance features Match SSO plus history/compliance needs to the correct offering
NocoDB Its licence distinguishes internal use and commercial arrangements Confirm both hosting rights and customer feature entitlements

This table deliberately avoids a permanent yes/no claim. Upstream editions change. Record the exact feature, version, licence document and quote date in the downloadable worksheet.

Estimate the work per application

For each app, count environments and clients, not just software names. Production and staging may have separate redirect addresses, secrets and permissions. A standard OIDC client may be straightforward; a legacy app with unusual claim expectations or an external directory dependency needs more investigation.

Include initial setup, user mapping, migration of existing accounts, group tests, emergency access and documentation. Recurring work includes certificate/secret rotation, version changes and investigating login failures across two systems. If one application needs a paid enterprise edition, its fee stays visible rather than being hidden inside a generic identity line.

A hypothetical three-app project may have one included OIDC feature, one paid SAML feature and one unsupported lifecycle requirement. The budget is not simply “three times the identity-server cost.” The third requirement might need manual operation or a different product.

Test the access boundary

Use at least three test identities: an allowed user, a user in the wrong group and a former user. Check initial login, changed groups, application sessions after revocation and access through alternate login routes. Confirm that a user cannot gain privileges by supplying an unexpected claim value.

Document what remains possible during an identity-provider outage. An emergency administrator path needs controlled credentials and an audit process. It should not become a convenient everyday bypass.

Back up the relevant client configuration and required secrets before changes, using access controls appropriate to credentials. Keep a known administrative session or another approved recovery method during initial setup. A rollback restores configuration; it does not automatically reverse accounts created or permissions changed during the experiment.

Compare the entire identity estate

If Entra, Okta or another provider remains for devices or other applications, do not credit the SSO project with cancelling that whole subscription. A Keycloak federation design may coexist with the existing provider. Count only the costs that can genuinely end.

Use the worksheet to request feature-level confirmation from each supplier. Then agree the shared operating responsibility and identity service scope. This produces an auditable decision: the protocols work, the licences permit the arrangement, the remaining manual steps have owners and the recurring bill matches those facts.

Sources and further reading

Use the linked documentation to confirm the version, edition and contract that apply to your project.

Scope identity across our apps

Bring your current bill, required capabilities and workload assumptions. We will separate recurring operation from migration and retained services.