Accounts without building accounts
Every app needs sign-up, sign-in, password resets and email confirmation, and each one is easy to get subtly wrong. Rimbra Auth does all of it for you.
It works for apps hosted on Rimbra and anywhere else. Your frontend uses a small browser client; your backend checks each request’s token on its own, without calling Rimbra.
Three steps
- 1
Create an auth project in Hosting → Auth with your app’s name and site URL.
- 2
Import the client in your frontend and call signUp, signIn, sendLink or signInWith("google").
- 3
On your server, check the Bearer token against the project’s JWKS. The user’s ID is the token’s subject.
Search, add, suspend and sign out users in the dashboard, or from your server with the admin API.
Limits by plan
| Plan | Auth projects | Users |
|---|---|---|
| Free | 2 | 10,000 |
| Launch | 5 | 50,000 |
| Pro | 20 | 100,000 |
| Scale | 100 | 500,000 |
Safe by default
- Passwords are stored as bcrypt hashes. Sign-in attempts and emails are rate limited.
- Refresh tokens change every time they are used, and suspending a user signs them out everywhere.
- Email links and codes work once. Five wrong codes and a new email is needed.
- Redirects only go to your site, addresses you list, or localhost.
Questions
Does my app have to run on Rimbra?
No. Any frontend can use the browser client, and any backend can check the tokens.
Can I keep my own user table?
Yes. Use the token’s subject (the user’s ID) as the key in your own database, and keep app-specific fields there or in the user’s data.
Who sends the emails?
Rimbra sends them under your app’s name from your own address, like auth@yourdomain.com, once the domain is verified in Emails → Domains. Never from a Rimbra address.