Kubecost does not currently offer SCIM-based user provisioning. Stepwork automates Kubecost provisioning with 98% accuracy — no API required.
SCIM Status: No SCIM; SAML is paid. Complexity Vector: Cluster and role permissions are managed across UI and RBAC, where Stepwork automates lifecycle updates.
Kubecost handles cost visibility, not identity lifecycle. Access remains manual across clusters, which is why teams use Stepwork to automate Kubecost flows with 98% accuracy without needing an API.
Kubecost supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. Kubecost does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Kubecost 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 Kubecost 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. Additional risks include manual roles, cluster access drift, offboarding gaps. Stepwork eliminates these risks by automating the entire provisioning workflow.
No. Stepwork completes MFA exactly like a human user — supporting OTP, passkeys, push notifications, and other methods. It signs in through your existing identity provider via SAML, mirroring your organization's security posture.
See how Stepwork provisions users in Kubecost with 98% accuracy — in a 15-minute demo.
Book a Demo