Your app’s sign-in emails, sent by Bloxks with nothing to set up: what it covers, what is included, how to check it.
When your app has accounts, it sends emails on its own: confirm the address at sign-up, reset a forgotten password, sign in with a link, confirm a new address, accept an invitation. With Mail, Bloxks sends them for you. There is nothing to connect.
What you get
- Emails leave from noreply@your-app.onbloxks.app, with your app’s name as the sender and its logo inside.
- The sending domain is authenticated with DKIM and a custom MAIL FROM. The recipient’s mail provider still decides whether to place a message in the inbox or spam.
- Text follows your app’s language (French or English), with one clear button.
- Security notices (password changed, email changed) are sent too.
How it turns on
As soon as your app has a sign-in screen and a linked Supabase project, Bloxks turns the emails on by itself. You will see it in the Backend tab, then Emails.
If your Supabase project already sends its emails through your own service (Resend, Brevo, a function of yours), Bloxks leaves it alone. The Emails tab offers a Switch to Mail button whenever you want.
What is included
| Plan | Sign-in emails per month |
|---|---|
| Pro | 3,000 |
| Empire | 20,000 |
Beyond that, each extra 1,000 emails uses 0.50 € of credits. The Emails tab shows how much of the month’s quota you have used.
To stop a bug or abuse quickly, each app can send up to 500 emails per hour with Pro and 3,000 with Empire. The Emails tab warns you at 80 %; past the limit, requests are refused and must be retried after the hourly allowance becomes available again.
Without an active subscription, sending is paused: your app’s users would not receive their confirmation or password emails until you subscribe again.
Check it works
The preview on your screen never sends emails. In Backend → Emails, send a test of each template to your Bloxks account address. Then install the app on your phone, sign up (or tap "forgot password") with an address you control, and check your inbox and spam folder. The Emails tab shows authentication emails and their status: sent means the sending service accepted the message; delivered means the recipient’s server accepted it, not necessarily that it reached the inbox.
Bounces and spam
Delivery, bounce and complaint statuses require the SES event pipeline. If the status stays at sent, do not assume the recipient received the message. Repeated bounces hurt everyone’s deliverability: only email people who requested these messages, and investigate failures before continuing.
Use your own service instead
Prefer your own sender (hello@yourdomain.com) through Resend or another SMTP? Open Backend, then Users, and connect it there: see Sign-in emails. Mail steps aside automatically. You can come back to it any time from the Emails tab.
Good to know
- The sender name and the sending subdomain (your-app.onbloxks.app) can be changed in the Emails tab.
- Emails your app sends on its own (welcome messages, receipts) are a different thing: see the Resend integration.
- Your users’ addresses are used only to deliver these emails; Bloxks keeps a short log (status, date) so you can see what happened.