SSO software is software that lets your people sign in to many work tools with one login. Three quite different products are sold under that label: identity providers, which do real single sign-on; password managers, which store and fill each tool's own password; and access-management tools, which handle who has accounts but not how people log in.
They solve different problems and they're priced differently. Buying the wrong one is how a small company ends up paying for SSO and still finding ex-employees in its tools. This post explains what each kind is, what you're paying for, and which problem it fixes. Prices are from the vendors' own pages, read on 27 October 2026.
Three things sold as SSO software
| Kind | What it does at login | What you pay for | Example price, per user a month |
|---|---|---|---|
| Identity provider | Vouches for the person; the tool trusts it (SAML, OIDC) | Directory, SSO, MFA, login policies, often provisioning | Okta Starter $6; Entra ID P1 $7; JumpCloud SSO $3 |
| Password manager | Fills in the tool's own username and password | Encrypted vault, sharing, admin controls | Bitwarden Teams $4, Enterprise $6 |
| Access-management tool | Nothing; it works on accounts, not logins | Seeing and changing who has accounts in each tool | Varies; often per employee or flat |
Only the first one is single sign-on in the technical sense. The other two get called SSO because, from an employee's chair, the result looks similar: fewer passwords to type.
Identity providers
An identity provider (IdP) is the real thing. Your people sign in to it once, with MFA, and it tells each connected tool who they are, in a signed message the tool trusts. The tool never sees a password. The two standards that carry those messages are SAML 2.0, from 2005, and OpenID Connect, from 2014. When you see "SSO federation software", this is what it means: federation is the trust set up between the identity provider and each tool.
What the price buys, roughly in order of importance, starts with a directory: the list of your people, their groups and their status. On top of it sits SSO into tools that support SAML or OpenID Connect (SAML vs OIDC explains the two), and MFA, enforced at one front door instead of in thirty tools. Then come login policies, which decide which devices and countries are allowed and when to ask for extra checks. Last, and often a separate tier or add-on, is provisioning: creating and removing accounts in each tool automatically, usually through SCIM.
Prices as listed on the vendors' pages vary more than the products do. Okta lists Starter at $6 and Essentials at $17 per user a month, billed annually, with a $1,500 yearly minimum; provisioning (Lifecycle Management) is included from Essentials. Microsoft Entra ID has a free tier with "unlimited SSO" and MFA, included with Microsoft 365 or Azure, and P1 at $7 and P2 at $10 per user a month, paid yearly. JumpCloud sells SSO à la carte at $3 per user a month billed annually, or an SSO package with MFA and a password manager at $11. OneLogin lists Basic at $3, Essentials at $6 and Business at $10 per user a month, through sales. Google Workspace has no separate price: a super admin can add SAML apps to the Workspace you already pay for, and the free Cloud Identity edition does the same for up to 50 users by default.
Here is the part the price lists leave out. An identity provider can only sign people in to a tool that accepts SSO on your plan. Most tools keep SAML on Business or Enterprise. So the full cost of identity-provider SSO is the IdP plus every tool's upgrade: the SSO tax. Our SSO providers comparison prices the IdPs side by side for 20 people; this post is about what kind of thing you're buying.
Password-vault "SSO"
A password manager stores a separate, strong password for each tool and fills it in for the person. One master login opens the vault, which is why it feels like single sign-on. Technically it isn't: each tool still has its own password, and the tool has no idea a vault was involved.
Identity providers sell the same trick for tools that don't support SAML. Microsoft calls it password-based SSO, and its SSO planning guide says it is "also known as password vaulting", for apps with an ordinary HTML sign-in page. JumpCloud bundles a password manager into its SSO package.
A password manager is good at three things. It ends reused and shared passwords, which is most small companies' real password problem. It lets people share a login safely when a tool only allows one account. And it makes rotating passwords practical when someone leaves.
What it doesn't do: enforce anything at the tool. The tool still accepts that password from anyone who has it. And it doesn't remove a leaver's account from the tool.
One irony is worth knowing. Password managers charge an SSO tax of their own. On Bitwarden's business pricing page, Teams is $4 per user a month and Enterprise $6, both billed annually; logging in to Bitwarden through your identity provider ("Passwordless SSO integration") is listed on Enterprise. 1Password's business pricing page does the same: its FAQ says Business, at $8.99 per user a month billed yearly, is the plan that adds identity-provider integrations, such as unlocking the vault with SSO through Okta or Entra ID. The Teams Starter Pack below it is priced at $24.95 a month for 10 people in the page's FAQ, while the price card on the same page shows $2.49 per user. SSO vs a password manager goes deeper on the choice.
Access-management tools
The third kind doesn't touch login at all. It manages the accounts themselves: who has one in each tool, with which role, and whether they still should. That covers SaaS management platforms built for large companies, and smaller tools aimed at adding and removing people.
Why it ends up in an "SSO software" search: the reason many small companies want SSO is offboarding. They picture one switch that cuts a leaver off from everything. SSO doesn't do that. Disabling someone in the identity provider blocks their next login to connected tools, but their account, their paid seat and often their open sessions remain. Removing those is provisioning, and provisioning through SCIM is usually on an even pricier plan than SSO. Read what SCIM is for the details.
Access-management tools come at the same goal from the other side: they act on each tool's member list directly, whether or not the tool supports SSO.
Do you need software for SSO at all?
Maybe not new software. If you're on Google Workspace or Microsoft 365, you already own an identity provider, and both can do SAML SSO for many apps at no extra charge. The money goes on the tools' side, not the IdP's. Many tools also offer "Sign in with Google" or "Sign in with Microsoft" on cheap plans, which gives your people one login without enforcing it.
What does SSO software cost?
For a 20-person company, the three kinds land in different places. An identity provider costs $0 if you use Google Workspace or Entra ID Free, $720 a year for JumpCloud's à la carte SSO, $1,500 for Okta Starter because of its minimum, and $4,080 for Okta Essentials with provisioning. A password manager is $960 a year on Bitwarden Teams, or $2,157.60 on 1Password Business. An access-management tool varies too much to quote as one number; ask whether it is priced per employee, per tool or flat.
Then add the line that does not appear on any of those invoices. An identity provider only works with tools that accept SSO on your plan, and those upgrades are usually the larger bill. GitHub's Team plan is $4 a user a month and Enterprise, where SAML is listed, starts at $21; for 20 people that one upgrade is $4,080 a year, as much as Okta Essentials. Password managers and access-management tools skip that line, which is most of their appeal. SSO pricing adds up the full bill.
Mistakes people make buying SSO software
Buying an identity provider to fix passwords. If the problem is reused passwords on tools that do not offer SSO on your plan, an identity provider cannot reach them. A password manager can.
Buying a password manager to fix offboarding. Removing someone from the vault takes away the stored password, not the account. Anyone who knew or reset that password can still log in.
Buying both and still finding ex-employees in your tools. Neither one removes accounts unless provisioning is set up and the tool supports it on your plan. That is the gap the third category exists for.
Matching software to the problem
Start from the problem, not the product category:
| Your problem | What fixes it |
|---|---|
| A customer contract or audit requires enforced login via an IdP | Identity provider, plus each in-scope tool's SSO plan |
| Reused, weak or shared passwords | Password manager, plus MFA |
| Leavers keep accounts and seats in tools | Provisioning (SCIM) where offered, or an access-management tool |
| Nobody knows who has access to what | An access list, then a regular user access review |
| Too many logins for employees | "Sign in with Google/Microsoft" where free; an IdP if you need more |
Most small companies have the second, third and fourth problems, and only sometimes the first. If you aren't sure which you have, SSO for small business walks through the decision, and IAM tools covers the wider identity market.
Where SmashSSO fits
SmashSSO is in the third category. It isn't SSO: it doesn't sit in the login path or change how anyone signs in. It reads your people from Google Workspace, shows who has an account in each tool and with what role, and flags accounts that match nobody in your directory. Access bundles by role add a new person to every tool they need; role changes and removals run the same way. When someone is suspended in Google Workspace, it shows every tool they're still in.
Changes run through a tool's member API where you've added a token, or through an agent in your own Chrome, in tabs where you're already an admin. The agent needs Chrome open, is slower than an API, and can fail when a tool changes its screens; a failed run says so. Adding a paid seat always waits for approval, and every change goes in an audit log. It costs a flat fee from $199 a month billed annually (pricing). If you need enforced login, buy an identity provider; SmashSSO is for the accounts behind the login.