Skip to content

What Is Seamless Auth?

Seamless Auth is open source passwordless auth (passkeys, magic links, OTP) that you self-host or run as a managed service. The server, SDKs, and CLI are licensed Apache-2.0.

Scaffold a complete local stack (web app, API, auth server, and admin console) with no prompts:

Terminal window
npx seamless-cli init my-app --local --yes --email=you@example.com

Then cd my-app && docker compose up, and register in the browser with the email you passed, which becomes the first admin. The Self-Hosted Quickstart walks through each step.

It combines a hosted or self-hostable auth server, official SDKs, a CLI for scaffolding a working stack, a developer portal for the managed offering, and an operator dashboard for managing users, sessions, security, and system configuration.

The goal is to give you modern authentication with the same SDKs and session model whether Seamless hosts the auth instance for you or you keep the auth engine and data inside your own stack.


Seamless Auth request topologyA browser running a React app with @seamless-auth/react sends signed httpOnly cookies to your backend. A native app running @seamless-auth/react-native keeps its tokens in the platform keystore and sends them to the same backend in an Authorization Bearer header with the x-seamless-auth-transport bearer header. Your backend runs @seamless-auth/express, fastify or nextjs, and forwards each request to seamless-auth-api with a bearer token and a service token. The auth API owns the session, stores it in Postgres, and publishes a JWKS the backend uses to verify the tokens the API signs.BrowserReact app@seamless-auth/reactholds no tokensNative app@seamless-auth/react-nativetokens in theplatform keystoreYour backend@seamless-auth/expressfastify, nextjs/auth adapter routesrequireAuthkeeps browser tokensin signed cookiesseamless-auth-apiowns the sessionissues androtates tokens/.well-known/jwks.jsonPostgressigned httpOnlycookiesBearer tokens+ transportheaderBearer token+ service tokenJWKS verifiesAPI-signed tokens
Both clients reach the auth API through your backend. The auth API owns the session; the browser and native clients differ only in where the tokens are kept.

Every client talks to your backend, never straight to the auth API. Your backend mounts the /auth adapter routes from @seamless-auth/express, @seamless-auth/fastify, or @seamless-auth/nextjs and forwards each call to seamless-auth-api with the user’s token in Authorization: Bearer and a service token alongside it.

  • The auth API owns the session. It creates, rotates, and revokes sessions, stores them in Postgres, signs the access tokens, and publishes the keys at /.well-known/jwks.json.
  • Browser (cookie transport). @seamless-auth/react, @seamless-auth/angular, @seamless-auth/vue, and @seamless-auth/svelte never see a token. The adapter keeps the auth API’s tokens inside signed httpOnly cookies on your domain and unwraps them when it forwards a request.
  • Native app (bearer transport). @seamless-auth/react-native has no cookie jar, so it keeps the tokens in the platform keystore and sends them to the same adapter routes in Authorization: Bearer, with x-seamless-auth-transport: bearer. The adapter writes no cookies for these requests.
  • Your backend verifies, the auth API decides. requireAuth checks the signed cookie, or a bearer token against the auth API’s JWKS, so a protected route does not need a round trip. Your own code still enforces roles and authorization.

Cookie, Session, And Token Reference and Bearer Transport For Native Clients have the exact cookie names, token types, and headers.


  • Authentication is based on cryptographic verification, not shared secrets.
  • Supports passkeys, magic links, email/phone OTP, TOTP MFA, and optional OAuth login.

  • The auth engine runs as its own service inside your stack.
  • SDKs are thin integration layers, not hidden platforms.
  • Frontend auth flows stay inside your application.
  • The admin dashboard is a separate app, not a magical control plane.

  • The auth API issues and tracks sessions; your backend validates them on every request.
  • Browsers carry the session in secure, HTTP-only cookies; native apps carry it as bearer tokens.
  • Defense-in-depth approach to authentication.
  • Sessions are tracked per device and per browser.

  • Roles and access control are defined and enforced in your own application code.
  • No hidden authorization layers or assumptions.

  • The same core model works locally, in staging, and in production.
  • Local development is designed to stay close to deployment reality.
  • The CLI can scaffold a production-shaped local stack quickly.

Seamless Auth is made up of a few focused projects.

