Skip to content
StitchOps

Blog

What a custom SCIM connector really costs

Building your own provisioning connector looks like a two week project. Here is every cost that shows up after the first version works, and a worksheet to estimate yours.

, Cofounder and CEO ·

When an app has no SCIM, the engineering answer is often "we will build a connector". The first version usually works in a couple of weeks. The cost that matters comes after.

What you are actually building

A SCIM connector sits between your identity provider and the app. It has to:

  • Accept SCIM requests to create, update, deactivate and look up users, and answer in the format the identity provider expects.
  • Translate each request into the app's API calls, or into actions on its admin screens if there is no API.
  • Store and rotate the credentials it uses, without exposing them.
  • Retry safely when the app is slow or down, without creating duplicates.
  • Reconcile, so accounts created outside the connector are found.
  • Log every change so you can prove what happened.

The costs after version one

The costs after version one
CostWhat it coversHow long it lasts
BuildFirst working version, tests, identity provider configurationOnce per app
HostingA service that is always available, with TLS, backups and patchingEvery month
Security reviewThreat model, credential handling, penetration test scopeOnce, then every major change
Vendor API accessAPI add ons, rate limits, sandbox feesEvery renewal
ChangeVendor API versions, new fields, login and MFA changesEvery time the app changes
OperationsMonitoring, alerts, someone on call when a leaver is not removedFor as long as the app is used
KnowledgeThe one engineer who understands itUntil they leave

The last row is the one that ends most custom connectors. The person who built it moves on, the connector breaks quietly, and terminations go back to tickets.

Worksheet: estimate your own

For each app you are considering, write down:

  1. Engineering days for the first version, then double it for testing and identity provider setup.
  2. Monthly hosting and monitoring cost for one more always on service.
  3. Any API fee or plan upgrade the vendor requires for API access.
  4. Expected vendor changes per year, times the days each one takes.
  5. On call hours per month, at your fully loaded engineering rate.
  6. Multiply years two and three, because the connector does not retire when it ships.

Banks we have spoken with were quoted custom integration projects for core systems that cost more than the governance tool they were meant to feed. That is not unusual.

When building makes sense

Build when the app is central to your product, has a stable and well documented API, and you have a team that will own the connector for years. For everything else, the connector is a liability on your balance sheet of attention.

The alternative

StitchOps runs provisioning for apps with or without an API, anywhere a person can log in and act. Monitoring, logs for every action and updates when the app changes are included in the per app price. There is no service for you to host, and no single engineer who has to remember how it works.

See build vs buy for identity integrations for the decision framework, or pricing.

Frequently asked questions

What is a custom SCIM connector?
A service your team builds and runs that accepts SCIM requests from your identity provider and translates them into actions in an app that does not support SCIM, usually through the app's API.
Why does a custom connector cost more than expected?
The first version is the small part. Hosting, security review, credentials, error handling, reconciliation, monitoring, vendor API changes and the person on call for it continue for as long as the app is in use.
What if the app has no API?
Then a custom connector has nothing to call. Teams either automate the app's admin screens themselves, which is harder to maintain, or keep the work manual.
What is the alternative?
StitchOps runs provisioning for apps with or without an API, anywhere a person can log in and act, priced per app with monitoring and updates when the app changes included.

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.