Skip to content
StitchOps

Engineering · SCIM pricing

Bytebase SCIM pricing

Database schema change management and access control for developers. SCIM costs extra.

SCIM pricing for every app →

What Okta covers for Bytebase, 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 Bytebase account lifecycle.

Not in the Okta Integration Network.

StitchOps covers 8 of 8 capabilities for Bytebase.

  • Single sign on

    Okta, from the OIN

    No SAML or OIDC in the OIN.

    StitchOps

    Enterprise password management signs users in to Bytebase with vaulted credentials. Users never need the password.

  • Shared accounts and MFA

    Okta, from the OIN

    Not part of the OIN listing.

    StitchOps

    Shares Bytebase logins and their MFA across a team, with credentials kept in your vault.

  • Joiners

    Okta, from the OIN

    No account creation in the OIN.

    StitchOps

    Creates the Bytebase account with the right role on day one, anywhere a person can log in and act.

  • Movers

    Okta, from the OIN

    No account updates in the OIN.

    StitchOps

    Changes Bytebase 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 Bytebase 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 Bytebase.

    StitchOps

    Changes the Bytebase 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 Bytebase accounts.

    StitchOps

    Pulls the Bytebase user list on a schedule, compares it to your directory, and removes what you approve.

  • Audit evidence

    Okta, from the OIN

    Nothing logged inside Bytebase.

    StitchOps

    Step level evidence for every action StitchOps takes in Bytebase.

Okta coverage from the Okta Integration Network, read October 10, 2026. Bytebase has no OIN listing. StitchOps for Okta →

SCIM and API tax

What Bytebase charges to automate accounts.

Bytebase includes SCIM provisioning only on Enterprise. That plan is sold by quote, so the price jump is not published. The plan most teams buy is Pro, $20 per user a month.

SSO sits on the same plan as SCIM or above it. If you need SSO anyway, that upgrade is not avoidable, and the calculator counts it that way.

Pricing notes

Free, Pro $20 per user a month cloud only, Enterprise custom yearly. SCIM, 2FA, audit log Enterprise only.

Last verified 2026-06-12 (estimate). Source · SCIM pricing for every app · Method

Pricing data includes the SCIM Tax Index (Iden), CC BY 4.0, https://scimtax.org/. Modified and extended by StitchOps.

Estimate Bytebase and your other apps

Loading prices.

Tune it in the full calculator

Expected scenario, list prices, SSO required, default department shares.

Automate Bytebase accounts on the plan you have.

StitchOps carries what your identity provider decides into the app, through an API when one exists, and anywhere a person can log in and act when one does not.

Joiners

Create the Bytebase account with the right role when your HR system or identity provider says someone starts.

Movers

Change Bytebase roles, teams and access when someone changes department or manager.

Leavers

Remove Bytebase access the same day someone leaves, and free the seat.

Access checks

List who can log in to Bytebase on a schedule, with evidence for the audit.

Common questions.

Does Bytebase support SCIM?

Yes, but only on Enterprise, sold by quote. On the plan most teams buy, SCIM is not available.

Which Bytebase plan includes SCIM?

Enterprise. It is sold by quote.

Can Bytebase accounts be automated without upgrading?

Yes. StitchOps creates, changes and removes Bytebase accounts on the plan you already have, triggered by the events your identity provider already sends. It uses an API when one exists and works anywhere a person can log in and act when one does not.

Is Bytebase in the Okta Integration Network?

No. As of October 10, 2026, the OIN has no listing for Bytebase. Okta can sign users in only through a custom app if Bytebase supports SAML or OIDC, and has no connector to manage Bytebase accounts.

Can Okta deprovision Bytebase users?

Not through an OIN connector. StitchOps removes Bytebase accounts the day someone leaves, anywhere a person can log in and act, and saves evidence of each removal.

How do you rotate Bytebase passwords when someone leaves?

StitchOps logs in to Bytebase, sets a new password, confirms it took effect, and updates 1Password, Keeper or the StitchOps vault in the same run.

Last updated . Product names are trademarks of their respective owners. StitchOps is not affiliated with or endorsed by them.

Start with one workflow that never had an API.

Fifteen minutes on your top three manual processes. We tell you which one to run first.