Enterprise SSO and SCIM, as a service

Enterprise SSO and SCIM for your B2B app, at one flat price.

OhAuthCat adds SAML, OIDC and SCIM directory sync to your B2B app through one API. When a customer’s IT team asks for single sign-on, you say yes the same day.

No card needed. Already have an account? Sign in

  • SAML 2.0 · OIDCany identity provider
  • SCIM 2.0users and groups
  • $0for 3 + 3 connections
Sign-in · SAML · Okta
Signed in
  1. Your appRedirect to OhAuthCat9 ms
  2. OhAuthCatSign the SAML request6 ms
  3. OktaSign in with MFA1.29 s
  4. OktaPost SAML response31 ms
  5. OhAuthCatVerify signature4 ms
  6. OhAuthCatMap roles2 ms
  7. Your appFetch the profile40 ms

Every check passed1.39 s total

Directory sync · SCIM
  • user.createdpriya.nair@northwind.example
  • group.updatedEngineering · 48 members
  • user.deactivatedtom.becker@northwind.example
Illustration: one sign-in, hop by hop, and the directory changes your app receives
How it works

Every hop of a sign‑in, checked and shown

Your app makes one call. OhAuthCat talks to the customer’s identity provider, refuses anything it can’t fully verify, and hands you the same profile shape for every IdP. Directory changes arrive the same way.

meera.iyer@northwind.example signs in with Okta

Completed6 steps · 1.39 s end to end · 11 checks passed

  1. Your app

    Redirect to OhAuthCat

    One API call turns the user’s email domain into the right connection.

    • Connection found for northwind.example

    9 ms

  2. OhAuthCat

    Sign the SAML request

    We build and sign the AuthnRequest the customer’s IdP expects.

    • RSA-SHA256 request signature
    • Request ID stored for replay checks

    6 ms

  3. OktaCustomer’s IdP

    User signs in with MFA

    The customer’s own identity provider authenticates the user; you never see a password.

    • Customer’s MFA policy applied

    1.29 s

  4. OhAuthCat

    Verify the response

    The hardened validator refuses anything it cannot fully check.

    • Signature verifies against the pinned certificate
    • No wrapping, DOCTYPE or comment injection
    • Audience, destination and issuer match
    • Inside NotBefore / NotOnOrAfter
    • Assertion not seen before

    4 ms

  5. OhAuthCat

    Map the profile

    Okta’s attribute names become one profile shape, the same for every IdP.

    • Groups mapped to your roles
    • Email domain verified

    2 ms

  6. Your app

    Fetch the profile

    Your backend exchanges a one-time code for the profile.

    • PKCE code exchange
    • Session starts in your app

    40 ms

Illustration of how OhAuthCat handles a real sign-in and directory change. Names and timings are examples.

Command line

Install the CLI

The ohauthcat command manages connections, directories and exports from your terminal and CI. Install it with one command.

curl -fsSL https://ohauthcat.com/install.sh | sh

Checks the download against the release checksums, then installs to /usr/local/bin or ~/.local/bin.

Pricing

Flat pricing, never per connection

Plans are priced per project. Your bill doesn’t grow because your customers do. Prices are in US dollars.

Plans compared by price, connections and features
IncludedFreeEnough to close your first enterprise deals$0 foreverMost teams start hereProSSO live with enterprise customers$99 per monthBusinessSSO is business-critical$499 per monthEnterpriseRegulated or mission-criticalFrom $3k per month, billed annually
Production SSO connectionsOne per enterprise customer that signs in with SAML or OIDC350200Custom
Production SCIM connectionsOne per customer directory you sync350200Custom
Sandbox connectionsUnlimitedUnlimitedUnlimitedUnlimited
Monthly active end users50,000100,0001,000,000Unlimited
Permissions / roles100 / 20500 / 505,000 / 1,000Unlimited
M2M clients550500Unlimited
OAuth clients / dynamic clients / APIs5 / 1,000 / 225 / 10,000 / 10200 / 100,000 / 50Unlimited
Audit log events per month100,0001,000,00010,000,000Unlimited
Audit log retention7 days90 days1 year1 year
Feature flags202002,00010,000
Pipes providers / token fetches per month3 / 10,00025 / 100,000100 / 1,000,000Unlimited
Vault objects per environment1,000100,0001,000,000Unlimited
Every security check, setup portal, test IdPSecurity features are never gated by planIncludedIncludedIncludedIncluded
Your own branding, no badgeFree portals show OhAuthCat branding onlyNot includedIncludedIncludedIncluded
Terraform providerIncludedIncludedIncludedIncluded
Group-to-role mapping, sign-in policiesNot includedNot includedIncludedIncluded
Receive real-time access signals (SSF and CAEP)Not includedIncludedIncludedIncluded
Send real-time access signals (SSF and CAEP)Not includedNot includedIncludedIncluded
Uptime SLA with creditsNot includedNot includedIncludedIncluded
Data residencyNot includedNot included+$99/monthIncluded
BYOKNot includedNot includedNot includedIncluded

What counts as a connection? One enterprise customer signing in with SSO is one SSO connection; one customer directory syncing users with SCIM is one SCIM connection. SSO sign-ins and directory users are never metered, and there are no overage charges.Prices are in US dollars, excl. taxes. The merchant of record adds VAT or sales tax at checkout.

Work out your plan
Migration

Switching from another SSO provider

Move your connections without asking your customers’ IT admins to change anything, wherever that’s technically possible. Importers for WorkOS and Ory Polis come first.

  • If SSO runs on your own domain, point it at OhAuthCat. The identity provider sees the same URLs and the same entity ID.
  • If it runs on your old vendor’s domain, the IT admin changes one field, and we send them a pre-filled guide.
  • Profile IDs your app already stored keep matching, so there’s no data migration.
DNS for sso.yourapp.com
Before
CNAMEold-vendor.example
After
CNAMEthe target shown in your OhAuthCat dashboard

Nothing changes in your customers’ identity providers

Add SSO to your app today

The free plan is enough to close your first enterprise deals. No card needed.

Start free