Finance · SCIM pricing
Carta SCIM pricing
Cap table management, equity plans and valuations. SCIM costs extra.
SCIM pricing for every app →What Okta covers for Carta, and what StitchOps adds.
Okta signs users in and manages accounts where the app supports it in the Okta Integration Network. StitchOps covers the rest of the Carta account lifecycle.
In the OIN with SWA password fill only. No SAML, OIDC or provisioning.
StitchOps covers 8 of 8 capabilities for Carta.
| Capability | Okta, from the OIN | StitchOps |
|---|---|---|
| Single sign on | Password fill only (SWA). No SAML or OIDC. | Enterprise password management signs users in to Carta with vaulted credentials. Users never need the password. |
| Shared accounts and MFA | Not part of the OIN listing. | Shares Carta logins and their MFA across a team, with credentials kept in your vault. |
| Joiners | No account creation in the OIN. | Creates the Carta account with the right role on day one, anywhere a person can log in and act. |
| Movers | No account updates in the OIN. | Changes Carta roles and access when someone changes jobs, anywhere a person can log in and act. |
| Leavers | No deprovisioning in the OIN. | Removes Carta access the day someone leaves, anywhere a person can log in and act, and saves evidence of the removal. |
| Password rotation | No password rotation in Carta. | Changes the Carta password on a schedule and the day someone leaves, and updates your vault in the same run. |
| Access reviews | No connector to read or remove Carta accounts. | Pulls the Carta user list on a schedule, compares it to your directory, and removes what you approve. |
| Audit evidence | Nothing logged inside Carta. | Step level evidence for every action StitchOps takes in Carta. |
Single sign on
Okta, from the OIN
Password fill only (SWA). No SAML or OIDC.
StitchOps
Enterprise password management signs users in to Carta with vaulted credentials. Users never need the password.
Shared accounts and MFA
Okta, from the OIN
Not part of the OIN listing.
StitchOps
Shares Carta logins and their MFA across a team, with credentials kept in your vault.
Joiners
Okta, from the OIN
No account creation in the OIN.
StitchOps
Creates the Carta account with the right role on day one, anywhere a person can log in and act.
Movers
Okta, from the OIN
No account updates in the OIN.
StitchOps
Changes Carta roles and access when someone changes jobs, anywhere a person can log in and act.
Leavers
Okta, from the OIN
No deprovisioning in the OIN.
StitchOps
Removes Carta access the day someone leaves, anywhere a person can log in and act, and saves evidence of the removal.
Password rotation
Okta, from the OIN
No password rotation in Carta.
StitchOps
Changes the Carta password on a schedule and the day someone leaves, and updates your vault in the same run.
Access reviews
Okta, from the OIN
No connector to read or remove Carta accounts.
StitchOps
Pulls the Carta user list on a schedule, compares it to your directory, and removes what you approve.
Audit evidence
Okta, from the OIN
Nothing logged inside Carta.
StitchOps
Step level evidence for every action StitchOps takes in Carta.
Okta coverage from the Okta Integration Network, read October 10, 2026. Carta on okta.com StitchOps for Okta →
SCIM and API tax
What Carta charges to automate accounts.
Carta includes SCIM provisioning only on Scale. That plan is sold by quote, so the price jump is not published.
Pricing notes
SCIM only via Okta connector and only on Scale plan (about $224 per stakeholder list). Launch flat for very small companies.
Last verified 2026-06-12 (estimate). Source · SCIM pricing for every app · Method
Pricing data includes the SCIM Tax Index (Iden), CC BY 4.0, https://scimtax.org/. Modified and extended by StitchOps.
Estimate Carta and your other apps
Loading prices.
Expected scenario, list prices, SSO required, default department shares.
Automate Carta accounts on the plan you have.
StitchOps carries what your identity provider decides into the app, through an API when one exists, and anywhere a person can log in and act when one does not.
Joiners
Create the Carta account with the right role when your HR system or identity provider says someone starts.
Movers
Change Carta roles, teams and access when someone changes department or manager.
Leavers
Remove Carta access the same day someone leaves, and free the seat.
Access checks
List who can log in to Carta on a schedule, with evidence for the audit.
Common questions.
Does Carta support SCIM?
Yes, but only on Scale, sold by quote. On the plan most teams buy, SCIM is not available.
Which Carta plan includes SCIM?
Scale. It is sold by quote.
Can Carta accounts be automated without upgrading?
Yes. StitchOps creates, changes and removes Carta accounts on the plan you already have, triggered by the events your identity provider already sends. It uses an API when one exists and works anywhere a person can log in and act when one does not.
Is Carta in the Okta Integration Network?
Yes. As of October 10, 2026, the OIN lists Carta with SWA sign in and no provisioning.
Can Okta deprovision Carta users?
Not through an OIN connector. StitchOps removes Carta accounts the day someone leaves, anywhere a person can log in and act, and saves evidence of each removal.
How do you rotate Carta passwords when someone leaves?
StitchOps logs in to Carta, sets a new password, confirms it took effect, and updates 1Password, Keeper or the StitchOps vault in the same run.
Last updated . Product names are trademarks of their respective owners. StitchOps is not affiliated with or endorsed by them.
Start with one workflow that never had an API.
Fifteen minutes on your top three manual processes. We tell you which one to run first.