Fly.io does not currently offer SCIM-based user provisioning. Stepwork automates Fly.io provisioning with 98% accuracy — no API required.
SSO without SCIM. Complexity Vector: Access spans orgs, apps, and API tokens.
You’re not wrong—infra tools get risky when offboarding depends on manual org membership and tokens. Fly.io supports SSO via Google and GitHub, but lifecycle provisioning isn’t automated, which is why teams use Stepwork to automate Fly.io flows with 98% accuracy without needing an API.
Fly.io supports OIDC sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. Fly.io does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Fly.io provisioning through interface automation — the same way a human would, but with 98% accuracy and no API required. Record the flow once, and Stepwork runs it on demand or on a schedule.
Yes. Stepwork authenticates to Fly.io through your existing identity provider (Okta, Microsoft Entra ID, 1Password, etc.) and completes MFA natively — including OTP, passkeys, and push notifications. No separate credentials or service accounts are needed.
The primary risk is no scim lifecycle.. Additional risks include org membership manual, role drift, token cleanup manual.. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in Fly.io with 98% accuracy — in a 15-minute demo.
Book a DemoNo. Stepwork completes MFA exactly like a human user — supporting OTP, passkeys, push notifications, and other methods. It signs in through your existing identity provider and OIDC, mirroring your organization's security posture.