Piece Role
Seamless Auth portal Managed offering: create apps, pick plans, issue service tokens
seamless-cli Scaffolds a full local stack for self-hosting
seamless-auth-api Runs the passwordless auth engine
@seamless-auth/core Framework-agnostic server auth primitives
@seamless-auth/express Official Express backend integration
@seamless-auth/fastify Official Fastify backend integration
@seamless-auth/nextjs Official Next.js App Router integration
@seamless-auth/react React auth provider and built-in auth routes
@seamless-auth/angular Angular service, route guards, and built-in auth routes
@seamless-auth/vue Vue plugin, composable, router guards, and built-in auth routes
@seamless-auth/svelte Svelte session, SvelteKit load guards, and built-in auth screens
@seamless-auth/react-native React Native and Expo SDK over bearer transport
@seamless-auth/client Framework-free client shared by the React, Angular, and native SDKs
seamless-auth-admin-dashboard Operator UI for users, sessions, events, security, and config
@seamless-auth/types Shared domain and API types

If you want the fuller package map, continue to Ecosystem Overview.


Seamless Auth treats authentication as infrastructure:

CLI -> Local stack
SDKs -> App integration
Auth API -> Passwordless auth engine
Admin Dashboard -> Operator workflows

By the end of this guide, you will have:

  • A working local stack
  • Passwordless authentication
  • Session management with device-level control
  • A clearer mental model of the ecosystem
  • Enough context to choose the right package for your next step
  • A path to customize auth UI and protect app routes when you leave the starter

When Seamless Auth Is Not The Right Choice

Section titled “When Seamless Auth Is Not The Right Choice”

Seamless Auth makes deliberate tradeoffs. It is likely the wrong fit if any of these are hard requirements for you:

  • You need password login. There is no password flow. Users sign in with passkeys, magic links, email or phone OTP, or OAuth, with TOTP as a second factor. seamless migrate imports identities, not password hashes, so imported users sign in passwordlessly from their first login (see Migrate Users).
  • You need SAML. The auth API signs users in to your application and can use OAuth and OIDC providers as a login source, but it does not speak SAML, as a service provider or as an identity provider. To be an identity provider for other apps over OpenID Connect, use the OpenID Provider (since v0.21). It is a separate service in front of the API, off by default, new, and not OpenID certified yet.
  • Your backend has no official adapter. Official server adapters exist for Node.js 22 or later (core, express, fastify, nextjs), Python (FastAPI and Django, pip install "seamless-auth[fastapi]"), Go (net/http, so chi, Echo and Gin), and Rust (Axum), all held to the same conformance suite. A backend in another language has to implement the adapter contract against the auth API itself.
  • Your frontend has no backend. Both the browser and the native SDK call /auth adapter routes on your own server, which hold the service token and, for browsers, the cookies. A static site with no server of its own needs one added (a Next.js app can be its own).
  • Your frontend is not React, Angular, Vue, Svelte, or React Native. @seamless-auth/client is framework-free, but there are no shipped bindings for other frameworks yet.
  • You want to self-host without operating anything. Self-hosting means you run the auth API, Postgres, signing keys, migrations, and backups, and the CLI does not deploy them for you. The managed path exists for exactly this.
  • You need a 1.0 stability guarantee. Every package is still 0.x. Minor releases can change behavior, so pin versions and read the release notes; see the Compatibility Matrix.

The auth server (seamless-auth-api), the server adapters (@seamless-auth/core, express, fastify, nextjs), the frontend and native SDKs (@seamless-auth/react, angular, vue, svelte, react-native, client), @seamless-auth/types, the admin dashboard, and the CLI (seamless-cli) are all licensed under the Apache License 2.0 (Apache-2.0).

They were previously licensed AGPL-3.0 and were relicensed to Apache-2.0 in October 2026.

Does using Seamless Auth put copyleft obligations on my application?

Section titled “Does using Seamless Auth put copyleft obligations on my application?”

No. Apache-2.0 is a permissive license. Using, self-hosting, or modifying the server, SDKs, or CLI places no copyleft obligations on your application code, and you do not have to publish your source. If you redistribute Seamless Auth itself, keep its license and notices, as Apache-2.0 requires.


→ Continue to Managed or Self-Hosted