Running In Production
There are two ways to run Seamless Auth in production. The managed offering hosts the auth instance for you. Self-hosting means you provision and operate the stack yourself.
Managed hosting
Section titled “Managed hosting”On the managed path, Seamless runs the auth instance for you. You create an application in the portal
at https://dashboard.seamlessauth.com, pick a plan, and Seamless
provisions a dedicated hosted instance. Its Auth Server URL is
https://<infra-id>.trials.seamlessauth.com on the Trial plan and
https://<infra-id>.seamlessauth.com on paid plans; copy the exact value from Credentials →
Auth API Configuration. You point the backend adapter at that URL with a portal-issued service
token.
On this path you do not provision Postgres, manage signing keys, or run the auth server. See the Managed Quickstart.
Self-hosting
Section titled “Self-hosting”The Production Checklist is the step-by-step guide for taking a self-hosted install to a public host. Start there.
The CLI (seamless-cli) scaffolds and inspects
projects; it does not deploy them. It has no deploy or destroy command, so provisioning and
operating the servers is up to you. See the CLI command reference for
what it does ship.
What the CLI prepares
Section titled “What the CLI prepares”seamless init --local generates a local project with:
- a web starter and a backend starter (or a full-stack starter)
- the Seamless Auth API in Docker or local-source mode
- the admin dashboard, served by your backend at
/console, as a separate container, or not at all - Docker Compose wiring
- local secrets and service URLs
seamless.config.json
That is a working local stack in development mode, not a production configuration. Its compose file returns sign-in codes in responses and signs tokens with a key generated on disk, so do not deploy it as it is. The Production Checklist says what to change.
What self-hosted operators own
Section titled “What self-hosted operators own”If you self-host, you own:
- hosting the auth API, your application backend, your web app, and the admin console if you use it
- provisioning Postgres
- setting stable production secrets
- configuring JWKS signing keys
- configuring HTTPS, CORS, origins, cookie domain, and proxy headers
- managing OAuth provider callback URLs and provider secrets
- monitoring, logging, alerting, backup, and restore testing
- upgrades and rollback
Use Environment Variables, System Config Reference, and Cookie, Session, And Token Reference alongside the checklist.
The managed offering handles these for you.
Next Step
Section titled “Next Step”Continue to the Production Checklist.