Passkeys first. Every other way, too.
Identify
An email address — and a work address goes straight to its company's single sign-on.
Prove
A passkey, a password, a magic link, a social account or single sign-on.
Check
Account status, lockout, password spraying and risk — before any session exists.
Confirm
A second factor, when the organisation, the risk or the action asks for one.
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
For the people who still want one.
Hashed with Argon2id at the parameters OWASP recommends. Older bcrypt hashes still verify, and are upgraded to Argon2id at the next sign-in.
- Per-account lockout, which each organisation can tune
- Password-spraying protection that counts the accounts targeted
- Checked against known breaches by default
- Reset links go only to the account's own address
PlansOn every plan
One link, by email, and you're in.
A sign-in link sent by email and finished on the hosted sign-in page — for the people and the products where a password is one thing too many.
- Sent only to the account's own address
- Finished on the hosted sign-in page
PlansOn every plan
The account people already have.
Google, Microsoft, Apple, GitHub, Facebook, X and Discord — or an organisation's own OpenID Connect provider. GitHub, Facebook, X, Discord and Apple sign in through their own flows; the rest by OpenID Connect discovery.
- A second factor still applies where the organisation requires one
- An address the provider does not vouch for never takes over an account
PlansOn every plan
A work address finds its own way in.
Someone types a work address and Qeet ID finds their organisation's single sign-on from the domain alone, then sends them to it — SAML 2.0 or OpenID Connect.
- Only for domains the organisation has verified
- An organisation on single sign-on can switch the other ways off
PlansFrom Pro
02Second factors
Asked for when it matters. Answered in seconds.
When it is asked for
The organisation requires it
An organisation can require a second factor of every member.
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.
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.
- 10 minutesAccess tokenRenewed while the session lives
- 24 hoursIdle timeoutBy default — an organisation sets 15 minutes or more
- 30 daysMaximum ageBy default — an organisation sets 1 hour to 365 days
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.
| Setting | Default | Each 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 age | 30 days | Set 1 hour to 365 days |
| Idle timeout | 24 hours | Set 15 minutes, up to the maximum age |
| Remember this device | 30 days | Choose the days, or not allow it |
| Account lockout | Platform limits | Tune it within the platform's bounds |
| Self-registration | Off | Turn 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