Managed Quickstart
Sign up, create an application, get a service token, and connect a real app to your hosted auth instance. See Managed Quickstart.
Seamless Auth is available two ways. Both use the same SDKs (@seamless-auth/react,
@seamless-auth/express) and the same passwordless auth model. The difference is who runs the auth
server and its database.
| Path | Who runs the auth infrastructure | Start here |
|---|---|---|
| Managed | Seamless hosts a per-application auth instance for you | Managed Quickstart |
| Self-hosted | You run the auth API, Postgres, and cookies in your stack | Self-Hosted Quickstart |
On the managed path you sign up at the Seamless Auth portal, create an application, and pick a plan. Seamless provisions a dedicated auth instance for that application and gives you its URL and a service token. You point the SDKs at that instance and ship.
Choose managed when you want:
The portal lives at https://dashboard.seamlessauth.com. Its own login is passwordless, built on Seamless Auth.
Managed Quickstart
Sign up, create an application, get a service token, and connect a real app to your hosted auth instance. See Managed Quickstart.
On the self-hosted path you run the auth stack yourself. seamless-cli scaffolds a full local
project (React web app, Express API, the auth server in Docker or local-source mode, optional admin
dashboard, and Docker Compose wiring) so you can develop against a production-shaped stack on your
own machine.
Choose self-hosted when you want:
Self-Hosted Quickstart
Scaffold a local stack with the CLI, start it with Docker, and register as the first admin. See Self-Hosted Quickstart.
Both paths work for an existing project. seamless add, run at the root of your repository, finds
your backend and web app, connects them to a local auth server (--local) or a managed application
(--app <id>), writes the environment values, installs the packages, and prints the code to add.
See Add Seamless Auth To An Existing App.
The only integration values that differ between the two paths are the auth server URL and the source of the service token.
| Value | Managed | Self-hosted |
|---|---|---|
React apiHost |
Your backend API, which runs the adapter | Your backend API, usually http://localhost:3000 |
Express authServerUrl |
Your application’s Auth Server URL from the portal | The auth API, usually http://localhost:5312 |
Service token (serviceSecret) |
Generated in the portal, shown once | Generated locally by the CLI into your project files |
On both paths the React SDK points at your own backend, never at the auth server: the adapter on your backend is what sets the browser’s session cookies. Everything else (the provider component, hooks, middleware, and route protection) is the same.