KeyHasp

How it works

Your directory decides. KeyHasp carries it out.

KeyHasp sits between your identity provider and your tools. When someone joins, changes or leaves, it makes each tool match, and checks that it did.

Directory

Your identity provider

  • Google Workspace
  • Microsoft
  • Okta

KeyHasp

KeyHasp cloud, on AWS

  • Lambda
  • RDS PostgreSQL
  • Secrets Manager
  • SQS

Tools

30+ connectors

  • GitHub
  • AWS
  • Sentry
  • SendGrid
  • and more
Your identity provider sends changes to KeyHasp, a cloud service on AWS isolated per company, which applies them to each tool through its user-management API.

Offboarding

When someone leaves.

  • Triggered by the directory

    Suspending or deleting a person in your identity provider starts the offboarding. A full sync every 15 minutes catches anything an event missed.

  • Revokes what really exists

    KeyHasp reads each tool first and removes the accounts that actually exist, including ones it never created. Each tool runs on its own.

  • Verified, recorded, owned

    Each revocation is confirmed by reading the tool again. The report keeps the evidence, and anything still failing becomes a task with an owner.

Onboarding

When someone joins.

  • Role templates

    A hire gets the accounts of their role template, with least privilege.

  • Production stays out

    Production access is never part of a template. It is requested, approved and expires.

Day to day

Everything in between.

  • Who has what

    A matrix of what each tool actually reports, with unlinked accounts in plain sight.

  • Requests and temporary access

    Access is requested and approved by someone other than the requester, and expires on its own. Production access always has an end date.

  • Orphan accounts

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

Getting started

Three steps to start.

  • Sign in with your company account to create your KeyHasp workspace.
  • Connect your identity provider.
  • Connect your tools. For GitHub, that means installing the KeyHasp App on your organization.
Read the security model

Offboarding you can trust, without the SSO tax.