Skip to content
Qeet ID
Read the docs
In development

Their identity provider. Signed in to your app.

SAML 2.0 and OpenID Connect for every organisation you sell to — set up by their own IT team through a link you send, tested before anyone signs in, and kept current when their certificates change.

Read the docsTalk to us

  1. Discover

    A work address finds its organisation's connection from the domain alone.

  2. Redirect

    To the organisation's own identity provider, by SAML 2.0 or OpenID Connect.

  3. Verify

    The signed answer is checked, with three minutes allowed for clock drift.

  4. Provision

    An account is made only where the domain allows, and kept in step after.

  5. Session

    Signed in, under the organisation's own sign-in rules.

01Connections

SAML or OpenID Connect. Either way, both ways.

Their identity provider, trusted properly.

Qeet ID is the service provider for each organisation's own identity provider. A connection is set up from the provider's metadata and keeps itself current, so a certificate change on their side does not break sign-in on yours.

SAML connections in the docs
  • Set up from the IdP's metadata, and kept current
  • Survives the IdP's certificate rollover
  • Accepts assertions the IdP encrypts

PlansFrom Pro

02Admin portal

Their IT team sets it up. You send a link.

How it goes

  1. You send a link

    Time-limited and scoped to what it may set up. Their IT team needs no Qeet ID account.

  2. They see what their IdP needs

    The addresses and identifiers to enter in their identity provider.

  3. They prove the domain

    A DNS record verifies the organisation's domain.

  4. They test it

    A test sign-in that signs nobody in, and says what went wrong if it fails.

Safe while it is built

  • Draft first

    A connection starts as a named draft, and a draft cannot sign anyone in.

  • Verified domains only

    Single sign-on applies only to domains the organisation has verified.

  • Accounts where allowed

    A sign-in creates an account only where the domain allows it.

  • Groups in step

    The identity provider's groups map onto the organisation's own.

03Guard rails

One organisation's sign-in stays in that organisation.

  • Kept inside its tenant

    A shared guard keeps every federated sign-in inside the organisation it belongs to.

  • No quiet takeovers

    Single sign-on never adopts an owner or admin account it is not linked to.

  • Bound to the browser

    A SAML sign-in completes only in the browser that started it.

  • Sign-out reaches the apps

    Signing out ends the app grants the session started, and the applications are told.

04On each plan

Single sign-on from Pro. No charge per connection.

  • Free

    ₹0/month

    10,000 users

  • Starter

    ₹2,400/month

    25,000 users

  • Pro

    ₹8,000/month

    100,000 users

  • Enterprise

    Custom

    Custom scale

  • OpenID Connect provider: Free: included; Starter: included; Pro: included; Enterprise: included

  • Domain verification: not on Free; Starter: included; Pro: included; Enterprise: included

  • Single sign-on: not on Free; not on Starter; Pro: included; Enterprise: included

  • SAML 2.0: not on Free; not on Starter; Pro: included; Enterprise: included

  • Admin portal: not on Free; not on Starter; Pro: Self-serve; Enterprise: included

Full pricing and calculator

Set up your first connection.

Read the docsTalk to us