Vercel SSO is sold to Pro teams as a SAML add-on at $300 a month, flat, on top of the $20 a month for each paid seat. That is $3,600 a year whether you have 3 developers or 30. SCIM (Vercel calls it Directory Sync) is Enterprise only.
Those prices are from Vercel's pricing page and its Pro plan docs, as we read them on 27 October 2026. A flat fee is kinder to big teams than a per-seat upgrade and much harsher to small ones. Below: the plans, the sums at different team sizes, what Enterprise adds, how the setup works, the login controls Pro already has, how to remove someone from a Vercel team, and what to do instead.
Vercel's plans and SSO
| Plan | Price | SAML SSO | Directory Sync (SCIM) |
|---|---|---|---|
| Hobby | $0 | No | No |
| Pro | $20 a month platform fee, then $20 a month per extra paid seat | $300 a month add-on | No |
| Enterprise | Custom | Yes | Yes |
Vercel's docs explain how Pro is billed. The $20 platform fee includes one deploying seat and $20 of monthly usage credit. Each extra paid seat, meaning an Owner or Member, the roles that can configure and deploy, is $20 a month. Viewer seats are free and unlimited: viewers can see deployments and analytics and comment on previews, but can't deploy. And Pro is billed monthly, on seats, add-ons and any usage beyond the credit; Vercel's docs don't describe an annual Pro price.
The SAML SSO add-on is listed under "Paid add-ons" at $300 a month. Vercel's SAML docs say SAML "is available on Enterprise and Pro plans" and that Pro teams "will first need to purchase the SAML SSO add-on from their Billing settings."
Directory Sync, which creates and removes team members from your identity provider, is an Enterprise feature. The SAML page says so directly: for automatic provisioning and de-provisioning, "consider upgrading to Directory Sync, which is available on Enterprise plans." That split, login on one tier and lifecycle on the next, is the same one we explain in SCIM vs SAML.
The add-on price
| Tool | Plan without SSO | Cheapest plan with SSO | Extra a year, 20 people |
|---|---|---|---|
| Vercel | Pro · $0 | Pro + SAML SSO add-on · $300 | $3,600 |
| Total SSO tax a year | $3,600 | ||
That table shows the add-on alone. What it does to a real Pro bill depends on how many people need to deploy. Leaving out usage charges:
| Paid seats | Pro seats, a year | With SAML add-on, a year | Increase |
|---|---|---|---|
| 5 | $1,200 | $4,800 | 300% |
| 10 | $2,400 | $6,000 | 150% |
| 20 | $4,800 | $8,400 | 75% |
| 50 | $12,000 | $15,600 | 30% |
The sums: on Pro, every paid seat effectively costs $20 a month, the first one through the platform fee, so N seats cost N × $20 × 12 a year. The add-on is $300 × 12 = $3,600 a year on top. Ten paid seats: $2,400 + $3,600 = $6,000.
For a five-person engineering team, SAML quadruples what Vercel charges for seats. That's the SSO tax at its most lopsided, and the reason flat add-ons hit small teams hardest; our post on per-seat pricing shows the opposite shape, where the bill grows with every hire. If you're tallying tools, the SSO tax calculator handles flat fees and per-seat upgrades side by side.
What Enterprise adds
Because SAML on Pro is a bolt-on, the plan that bundles identity features is Enterprise, at a custom price. On the pricing page as we read it on 27 October 2026, Enterprise lists SAML SSO together with Directory Sync (SCIM), audit logs, team- and project-level role-based access control, SSO-protected previews, a custom security questionnaire, and platform SLAs and support. Vercel's team member docs also put project-level roles on Enterprise only: on Pro, a person's role applies across every project in the team.
That last point matters more than SSO for some teams. On Pro, a contractor you add as a Member to deploy one client project gets that role across every project in the team. Enterprise's project roles are how you narrow it. If you need that, audit logs or SCIM, Enterprise is a real conversation. If you need only the login, it's a $300 a month add-on or nothing.
Setting it up
You need to be an Owner of the team and have the add-on bought. Select the team in the team switcher, open Settings, then Security & Privacy. In the Authentication and User Provisioning section, find the SAML row and click Configure, then follow the walkthrough for your identity provider. Vercel supports a long list, including Okta, Microsoft Entra ID, Google, OneLogin, JumpCloud, Duo and generic SAML.
To make SAML compulsory, an Owner who is currently signed in through SAML turns on Require Team Members to login with SAML in the same section. Members then can't see anything in the team unless their session came through SAML. Changing the SAML configuration later switches enforcement off until you test and turn it back on.
People sign in by choosing Continue with SAML SSO on Vercel's login page and entering the team's slug, the name in your team URL. Sessions last 24 hours by default; a session_lifetime attribute from your identity provider can set anything from one day to 30 days.
Two behaviors are worth knowing before you switch it on. New sign-ups join automatically: Vercel says "any new users signing up with SAML will automatically be added to your team." Check which role they get, because Owner and Member seats are paid. Removals stay manual: on Pro, after someone joins, "you manage team member roles and removals manually through the Vercel dashboard."
The login controls Pro already has
Before paying for the add-on, use what's in Pro. Vercel's pricing page lists OAuth sign-in with GitHub, Google, GitLab and Bitbucket, and MFA, on Hobby, Pro and Enterprise alike. If your team signs in with company Google or GitHub accounts, those accounts carry your company's own rules.
The stronger control is two-factor enforcement. An Owner who has 2FA on their own account opens Team Settings, then Security & Privacy, scrolls to Two-Factor Authentication Enforcement, switches it on and saves. As we read the docs on 27 October 2026, members without 2FA then can't reach team resources until they set it up, though they keep their seat. Builds fail for them, and CI/CD tokens tied to them stop working, which is worth a warning in your team chat before you flip the switch. Owners can filter the Members page by 2FA status to see who is left. Our post on SSO vs MFA explains how much of the login risk this covers.
Removing members from a Vercel team
Owners remove members on any team plan. Select the team in the team switcher, open Settings, then Members, click the ... next to the person and choose Remove from Team.
A team can't be left without an Owner, so promote someone else before removing the last one. Vercel's docs we read don't say whether a removed seat is credited partway through a billing cycle; check your billing page. Pending invitations are worth a glance too: an invite stays open for 7 days, or 30 days on teams that enforce SAML, so check the list and withdraw any invite you no longer want accepted.
When an engineer leaves, removing them from the team is only part of the job. Access tokens they created for CI or scripts should be revoked, and anything they could have copied rotated. Environment variables they could read, such as API keys and database URLs, are the bigger risk: rotate the secrets that matter, because removing the person doesn't change a key they already saw. Your Git provider needs the same treatment: if your projects deploy from GitHub or GitLab, remove them from your Git organization too; our post on GitHub Enterprise pricing covers GitHub organization removals. And domains and projects registered under their personal account should move to the team before they go. Our post on revoking access covers what happens when that step is skipped, and the employee offboarding checklist covers the rest of their tools.
Alternatives
Before paying $3,600 a year for a login button, four steps get a small team most of the way there.
Use the sign-in methods Pro already has, and ask everyone to sign in with their company Google or GitHub account. Enforce two-factor authentication for the whole team. Keep paid seats for deployers: everyone else can be a free Viewer, which also keeps the people who only look out of your secrets. Remove leavers the same day and rotate their secrets, which is the part SAML on Pro wouldn't automate anyway.
Real SSO becomes worth it when a customer contract or an auditor names it, or the team grows to where the flat fee is a small slice of the bill. At 50 paid seats the add-on is a 30% increase; at 5, it is 300%.
Where SmashSSO fits
SmashSSO adds and removes Vercel team members from the same place as your other tools, on Pro without the add-on. It reads your people from Google Workspace, reads your Vercel team members and roles, and matches them by email; members who match nobody in your directory are flagged. When someone is suspended in Google Workspace, it alerts you and shows Vercel among the tools they're still in.
Vercel has a member API, so once you add a team ID and an access token, SmashSSO's changes go through it. Without a token, an agent does the work in your own Chrome, where you're signed in as an Owner; that needs the browser open, is slower, and can fail if Vercel redesigns its dashboard, in which case the run says so and shows its last screenshot. Giving someone an Owner or Member role adds a $20 seat, so that step waits for your approval. Every change is in the audit log. It doesn't rotate secrets for you.
It isn't SSO. If you need SAML login enforced on Vercel, buy the add-on. If you need the team list to match the people who work for you, SmashSSO does it for a flat fee from $199 a month billed annually, covering every tool, not just Vercel (pricing).