Announcing StitchOps for HR: every HR system, connected to Okta
StitchOps for HR makes any HR system the source of record for Okta, with or without an API, from $5,000 per HR system per year. Plus how one company went live in 2.5 hours.
Thomas Bieser, Cofounder and CEO ·
Today we're announcing StitchOps for HR. It makes your HR system the source of record for Okta, so every hire, role change, and departure flows from HR into Okta and on into every app Okta manages. It works with any HR system, with or without an API, and starts at $5,000 per HR system per year.
What StitchOps for HR does
Your HR system drives Okta, and Okta drives every app. There is no HRIS API or SCIM fee and no custom development, even when your HR system already offers an integration with Okta.
- Joiners. New hires are in Okta before Day 1.
- Movers. Role changes in HR update access automatically.
- Leavers. Access is removed on their last day.
- Write back. Email and username flow back to HR, so both systems agree.
- Edge cases. Rehires, leaves of absence, and contractors are handled by your policies.
- Any HR system. With or without an API.
New to the terms? Read joiner, mover, leaver: the identity lifecycle explained.
Pricing
StitchOps for HR (HR Source on our pricing page) is $5,000 per HR system per year for companies with 101 to 500 users, and pricing changes with company size. That is typically a fraction of what custom development or a vendor's annual upgrade premium would cost. See stitchops.io/pricing for every tier.
HR systems we work with
StitchOps for HR works with these HR systems, including all 10 ADP products.
Walkthroughs for some of the most common: BambooHR, Paycom, Paylocity, and Rippling.
Don't see your HR system? No problem.
If your HR system has a login, StitchOps can connect it to Okta as your source of record, often in a day. That includes regional payroll providers, PEOs, industry specific platforms, and systems built in house. Here is how to connect an HR system with no API to Okta.
This matters because HR systems are chosen for payroll, benefits, and compliance, not for identity. Your HR team should not have to switch platforms so IT can automate onboarding. Your identity program should not stall because the HR system lacks an API.
It matters even more when a company runs more than one HR system. An acquisition, a new country, or a contractor workforce often brings a second system. With StitchOps for HR, each one feeds Okta the same way, so every person follows the same joiner, mover, and leaver rules.
In practice: live in 2.5 hours
StitchOps for HR grew out of a real project. A fast growing technology company connected its HR system to Okta with 2.5 hours of hands on keyboard work, when the alternatives on the table were quoted at 90 to 120 days. Here's how it went.
The situation
The company was moving its workforce onto Okta and wanted invitations out to employees before the Thanksgiving holiday, so the IT team could start moving applications over.
Their HR system was already the source of truth for every hire, role change, and departure. What they needed was for that truth to flow into Okta on its own, with no one retyping records.
The integration the HR platform offered sat behind a premium tier, and finance could not make the total cost of ownership work. So their Okta account team brought in StitchOps to close the gap.
Why Okta and StitchOps
The team chose Okta as its identity control plane, and StitchOps to connect Okta to the HR system. The alternative paths would have cost more, taken longer, and given them less control over how employee data flowed.
| Measure | Okta and StitchOps | The alternatives |
|---|---|---|
| Time to go live | 2.5 hours of hands on keyboard work | 90 to 120 days expected |
| Annual cost | A fraction of the alternatives | Premium tier upgrade or custom development |
| Control over the data | Filters, field mapping, and sync timing set by the customer | Fixed to what the connector offered |
| Identity platform | Okta, chosen on its own merits | Shaped by what the HR platform supported |
The last row mattered most. The company wanted the best identity platform for its business, and it did not want that choice limited by which integrations its HR vendor chose to include.
The go live: 2.5 hours
The StitchOps team worked with the company's Head of IT in a shared Slack channel. The whole integration took 2.5 hours of hands on keyboard work, and the customer was blown away.
- Agree on the data. The Head of IT named the fields every Okta profile needed: name, email, department, job title, start date, work location, and manager.
- Load employees as staged. StitchOps created every user in Okta as staged, with no invitations sent, so IT could check records before anyone was told.
- Surface data gaps. The first load found 27 people with no work email in the HR system, mostly contractors. HR filled in the missing emails at the source.
- Apply policy. The Head of IT and the Head of Security chose to keep a group of high turnover contractors out of Okta. StitchOps filtered them by job title, which kept their managers in scope. When the company later reversed that decision, the change took a single request.
- Keep it in sync. Changes to title, department, manager, work location, or name now update Okta automatically. Managers are linked as real Okta users, and email changes are flagged for review so no one's login breaks.
The Head of IT set the bar for the last step:
"The idea here is that any change in [the HR system] should be captured and pushed to Okta pretty rapidly. Especially when it comes to terminations."
The sync now runs every hour.
Why it matters to every team
Connecting HR to Okta is not just an IT project. In this go live, four teams each got something they needed.
Why HR cares
HR enters a new hire once, and that person has their accounts on Day 1. No tickets to IT, no follow up emails, and no new employee waiting for access during their first week.
The HR system stays the single source of truth. When a record is wrong, the fix happens in HR and flows everywhere else, which is exactly how this project caught 27 missing work emails before launch.
Why IT cares
IT stops being the integration layer between HR and every application. Joiners, movers, and leavers flow from HR into Okta, and Okta handles access to the apps from there.
The team kept control the whole way. Users arrived staged for review, policies were set by job title rather than hard coded, and a change of plan took one request instead of a new project. That freed the Head of IT to focus on groups, applications, and the switch to Okta.
Why security cares
Offboarding is where manual processes fail. When a termination in HR reaches Okta within the hour, access ends when employment ends, not whenever someone gets to the ticket.
Security also gets a say in who belongs in the identity system at all. Here, the Head of Security decided which contractor groups should be in Okta, and the integration enforced it automatically. Every profile change traces back to a record in HR, which makes access reviews and audits simpler.
Why finance cares
Finance started this project by asking about total cost of ownership, and the answer changed the deal. Instead of an annual premium for an HR platform upgrade, or months of custom development, the company pays a fraction of either.
Finance also gets control over Okta license spend. Because policy decides who enters Okta, the company can choose whether groups such as short term contractors use a license, and change that decision whenever it wants. And every week saved on a 90 to 120 day project is a week of IT time back.
Get started
Okta customers: tell us which HR system you run, and we'll show you how it connects to Okta and what it costs. Book a call.
Okta sellers and partners: if an HR integration is holding up your deal, bring us in. Register your opportunity at stitchops.io/partners/okta.
The SSO and SCIM taxes are going away, one happy customer at a time.
Frequently asked questions
- Can any HR system be connected to Okta?
- Yes. StitchOps for HR works with any HR system, with or without an API. If your HR system has a login, StitchOps can connect it to Okta as your source of record, often in a day.
- How much does StitchOps for HR cost?
- $5,000 per HR system per year for companies with 101 to 500 users, and pricing changes with company size. It is listed as HR Source on the StitchOps pricing page.
- Do I pay an HRIS API or SCIM fee?
- No. There is no HRIS API or SCIM fee and no custom development, even when your HR system already offers an integration with Okta.
- What happens when a company runs more than one HR system?
- Each HR system feeds Okta the same way, so every person follows the same joiner, mover and leaver rules.
Product names and logos are trademarks of their respective owners. Okta is a trademark of Okta, Inc. The customer in this post is not named at their request.