Engineering · SCIM pricing
PagerDuty SCIM pricing
On call management and incident response alerting. SCIM costs extra: 2 times the price of the plan most teams buy.
SCIM pricing for every app →What Okta covers for PagerDuty, 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 PagerDuty account lifecycle.
In the OIN with SAML or OIDC sign in and provisioning.
StitchOps covers 1 of 8 capabilities for PagerDuty.
| Capability | Okta, from the OIN | StitchOps |
|---|---|---|
| Single sign on | SAML or OIDC from the OIN listing. | Not needed. |
| Shared accounts and MFA | Not part of the OIN listing. | Shares PagerDuty logins and their MFA across a team, with credentials kept in your vault. |
| Joiners | Creates accounts through the OIN connector. | Not needed. |
| Movers | Updates accounts through the OIN connector. | Not needed. |
| Leavers | Deactivates accounts through the OIN connector. | Not needed. |
| Password rotation | Not needed for users who sign in with SAML or OIDC. | Rotates shared admin logins in PagerDuty on a schedule or after an offboarding. |
| Access reviews | The connector lets Okta read and remove PagerDuty accounts for reviews. | Not needed for reviews of assigned access. |
| Audit evidence | Okta logs the changes its connector makes. | Not needed. |
Single sign on
Okta, from the OIN
SAML or OIDC from the OIN listing.
StitchOps
Not needed.
Shared accounts and MFA
Okta, from the OIN
Not part of the OIN listing.
StitchOps
Shares PagerDuty logins and their MFA across a team, with credentials kept in your vault.
Joiners
Okta, from the OIN
Creates accounts through the OIN connector.
StitchOps
Not needed.
Movers
Okta, from the OIN
Updates accounts through the OIN connector.
StitchOps
Not needed.
Leavers
Okta, from the OIN
Deactivates accounts through the OIN connector.
StitchOps
Not needed.
Password rotation
Okta, from the OIN
Not needed for users who sign in with SAML or OIDC.
StitchOps
Rotates shared admin logins in PagerDuty on a schedule or after an offboarding.
Access reviews
Okta, from the OIN
The connector lets Okta read and remove PagerDuty accounts for reviews.
StitchOps
Not needed for reviews of assigned access.
Audit evidence
Okta, from the OIN
Okta logs the changes its connector makes.
StitchOps
Not needed.
Okta coverage from the Okta Integration Network, read October 10, 2026. PagerDuty on okta.com StitchOps for Okta →
SCIM and API tax
What PagerDuty charges to automate accounts.
PagerDuty includes SCIM provisioning only on Business, at $41 per user a month. That is 2 times the price of the plan most teams buy (Professional, $21 per user a month). For 100 users, the SCIM tax comes to about $24,000 a year.
Pricing notes
Status changed from free to gated. Native SCIM now requires Business or Enterprise plan; Professional tier does not include SCIM.
Last verified 2026-06-12. 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 PagerDuty and your other apps
Loading prices.
Expected scenario, list prices, SSO required, default department shares.
Automate PagerDuty 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 PagerDuty account with the right role when your HR system or identity provider says someone starts.
Movers
Change PagerDuty roles, teams and access when someone changes department or manager.
Leavers
Remove PagerDuty access the same day someone leaves, and free the seat.
Access checks
List who can log in to PagerDuty on a schedule, with evidence for the audit.
Common questions.
Does PagerDuty support SCIM?
Yes, but only on Business, at $41 per user a month. On the plan most teams buy, SCIM is not available.
Which PagerDuty plan includes SCIM?
Business, at $41 per user a month, against Professional, $21 per user a month for the plan most teams buy. At 100 users the difference is about $24,000 a year.
Can PagerDuty accounts be automated without upgrading?
Yes. StitchOps creates, changes and removes PagerDuty 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 PagerDuty in the Okta Integration Network?
Yes. As of October 10, 2026, the OIN lists PagerDuty with SAML, SWA sign in and provisioning to create, update and deactivate users.
Can Okta deprovision PagerDuty users?
Yes. The OIN connector deactivates PagerDuty accounts when a user is removed in Okta.
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.