Skip to content
In development

Passkeys first. Every other way, too.

Passkeys, passwords, magic links, social accounts and company single sign-on — with second factors, risk checks and sessions each organisation sets. Every decision is made on the server; the sign-in pages only show it.

  1. Identify

    An email address — and a work address goes straight to its company's single sign-on.

  2. Prove

    A passkey, a password, a magic link, a social account or single sign-on.

  3. Check

    Account status, lockout, password spraying and risk — before any session exists.

  4. Confirm

    A second factor, when the organisation, the risk or the action asks for one.

  5. Session

    Tokens signed with ES256: ten minutes of access at a time, renewed, and revocable.

01Ways in

Five ways in. Each one decided on the server.

The strongest way in is also the quickest.

WebAuthn passkeys, from the first sign-up: someone can create an account with a passkey and never set a password. A passkey counts as multi-factor on its own, so nobody who uses one is asked for a code.

  • Sign up with a passkey — no password needed
  • A passkey neither requires nor is required by a password
  • An admin can see and remove a member's passkeys

PlansOn every plan

02Second factors

Asked for when it matters. Answered in seconds.

When it is asked for

  1. The organisation requires it

    An organisation can require a second factor of every member.

  2. The sign-in looks risky

    Every sign-in is scored for risk; a risky one from someone with no factor gets a code by email.

  3. The action is sensitive

    Changing how someone signs in needs a recent sign-in — and they are emailed when it changes.

How people answer

  • Authenticator apps

    Time-based one-time codes (TOTP, RFC 6238).

  • Email and SMS codes

    A one-time code that is good only for what it was sent for.

  • Push approval

    On a phone linked with a pairing code — and the number on the screen must match.

  • Recovery codes

    Ten of them, each used once, shown only once.

  • Push prompts are capped, so nobody can be worn down by a flood of them.
  • A trusted device skips the second factor for the days the organisation chooses — 30 by default.

03Sessions

Every session has an end. You decide when.

  1. 10 minutesAccess tokenRenewed while the session lives
  2. 24 hoursIdle timeoutBy default — an organisation sets 15 minutes or more
  3. 30 daysMaximum ageBy default — an organisation sets 1 hour to 365 days
Lifetimes on a scale from one minute to one year.

What ends one sooner

  • Someone revokes it

    A person or an admin — one session, or every one.

  • The password changes

    Every other session of that person ends.

  • A refresh token is reused

    The reuse is detected and the session revoked.

  • Someone is offboarded

    A SCIM suspension ends every sign-in they have.

Your applications hear about each one, as a signed session.revoked webhook.

04Per organisation

Your customers' admins set the rules.

Every organisation in Qeet ID is its own tenant. Its admins choose how their people sign in, within limits the platform holds.

Your customers' admins set the rules.
SettingDefaultEach organisation can
Sign-in methods—Choose which are offered; on single sign-on, switch the others off
Second factor—Require one of every member
Session maximum age30 daysSet 1 hour to 365 days
Idle timeout24 hoursSet 15 minutes, up to the maximum age
Remember this device30 daysChoose the days, or not allow it
Account lockoutPlatform limitsTune it within the platform's bounds
Self-registrationOffTurn it on
Branding and email—Brand the hosted pages and write its own emails, sent in each recipient's language

Not in 1.0: custom sign-in domains are recorded, but not yet served.

05On each plan

Passkeys on every plan. A second factor on every plan, too.

  • Free

    ₹0/month

    10,000 users

  • Starter

    ₹2,400/month

    25,000 users

  • Pro

    ₹8,000/month

    100,000 users

  • Enterprise

    Custom

    Custom scale

  • Passkeys: Free: included; Starter: included; Pro: included; Enterprise: included

  • Email and password: Free: included; Starter: included; Pro: included; Enterprise: included

  • Magic links: Free: included; Starter: included; Pro: included; Enterprise: included

  • Social accounts: Free: included; Starter: included; Pro: included; Enterprise: included

  • Account recovery: Free: included; Starter: included; Pro: included; Enterprise: included

  • Multi-factor: Free: TOTP · email OTP; Starter: included; Pro: included; Enterprise: included

  • SMS and push codes: not on Free; Starter: included; Pro: included; Enterprise: included

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

Read how it works, end to end.