Going to production
Every app group has two environments, development and production. They are apart in everything: their own users and sessions, their own login address and keys, their own clients, APIs, roles, login methods and settings. Nothing moves from one to the other by itself, so production is set up on its own, ideally once your app works against development.
| Development | Production | |
|---|---|---|
| Login address | https://your-app-dev.auth.dev.seek.services |
https://your-app.auth.dev.seek.services |
| In the dashboard | Amber dot | Green dot |
| API keys | sk_dev_… |
sk_live_… |
What development allows
Section titled “What development allows”Development is made for building on a laptop. These are allowed there and nowhere else:
- Any local address. A client takes any
http://localhost:<port>,http://127.0.0.1:<port>orhttp://[::1]:<port>as a redirect URI, a post-logout address and an origin without registering it. Names underlocalhost(such ashttp://shop.your-app.localhost:5173) work too, once registered for the client. Production takes registeredhttpsaddresses only, matched exactly. - A client to start with. Every new app gets a single-page app client in development,
{slug}-dev-spa, with no addresses to set. Production has no client until you create one. - Shared social logins. Google, Apple, GitHub, Discord, X and Microsoft work in development with SeekAuth’s own credentials. Production needs your own for each.
localhostas the passkey domain.- Free users of its own. Development environments are not counted towards your plan’s monthly active users. Each has a cap of its own instead: 100 a month on Free, 1,000 on paid plans; past it, its sign-ups pause. On Free a development environment takes 20 new accounts a day (production 100).
The checklist
Section titled “The checklist”Do these in the production environment (switch to it at the top of the dashboard).
- Clients. On Clients, create the clients your apps use, with their exact
httpsredirect URIs, post-logout redirect URIs and allowed origins. Setting addresses takes the admin role. A web or machine client’s secret is shown once. See Clients. - APIs and roles. Create your APIs, permissions and roles again on APIs and roles; give each client its default API. See Roles and permissions.
- Login methods. Enable them on Login methods. For each social provider, create an OAuth app at the provider with the callback address
https://your-app.auth.dev.seek.services/callback/{provider}and enter its credentials. See Social providers. - Passkeys. Set the passkey domain to your app’s own domain before enabling passkeys. See Passkeys.
- Security policy. Choose whether two-step login is required, whether sign-up is open, and the address rules and captcha switch on Security policy. See Two-step login, Sign-ups and access and Bot protection.
- Access, terms and branding. For each app: its access mode, whether it needs an email address, its terms URL (Sign-ups and access), and its look on Appearance (Branding).
- Lifetimes. Check the token and session lifetimes on Sessions fit your app. See Sessions and sign-out.
- Webhooks. Add production endpoints on Webhooks, each with its own secret. See Webhooks.
- API keys. Scripts and CI that change production need a production key (
sk_live_…) from API keys; a development key cannot reach production. See the management API. - A domain of your own (paid plans), before your users make passkeys and remember the address. See Custom domains.
- Your plan. Free pauses new sign-ups at 1,000 monthly active users and takes 100 new accounts a day, each behind a captcha. Check Usage and Plans and limits.
- Point your apps at production: the production issuer and client ids in your frontend, and the production issuer and audience in every backend that verifies tokens.
Users do not move
Section titled “Users do not move”The users of development and production are different people to SeekAuth, with different ids (sub). Accounts made while testing stay in development. There is no endpoint that creates or imports users: people sign up in production themselves.