KeyHasp

No SSO tax

Offboarding you can trust, without the SSO tax.

Many SaaS tools keep SSO and SCIM for the enterprise plan, which can cost up to 10x more. KeyHasp revokes, verifies and records every departure on the plan you already have.

30+ connectors. Google Workspace, Microsoft and Okta.

An offboarding report in the KeyHasp dashboard, with fictitious data.

The SSO tax

Enterprise prices to remove one account.

Many vendors keep SSO and SCIM for their most expensive plan. Teams often pay that upgrade for one reason: to be sure that when someone leaves, their access goes with them.

  • 10xwhat gating SSO can add to the bill, or more
  • +425%GitHub: $4 to $21 per user/month for SSO
  • +350%SendGrid: $20 to $90 per month for SSO

Increase over the base plan for teams of five or more, as listed on sso.tax · checked

KeyHasp does the part you were buying SSO for. It removes people from every connected tool through the tool's own user-management API, on the plan you already pay for.

Offboarding

When someone leaves, their access leaves too.

Without SSO, offboarding is a checklist someone runs by hand. The account in the tool nobody remembered stays open.

  • Triggered by the directory

    Suspending or deleting someone in your identity provider (Google Workspace, Microsoft or Okta) starts the offboarding. A full directory sync every 15 minutes backs up real-time events.

  • Revokes what really exists

    KeyHasp reads each tool again first, so it removes the accounts that actually exist, including ones it never created. Each tool runs on its own: one failure never blocks the rest.

  • Verifies every revocation

    A step only succeeds once the tool, read back, confirms that the account is gone or suspended.

  • Never a silent failure

    Every run produces a report with timestamps, actions and the tool's own request ids as evidence. A step that still fails after bounded retries becomes a task with an owner.

Their KeyHasp session ends on their next request, too.

How it works

Your directory decides. KeyHasp carries it out.

  • Directory

    Google, Microsoft or Okta

    The source of truth for who works here. KeyHasp mirrors people and listens for changes.

  • KeyHasp

    KeyHasp cloud

    Runs on AWS, isolated per company, and compares who should have access with what each tool reports.

  • Tools

    Each tool's own API

    Changes go through each tool's user-management API, with a credential scoped to exactly that.

See how it works

Connectors

30+ connectors. More every day.

Your identity provider on one side, your team's tools on the other.

Identity providers

  • Google WorkspaceLive
  • MicrosoftLive
  • OktaLive

Tools

  • GitHubLive
  • AWSLive
  • SentryLive
  • SendGridLive
  • ClaudeLive
  • CursorLive
  • CodeRabbitLive
  • and 30+ more

Security model

Built to be trusted with access.

  • Scoped keys, never root

    Each connector uses a credential limited to user management. For GitHub, an App with only the Members permission and no access to code.

  • Isolated per company

    Each company is its own tenant, walled off in the database itself, and its tool credentials are encrypted with keys bound to it.

  • Sign in with your company account

    People sign in through your identity provider. There are no KeyHasp passwords, and leaving the directory ends the session.

  • Mass-termination guard

    A directory sync that would offboard more than three people or 20% of the company, whichever is larger, is aborted without changes.

  • 1GitHub App permission: Members
  • 0KeyHasp passwords
  • 15 minbetween full directory syncs
  • 20%the most one sync may offboard

SOC 2Audit in progress

Read the security model

Day to day

Know who can reach what, today.

The matrix shows what each tool actually reports, not what someone thinks was granted. Accounts that no person is linked to show up as unlinked instead of hiding.

The who-has-what matrix for a GitHub organization, with fictitious data.

Features

The rest of the lifecycle, in one place.

Offboarding is the reason to start. These cover the rest of the access lifecycle.

  • Onboarding with role templates

    A hire gets the accounts of their role, with least privilege. Production access is never part of a template.

  • Access requests and temporary access

    Request, approve, and let access expire on its own. Production access always has an end date.

  • Orphan accounts as tasks

    Accounts with no active person behind them become tasks with an owner.

  • Audit log

    Every change and every tool call, browsable in the dashboard.

FAQ

Questions.

Why not just buy the enterprise plan?

You can. But according to sso.tax, keeping SSO for the enterprise plan can multiply the price by up to 10x or more, and often it is bought only to cut access when someone leaves. KeyHasp does that on the plan you already pay for.

Which tools does KeyHasp support today?

More than 30, including GitHub, AWS, Sentry, SendGrid, Claude, Cursor and CodeRabbit, and we add more every day.

Does KeyHasp need admin access to our tools?

No. Each connector uses a credential limited to user management. For GitHub that is a GitHub App with only the Members permission, with no access to your code.

Where does our data live?

In the KeyHasp cloud, on AWS. Each company is its own tenant, isolated in the database with row-level security. Tool credentials sit in AWS Secrets Manager, encrypted per company, never in KeyHasp's database.

Is KeyHasp SOC 2 compliant?

Our SOC 2 audit is in progress and the report has not been issued yet. The security model page describes the controls in place today.

What happens when a revocation fails?

KeyHasp retries within a bounded policy. If the step still fails, it becomes an open task with an owner, and the offboarding is not marked complete until that task is resolved.

What if the directory sync goes wrong?

A sync that would offboard more than three people or 20% of the company, whichever is larger, is aborted without changes. A misconfiguration cannot offboard everyone at once.

Which directory does KeyHasp use?

Google Workspace, Microsoft or Okta. Suspending or deleting a person there is what starts their offboarding.

How do people sign in to KeyHasp?

With their company account, through your identity provider. There are no KeyHasp passwords, and someone who leaves the directory loses their KeyHasp session on their next request.

How much does KeyHasp cost?

Pricing isn't published yet. Join the waitlist and we'll share it when early access opens.

Early access

Join the waitlist.

Email us your work address and company, and we'll write when your team can try KeyHasp.

Join the waitlist

Or write to hello@worldhackmakers.com

We use your email only to reply and to contact you about KeyHasp. Privacy notice