Problem

The SSO tax

Also called the SSO wall, or the enterprise tax on single sign-on.

Charging more for single sign-on looks like a pricing decision. For the team paying it, it is a security decision, and usually the wrong one gets made.

The SSO tax is the premium a software vendor charges for single sign-on, usually by offering it only on its most expensive plan. It makes the secure way to sign in a luxury, so smaller teams, who can least afford a breach, are the ones left managing a separate password for every app.

How big the markup is

The catalog at sso.tax lists vendors that offer competitive starter plans and gate SSO behind an "Enterprise" paywall. It leaves out free and single-person plans, and anyone whose SSO costs less than a 10% price increase. It lists around 150 vendors, and 44 of them will not publish the SSO price at all: it is "contact sales". Some of the rows, as the catalog shows them:

VendorPrice increase for SSORow last updated
Railway9,900%February 2026
GitHub425%April 2020
HubSpot Marketing233%September 2025
Slack72%June 2023
Adobe Creative Cloud66%July 2023
Zoom25%October 2023

Read the dates before quoting a number: plans change, and some rows are years old. Check the vendor's own pricing page before a negotiation. The pattern holds even where the numbers move: the jump to SSO is rarely a feature price. It is a different plan, with everything else on it.

Why vendors charge it

1Password's explainer on the backlash names three reasons: the real cost of building and supporting SSO, the profit (Money. Really, that's the main reason.) and its use as a segmentation lever, the feature that marks a customer as an enterprise. It also offers the analogy that has stuck: SSO is like a rearview camera. It started as an extra and is now understood as a safety requirement.

The first reason is real and small. Supporting SAML and OIDC takes work. The other two explain why the price is a multiple rather than a margin.

Why it is a security problem, not just a pricing one

  • Offboarding stops working. With SSO, disabling one account in your identity provider closes every app at once. Without it, each app has its own password, and each one has to be found and closed by hand. The one that gets missed is the leaver's way back in.
  • Your MFA policy stops at the app's door. Phishing-resistant sign-in, device checks and conditional access all live in the identity provider. An app with its own password gets whatever that app offers instead.
  • Nobody can answer "who has access?" Membership of an SSO app is visible in one place. Local accounts are visible only inside each app, to whoever is an admin there.
  • It lands on the wrong teams. A large company pays the enterprise price without noticing. A twenty-person company decides SSO is not worth it, and runs the riskier setup because it is the cheaper one.

That last point is the whole argument. A tax on the secure configuration is paid in security by the people who decline it.

What to do about each app that charges it

  1. Count them. List every app your team signs in to, and mark the ones where SSO needs a higher plan. Most teams have never seen that list, and it is shorter than they fear.
  2. Ask, in writing. Ask each vendor for SSO on your current plan. Vendors do move: Tailscale removed its own partial SSO tax in April 2024 and wrote that SSO was once again available for free for everyone. A polite request that cites the catalog costs nothing.
  3. Pay where the data is. If an app holds customer data, source code or money, the SSO plan is usually worth it. Spend the budget there, not evenly.
  4. Compensate where you will not pay. Keep those apps' credentials in a shared password manager rather than in people's heads, require each app's own MFA, and put each one on the offboarding checklist by name.
  5. Make it a buying rule. For every new tool, "SSO on the plan we would buy" goes on the requirements list, next to price. It is easier to choose a vendor that does not charge it than to negotiate with one that does.

What we do

TemprBac includes single sign-on with Entra ID, Okta and Google on every plan, from the $20-a-month Basic tier up, and on dedicated and self-hosted deployments alike. We explained why on why it costs this little: charging extra for the configuration your security team already requires is not a business we want. It is also a matter of consistency. A product that exists to end access nobody is using cannot sensibly make the leaver's password the cheaper option.

Single sign-on on every plan

Time-bound access across the systems you already run, without paying extra for the secure way to sign in to it.

Join the waitlist