Roadmap

What we are building next

Seamless Auth plans by version. Each version has a public epic on GitHub that lists every piece of work in it and tracks what is done.

Next

v1.0

Stable platform

A platform you can build on for years: a frozen contract, a published upgrade policy, and nothing you cannot take with you.

  • A frozen contract and an upgrade and version skew policy
  • Configuration as code
  • Full data export
  • An independent security review you can cite
  • Rate limits shared across instances
  • OpenID certification for the OpenID Provider

Shipped · 2026-11-08

v0.23

Roles, permissions and hooks

Apps can authorize on what Seamless Auth issues, and extend it without forking.

  • Permissions and organization roles in tokens
  • Guards in every adapter
  • Custom claims, signed webhooks and login hooks
  • SIEM streaming over OTLP (syslog comes in v0.23.1, not yet released)
  • Native and CLI sign-in through the OpenID Provider

Shipped · 2026-11-02

v0.22

OpenID Provider session binding

The API owns which sessions an OpenID Provider sign-in was made on.

  • The provider binds a session to a client, and the API answers lookups, signs tokens and accepts revokes only for bound sessions
  • Provider service contract v3, so seamless-auth-oidc-provider v0.3.0 is upgraded with the API
  • Device-flow tokens no longer carry amr or auth_time

Shipped · 2026-11-01

v0.21

OpenID Provider

Any app that speaks OpenID Connect can sign users in through Seamless Auth, with no Seamless SDK required.

  • Authorization code with PKCE, refresh rotation, client credentials and device sign-in
  • Applications and resources managed from the API, console and CLI
  • Hosted login, consent and device pages with no-build branding
  • OAuth 2.1 and RFC 9700 defaults, with the OpenID conformance suite in CI
  • Verify-only resource servers in the Express, Fastify, Go, Python and Rust adapters

Shipped · 2026-10-29

v0.20

Never locked out, and hardened

Users who lose every passkey have a way back in, and admins cannot be locked out by their own sign-in policy.

  • Recovery codes and restricted recovery sessions
  • Self-service account recovery with a delay and owner notices
  • Break-glass admins and a staged, versioned sign-in policy
  • A fresh step-up on every admin write

Shipped · 2026-10-18

v0.19

The right choice today

Make what Seamless Auth already does trustworthy and findable, and fix what strangers trip on.

  • Security fixes and published advisories
  • OAuth state binding
  • Admin continuity and a first admin without reading logs
  • Documentation that matches what ships