Build vs buy for identity integrations: a decision framework
When to build your own connector, when to pay the vendor's upgrade, and when to buy automation for the apps in between. A framework IT, security and finance can agree on.
Thomas Bieser, Cofounder and CEO ·
Every company with an identity provider ends up with the same list: apps the identity provider cannot fully manage. For each one there are five options, and most teams pick by habit instead of by rule.
The five options
- Use the catalog integration. Free if your plan includes it. Always check first.
- Pay the upgrade. Move the app to the plan with SCIM, charged on every seat. See the SCIM tax.
- Build a connector. Your team writes and runs the integration. See what a custom SCIM connector really costs.
- Keep it manual. Tickets, spreadsheets and admin consoles.
- Buy automation. A vendor runs provisioning on the plan you have, including apps with no API.
The framework
Score each app on four questions.
| Question | Points toward |
|---|---|
| Does our current plan already include SCIM | Use it |
| Do we need other features on the higher plan, or SSO that only comes with SCIM | Pay the upgrade |
| Is the app core to our product, with a stable API and a team to own a connector for years | Build |
| Is the app low risk, rarely used and holding no sensitive data | Keep it manual, and review it |
| Everything else | Buy automation |
Most lists end up mostly in the last row. That is the point of the exercise: it makes visible how many apps are being handled by habit.
What each option really costs
- Upgrade: seat price difference times seats, every year, growing with headcount.
- Build: engineering time, hosting, security review, vendor API fees, maintenance and on call, for as long as the app is used.
- Manual: admin minutes for every joiner, mover and leaver, plus seats paid for leavers, plus the risk of the account nobody removed.
- Buy: a per app price, with the vendor carrying build, hosting and maintenance.
The SCIM tax calculator puts the upgrade and manual numbers side by side for your headcount.
Questions finance will ask
- What does it cost in year three, not year one. Builds and upgrades both grow.
- What happens when the person who owns it leaves. Built connectors and manual processes depend on people.
- How do we prove it to an auditor. Every option needs evidence of who changed what and when.
Where StitchOps fits
StitchOps is the "buy automation" option. It carries your identity provider's lifecycle events into apps where SCIM costs extra or does not exist, anywhere a person can log in and act, priced per app with volume discounts. Your identity provider stays the source of truth, its catalog integrations keep doing what they do, and the apps in between stop being a ticket queue.
See pricing.
Frequently asked questions
- What are the options for connecting an app to our identity provider?
- Use the catalog integration if your plan includes it, pay the vendor to upgrade, build a connector yourself, keep the work manual, or buy automation that works on the plan you have.
- When should we build our own identity integration?
- When the app is core to your business, has a stable documented API, and a team will own the connector for years.
- When should we pay the vendor's upgrade?
- When you need other features on the higher plan, or when SSO and SCIM are sold together and you require SSO.
- What does buying automation change?
- It moves the cost of building, hosting and maintaining connectors to a vendor, and it covers apps with no API at all.