HR, payroll and benefits · US and Canada
Remote as the source for Okta, for people hired anywhere.
StitchOps uses Remote as the source for Okta. People you hire through Remote in any country are in Okta before day one, role changes update their access, and leavers are removed on their last day.
HR Source pricing →What's hard about Remote today.
Remote employs your people in countries where you have no entity, and pays contractors around the world. IT still has to give them access, and without a connection to Okta, new starters abroad wait for an email and contractors keep access after their engagement ends.
What StitchOps does in Remote.
Joiners in Okta before day one
When HR adds a new hire in Remote, StitchOps creates them in Okta before their start date, so Okta can give them the apps their role needs on day one.
Employees and contractors
Employees hired through Remote and contractors paid through it each follow their own Okta rules, including end dates for contractors.
Role changes that update access
When Remote shows a new job, department, manager or location, StitchOps updates the person in Okta, and Okta adds and removes app access to match.
Leavers removed on their last day
When a last day arrives in Remote, StitchOps deactivates the person in Okta, and Okta removes their access in every app it manages.
Email and username written back
Once Okta has the new person's email and username, StitchOps writes them back to their record in Remote, so HR and IT see the same details.
No API fee, no custom development
StitchOps does not need a paid Remote API, a SCIM upgrade or a custom integration. It reads changes the way your HR team sees them, or uses a connection you already have.
Before and after.
What Okta covers for Remote, 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 Remote account lifecycle.
In the OIN with sign in and partial provisioning.
StitchOps covers 6 of 8 capabilities for Remote.
| Capability | Okta, from the OIN | StitchOps |
|---|---|---|
| Single sign on | No SAML or OIDC in the OIN. | Enterprise password management signs users in to Remote with vaulted credentials. Users never need the password. |
| Shared accounts and MFA | Not part of the OIN listing. | Shares Remote logins and their MFA across a team, with credentials kept in your vault. |
| Joiners | Creates accounts through the OIN connector. | Needed if your Remote plan doesn't include SCIM. Creates the Remote account with the right role on day one, anywhere a person can log in and act. |
| Movers | Updates accounts through the OIN connector. | Needed if your Remote plan doesn't include SCIM. Changes Remote roles and access when someone changes jobs, anywhere a person can log in and act. |
| Leavers | No deprovisioning in the OIN. | Removes Remote access the day someone leaves, anywhere a person can log in and act, and saves evidence of the removal. |
| Password rotation | No password rotation in Remote. | Changes the Remote password on a schedule and the day someone leaves, and updates your vault in the same run. |
| Access reviews | No connector to read or remove Remote accounts. | Pulls the Remote user list on a schedule, compares it to your directory, and removes what you approve. |
| Audit evidence | Nothing logged inside Remote. | Step level evidence for every action StitchOps takes in Remote. |
Single sign on
Okta, from the OIN
No SAML or OIDC in the OIN.
StitchOps
Enterprise password management signs users in to Remote with vaulted credentials. Users never need the password.
Shared accounts and MFA
Okta, from the OIN
Not part of the OIN listing.
StitchOps
Shares Remote 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
Needed if your Remote plan doesn't include SCIM. Creates the Remote account with the right role on day one, anywhere a person can log in and act.
Movers
Okta, from the OIN
Updates accounts through the OIN connector.
StitchOps
Needed if your Remote plan doesn't include SCIM. Changes Remote roles and access when someone changes jobs, anywhere a person can log in and act.
Leavers
Okta, from the OIN
No deprovisioning in the OIN.
StitchOps
Removes Remote access the day someone leaves, anywhere a person can log in and act, and saves evidence of the removal.
Password rotation
Okta, from the OIN
No password rotation in Remote.
StitchOps
Changes the Remote password on a schedule and the day someone leaves, and updates your vault in the same run.
Access reviews
Okta, from the OIN
No connector to read or remove Remote accounts.
StitchOps
Pulls the Remote user list on a schedule, compares it to your directory, and removes what you approve.
Audit evidence
Okta, from the OIN
Nothing logged inside Remote.
StitchOps
Step level evidence for every action StitchOps takes in Remote.
Okta coverage from the Okta Integration Network, read October 24, 2026. Remote.com on okta.com StitchOps for Okta →
Common questions.
Do we need a Remote API or SCIM connection?
No. StitchOps reads hires, changes and terminations from Remote the way your HR team sees them. If your team already has a connection in place, StitchOps can use it instead.
Remote employs our people, not us. Who owns the Okta setup?
You do. Remote stays the employer of record and runs payroll. StitchOps reads your people from Remote and makes the changes in your own Okta, under your rules.
What login does StitchOps need in Remote?
A login that can see hires, job changes and terminations, kept in your vault (1Password or Keeper) or the StitchOps vault. StitchOps runs on a dedicated worker VM in your environment, and models never see the credentials.
How is HR Source priced?
HR Source is priced per HR system per year, by company size, with no Remote API or SCIM fee on top. Prices are on our pricing page, and Connect for each app is priced separately.
How long does it take to connect Remote?
If StitchOps can log in to Remote, it can often be connected in a day. A 30 day pilot can prove it in your own Okta before you sign.
Is Remote in the Okta Integration Network?
Yes. As of October 24, 2026, the OIN lists Remote.com with no sign in and provisioning to create and update users.
Can Okta deprovision Remote users?
Not through an OIN connector. StitchOps removes Remote accounts the day someone leaves, anywhere a person can log in and act, and saves evidence of each removal.
How do you rotate Remote passwords when someone leaves?
StitchOps logs in to Remote, sets a new password, confirms it took effect, and updates 1Password, Keeper or the StitchOps vault in the same run.
For your IT team
- Where it runs
- An agent runs an unattended desktop session on a dedicated worker VM in your environment, on Windows or macOS. It connects outbound only over TLS 1.2 or later. No inbound ports are opened.
- Credentials
- Credentials stay in your vault (1Password or Keeper) or in the StitchOps vault, encrypted with AWS KMS and resolved on the worker at run time. Models never see the values.
- Okta stays the source of truth
- StitchOps creates, updates and deactivates people in Okta from your HR system, and Okta Lifecycle Management carries the change to every app. StitchOps is listed in the Okta Integration Network.
- Logs and telemetry
- Every run keeps step level logs with status, timing and redacted results. Telemetry is content free: no field values, no personal data, no screenshots.
- Security reviews
- SOC 2 Type 2 examination completed, with HIPAA and GDPR Article 5 attestations, by Sensiba LLP. Penetration tested by a third party. ISO 27001 certification being finalized. The security packet is shared under NDA.
Last updated . Product names are trademarks of their respective owners. StitchOps is not affiliated with or endorsed by them.
See it run in your Remote.
Fifteen minutes on how Remote reaches Okta today. We show you joiners, movers and leavers running from it.