[managed.<name>.users] turns on sign-in for the people who use your app: email and password, plus Google, GitHub, Microsoft or Vercel. floo runs the sign-in service (Better Auth) at /api/auth on every host of your app, including custom domains. Users, sessions and accounts live in your app’s own Postgres, in the floo_auth schema, next to your tables. Your app renders its own pages.
User accounts or team access
They share no config key, header or session. A User accounts app keeps
access_mode = "public".
Turn it on
1. Declare it on a managed Postgres
[managed.default.users] table means email and password with open sign-up from any address. One Postgres per app can hold User accounts.
2. Deploy
The next dev deploy sets up sign-in for dev and prod. After that,/api/auth on every host of an environment answers sign-in requests, and settings follow each environment’s deploys, so a prod change ships with a release. Each service gets:
Dev and prod have separate users: a dev user cannot sign in to prod. Preview environments sign in against dev’s users.
3. Add sign-in to your app
Use the standardbetter-auth client. Sign-in is on your app’s own origin, so the client needs no URL and cookies are first-party:
await auth.signIn.social({ provider: "google" }).
On the server, check the session with the request’s cookie:
GET /api/auth/token, and your backend checks it against FLOO_AUTH_JWKS_URL (EdDSA).
Session checks are answered from a signed cookie for 5 minutes, so page loads are fast and never wait on your database. Signing out takes effect at once in that browser. A session ended elsewhere (a password reset, or revoking other sessions) can keep working in another browser for up to 5 minutes.
Settings
signup = "closed"stops new sign-ups by every method; existing users still sign in.allowed_email_domainsrefuses sign-up from any other address, whatever the method, before an account exists./api/authbelongs to floo while User accounts is on: a[[routes]]entry at that path is replaced.
<your app's name> <noreply@auth.getfloo.app>. Codes are 6 digits, expire after 10 minutes, and allow 5 tries.
Testing
In dev, any address at@test.getfloo.app signs up and verifies with the code 000000, and no email is sent. Tests and coding agents can create and sign in users without a mailbox. Prod refuses these addresses. If you set allowed_email_domains, it applies to test addresses too: add "test.getfloo.app" to the list to use them. Leave it out when real users sign in on your dev environment.
On your machine
floo dev (CLI v2026.11.10 or later) prints a proxied URL next to each service. Open your app on that URL and /api/auth goes to your dev environment’s sign-in, so sign-up, sign-in and sessions work locally against dev’s users, with the session cookie on localhost. Every other path goes to your local service. Use a @test.getfloo.app address to skip the mailbox. Social sign-in returns to the dev host, so test it there.
Social sign-in
Each provider needs your own OAuth app in each environment, so the consent screen shows your app’s name:- Add the provider to
methodsand deploy. Until step 3 that method stays off. - Create an OAuth app with the provider. Set its callback URL to
https://<environment host>/api/auth/callback/<provider>, for examplehttps://shop.getfloo.app/api/auth/callback/google. Add one for each custom domain users sign in on. - Give floo the client id and secret for that environment:
USER_ACCOUNTS_METHOD_NOT_DECLARED unless the environment’s live deploy lists the provider in methods.
Your users’ data
Users are rows in your database. Query them like any table:floo_auth schema, through its own Postgres role. Removing the users table stops sign-in at /api/auth on the next deploy; the floo_auth data stays in your database.
Billing
There is no charge per user. Sign-in queries run on your Postgres and bill as Postgres compute.Limits
- Ten wrong passwords for one account within 15 minutes pause password sign-in for that account until the 15 minutes pass. Sign-in answers 429 with the message “Too many wrong passwords for this account. Try again in 15 minutes, or reset your password.” Resetting the password by emailed code ends the pause, and a correct sign-in before the tenth wrong try clears the count.
- One address gets 20 codes and wrong code guesses an hour per app host, counted together across verification and password reset. Past that, the request answers 429 with “Too many codes for this address. Try again in an hour.”
- Apple sign-in, passkeys and magic links are not available.
- Social sign-in on a preview host needs that host’s callback URL in your OAuth app.