Summary and recommendation
Better Uptime supports full SCIM 2.0 provisioning with user lifecycle management and group sync—but only on Enterprise plans that typically cost $3,100-$12,000/year. Teams on Starter ($29/month) or Pro (custom pricing) plans can't automate provisioning at all, creating manual overhead for DevOps teams that need frequent access changes for on-call rotations and incident response.
The real problem isn't just manual user management. For uptime monitoring tools, proper provisioning directly impacts incident response capabilities. When team members leave or change roles, they need immediate removal from on-call schedules and alert routing. Manual processes create dangerous gaps where alerts go to inactive users during critical outages. Better Uptime's Enterprise requirement forces teams to choose between operational security and budget constraints.
The strategic alternative
Stitchflow provides managed SCIM automation for Better Uptime without requiring the Enterprise tier upgrade. Works with any Better Uptime plan and any identity provider. Flat pricing under $5K/year, regardless of team size or plan level.
Quick SCIM facts
| SCIM available? | Yes |
| SCIM tier required | Enterprise |
| SSO required first? | Yes |
| SSO available? | Yes |
| SSO protocol | SAML 2.0 |
| Documentation | Official docs |
Supported identity providers
| IdP | SSO | SCIM | Notes |
|---|---|---|---|
| Okta | ✓ | ✓ | OIN app with full provisioning |
| Microsoft Entra ID | ✓ | ✓ | Gallery app with SCIM |
| Google Workspace | ✓ | JIT only | SAML SSO with just-in-time provisioning |
| OneLogin | ✓ | ✓ | Supported |
The cost of not automating
Without SCIM (or an alternative like Stitchflow), your IT team manages Better Uptime accounts manually. Here's what that costs:
The Better Uptime pricing problem
Better Uptime gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Plan Structure
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Starter | $29/month | ||
| Pro | Custom pricing | ||
| Enterprise | Custom ($3,100-12,000/year) |
What this means in practice
Better Uptime's custom Enterprise pricing typically ranges from $3,100 to $12,000 annually, representing a significant jump from their lower tiers. For organizations currently on Pro plans, this can mean:
The pricing gap is particularly painful because uptime monitoring tools are often considered utility services—teams need reliable provisioning but don't necessarily need all Enterprise features.
Additional constraints
Summary of challenges
- Better Uptime supports SCIM but only at Enterprise tier (Custom ($3,100-12,000/year typical))
- Google Workspace users get JIT provisioning only, not full SCIM
- Our research shows teams manually provisioning this app spend significant hidden costs annually
What the upgrade actually includes
Better Stack doesn't sell SCIM standalone. It's bundled with Enterprise features that require custom pricing:
Stitchflow Insight
The SAML prerequisite means you're forced into both SSO and SCIM together - no mixing and matching. If you just need automated user provisioning for your DevOps team, you're paying Enterprise rates ($3,100-12,000/year) for monitoring features you may not need. We estimate ~60% of Enterprise features are overkill for teams that simply want automated on-call schedule management.
What IT admins are saying
Community sentiment on Better Uptime's SCIM requirements is mixed, with cost concerns dominating smaller team discussions. Common complaints:
- Enterprise tier requirement puts SCIM out of reach for smaller DevOps teams
- The SSO prerequisite adds unnecessary complexity and cost barriers
- Custom pricing makes it difficult to budget for basic provisioning needs
- Having to negotiate enterprise deals just for identity automation
Why do I need to set up SAML first before I can even enable SCIM? Just let me automate user provisioning without jumping through SSO hoops.
We're a 15-person startup and they want us on Enterprise tier for SCIM. The pricing jump is insane for what should be basic functionality.
The recurring theme
Better Uptime gates essential provisioning behind enterprise sales processes, forcing smaller teams to either manage users manually or seek alternatives that don't require custom pricing negotiations.
The decision
| Your Situation | Recommendation |
|---|---|
| On Starter/Pro, need SCIM | Use Stitchflow: avoid the $3K-12K/year Enterprise upgrade |
| Already on Enterprise with SCIM | Use native SCIM: you're paying for it |
| Need Enterprise features beyond SCIM | Evaluate Enterprise: SCIM comes bundled |
| SSO prerequisite creates complexity | Use Stitchflow: skip the SAML setup requirement |
| Small DevOps team, low turnover | Manual may work: but monitor on-call schedule gaps |
The bottom line
Better Stack gates SCIM behind Enterprise pricing and requires SAML SSO as a prerequisite, creating barriers for teams that just want automated provisioning. For teams on lower tiers or those wanting to avoid the SSO complexity, Stitchflow delivers the same automation at flat <$5K/year pricing.
Automate Better Uptime without the tier upgrade
Stitchflow delivers SCIM-level provisioning through resilient browser automation, backed by 24/7 human in the loop for Better Uptime at <$5K/year, flat, regardless of team size.
Technical specifications
SCIM Version
2.0
Supported Operations
Create, Update, Deactivate, Groups
Supported Attributes
Not specifiedPlan requirement
Enterprise
Prerequisites
SSO must be configured first
Key limitations
- SAML SSO must be configured before SCIM
- Enterprise tier required
- User removal only detaches from org if user has other orgs
Configuration for Okta
Integration type
Okta Integration Network (OIN) app with SCIM provisioning
Prerequisite
SSO must be configured before enabling SCIM.
Where to enable
Required credentials
SCIM endpoint URL and bearer token (generated in app admin console).
Configuration steps
Enable Create Users, Update User Attributes, and Deactivate Users.
Provisioning trigger
Okta provisions based on app assignments (users or groups).
Full SCIM support. SSO must be configured first. Supports user and group provisioning.
Native SCIM is available on Enterprise. Use Stitchflow if you need provisioning without the tier upgrade.
Configuration for Entra ID
Integration type
Microsoft Entra Gallery app with SCIM provisioning
Prerequisite
SSO must be configured before enabling SCIM.
Where to enable
Required credentials
Tenant URL (SCIM endpoint) and Secret token (bearer token from app admin console).
Configuration steps
Set Provisioning Mode = Automatic, configure SCIM connection.
Provisioning trigger
Entra provisions based on user/group assignments to the enterprise app.
Sync behavior
Entra provisioning runs on a scheduled cycle (typically every 40 minutes).
SCIM endpoint: https://betterstack.com/scim/v2. Supports automatic provisioning mode.
Native SCIM is available on Enterprise. Use Stitchflow if you need provisioning without the tier upgrade.
Unlock SCIM for
Better Uptime
Better Uptime gates automation behind Enterprise plan. Stitchflow delivers the same SCIM outcomes for a flat fee.
See how it works