User accounts
Add end-user sign-up and login to your app, backed by its own auth store.
Add sign-up and login for your app's end users. The auth service runs alongside your app and keeps its users in the app's own database. User accounts are available on every plan, including Starter.
Wire, then enable
Two steps, one deploy:
- Wire. On the app's Auth tab, copy the agent setup prompt and paste it into your coding agent. It adds sign-up, login and the current-user check to your app. A connected agent can pull the same prompt itself with the
generate_feature_prompttool, before auth is on. - Enable and deploy. Once your agent has shipped the changes, turn on End-user authentication on the same tab and deploy once. That deploy brings the new code and the auth service up together.
- Your app needs a database. If it doesn't have one, enabling auth turns one on for it.
- Until that deploy, the auth endpoints answer 404, and the app's page lists "User accounts turned on" among the changes waiting to go live. That is expected.
Turn off and on
You can turn authentication off at any time from the dashboard, for example to switch to your own login (a connected agent can turn it on, never off). Your users are not deleted: they stay in the auth schema of your app's database until the app itself is deleted. A version of the app that is already running keeps signing users in until your next deploy, which removes the auth service. Turn authentication back on later and the same accounts work again. The general rule for every feature is in the overview.
Configure
There is little to set up beyond enabling. You manage your end users from the Users table: search by email, filter by active / banned / unconfirmed, and ban, unban, reset a password, confirm an email, or delete a user.
How your app talks to it
Your app calls the auth service over HTTP to sign users up, log them in, and read the current user. You don't write this by hand: the wiring prompt above tells your agent the exact endpoints, and it never needs a key or a password of yours.
Your database
With user accounts on, an auth schema appears in your app's database. The platform owns that schema; your app can read from it and keeps its own tables separately. See what runs here for how your app's database is laid out.