Skip to content
Qeet Group

One identity. Every platform.

Qeet ID

The auth platform engineers wish they'd had. Passkeys, social and SAML SSO, MFA, multi-tenant RBAC, machine-to-machine, SCIM, signed webhooks, and OpenID Connect — on a single, hash-chained, audit-ready identity graph.

Sector

Identity & Access

Stage

Generally available

Founded

2026

Overview

Qeet ID is the first company inside Qeet Group. It started from a question every engineering team eventually asks: why is authentication this expensive, this complicated, and this divided between "simple developer tools" and "real enterprise platforms"? Qeet ID was built to close that gap — developer simplicity on the surface, enterprise depth underneath, at a price that does not force teams to choose between the two.

Everything sits on a single, multi-tenant identity graph, so policy decisions stay coherent across products and tenants. Every record is scoped by tenant; sessions are stateful and revocable; the audit trail is hash-chained end to end.

Available today

The capabilities running in production now:

  • Authentication — email and password with stateful sessions and refresh-token rotation; passwordless magic links; email and phone one-time codes.
  • Passkeys — WebAuthn passkeys for phishing-resistant, passwordless sign-in.
  • Social sign-in — Google, GitHub, Microsoft, and Apple over OAuth 2.0 / OpenID Connect.
  • Multi-factor — TOTP authenticator apps with single-use recovery codes.
  • Authorization — multi-tenant role-based access control with a permission-check API, so every product and tenant resolves policy the same way.
  • Machine-to-machine — API keys and service accounts over the OAuth 2.0 client-credentials grant.
  • OAuth & OpenID Connect — the Authorization Code flow with PKCE and ID-token issuance, alongside discovery, JWKS, dynamic client registration, and a userinfo endpoint, so standards-based clients integrate without bespoke glue.
  • Enterprise SSO — SAML 2.0 as both service provider and identity provider.
  • Directory provisioning — SCIM 2.0 for automated user lifecycle driven from your IdP.
  • Events — HMAC-signed webhooks with persisted delivery, exponential-backoff retries, and a dead-letter queue, fed by a transactional outbox.
  • Audit — a hash-chained, append-only audit log with an independent chain verifier. Tamper is detectable, not assumed away.

On the roadmap

The platform is built so each of these slots into the same identity graph as it ships:

  • Asymmetric RS256 / ES256 token signing with scheduled key rotation
  • First-party SDKs — TypeScript, Go, Python, and more — over the standards-based API
  • Data-subject export to complement the in-platform erasure that ships today
  • Managed email and SMS delivery, and metered billing
  • SOC 2 attestation and a public trust center

Who they serve

Developers building their first product. Startups adding their first compliance certifications. Enterprises consolidating identity infrastructure across business units. The point is the same product feels right at every stage — no migration when scale arrives.

Security and compliance

Tenant isolation, revocable stateful sessions, and a hash-chained audit log are part of the platform, not an add-on. Qeet ID is built GDPR-aligned, with data-subject erasure handled inside the platform and machine-readable export on the roadmap. SOC 2 and a public trust center are on the roadmap as the product hardens toward 1.0.

Status

Generally available for the capabilities above, with engineering teams running them in production. New protocols and integrations ship continuously; the changelog lives at id.qeet.in. The free tier covers 5,000 monthly active users with no credit card required.

The product, documentation, and pricing live at id.qeet.in.

Visit id.qeet.in