Skip to content

Bot protection

Everything on this page stands in the way of an account being made, never of a login: someone who has an account always logs in. The limits on guessing codes and passwords are on Rate limits.

Free Pro and Scale
Captcha before a new account Always When the environment asks for it
Throwaway addresses Refused from the start (can be allowed) Allowed (can be refused)
New accounts a day 100 in production, 20 in development No limit
Sign-ups pause at 1,000 monthly active users 15,000 on Pro, 150,000 on Scale

The captcha is Cloudflare Turnstile. The login UI shows it when the server asks for one, and one solved anywhere in a login attempt counts for the whole attempt. If the platform has no captcha configured, nothing is asked.

A solved captcha counts only where Cloudflare says it was solved on a page the request could have come from: the environment’s login page, or the page of your app that sent it (an allowed origin of its client). One solved on any other site is asked for again.

A captcha is asked for:

  • At every sign-up through the sign-up form (the signup step), on every plan.
  • After failed attempts. Once there were 3 failures in 10 minutes from the same address or on the same account, or 10 attempts on the account, every step that tries a secret (a password, a code, a recovery code, a wallet or passkey signature) needs one.
  • Past the shared code budget. Once 3 codes were asked for an address in 15 minutes, the next ones need a captcha, unless the device has held a session of the account before.
  • Before every new account, where the plan (Free) or the environment asks for it: when an email code has proven an address nobody has, the captcha is asked before the code is used, so the same code goes through with it; and when a wallet nobody has used signs in.

Sign-ups through a social or custom provider come back by a redirect, where no captcha can be shown, and are never asked.

On Pro and Scale an environment can ask for a captcha before every new account, as Free always does. Turn the environment’s own captcha switch on in its Security policy, or:

PATCH /v1/environments/{environment_id}
Content-Type: application/json
{ "captcha_every_signup": true }

The environment’s answer says what it asks for itself (captcha_every_signup), what its plan asks for (plan.captcha_every_signup, which the dashboard shows switched on and locked), and whether the platform has a captcha at all (captcha_enabled).

Three switches of the Security policy decide which addresses can make an account or be added to one. Each is a field of PATCH /v1/environments/:id (admin role). They apply to new addresses only: users who already have such an address keep it and keep logging in.

Switch Off by default, except What it does
refuse_email_tags An address with a +tag in its local part cannot sign up or be added.
refuse_disposable_emails On from the start in environments made on Free An address at a throwaway email service cannot sign up or be added.
one_account_per_gmail_inbox An address that reaches an existing user’s Gmail inbox is that user’s.

The messages users see:

  • Tagged address: “Addresses with a +tag, like [email protected], cannot be used here. Enter the address without the tag.”
  • Throwaway address: “Addresses at throwaway email services cannot be used here. Enter an address you keep.”

Where the refusal applies:

  • At a sign-up with a password, and when an address is added (the add_email step, or a change of address in account settings), it is refused on the address alone.
  • A login code to a new address is refused only after the code has proven the inbox, so the refusal says nothing about whether the address has an account.
  • A provider’s address is refused the same way, and the provider’s account cannot be made.

The throwaway domains are the public blocklist of the disposable-email-domains project, built into SeekAuth. An address is throwaway when its domain, or a domain it is under, is on the list.

Gmail delivers [email protected], [email protected] and [email protected] to the same inbox. With one_account_per_gmail_inbox on, every such variant belongs to the user who has the inbox (the oldest account, if two already share one):

  • a login code sent to a variant logs in to that user’s account, and the variant is not stored;
  • a sign-up with a password or an added address that is a variant gets the usual answer and no code, and the owner of the inbox is emailed;
  • a provider’s address that is a variant counts as an existing account.

On Free, an environment makes at most 100 new accounts a UTC day in production, and 20 in development. Past that, sign-up is closed until the next day: a sign-up is refused with “Signing up is not open for this app.” and a code to a new address gets the usual answer with nothing sent. The workspace’s owners are emailed once that day, and the Overview page shows the day’s count. Paid plans have no daily cap.

A plan includes a number of monthly active users across the workspace’s production environments. At the pause, new sign-ups stop until the month ends or the workspace moves to a larger plan; logins go on.

Plan Warning Sign-ups pause
Free 1,000
Pro 10,000 15,000
Scale 100,000 150,000

Owners are emailed at 80% and at 100% of what the plan includes. Each development environment has its own allowance and pauses on its own: 100 monthly active users on Free, 1,000 on paid plans. See Plans and limits.

None of these protections tells anyone which addresses have accounts:

  • Known and unknown addresses get the same answer to naming an address, a wrong password, a password reset and a sign-up.
  • A wrong password costs the same time whether the account exists or not.
  • A sign-up with an address that has an account gets the usual answer and no working code, and the owner is emailed.
  • With sign-up closed or paused, a code to a new address gets the usual answer and nothing is sent.
  • A code’s expiry is counted from the moment the step began, so the answer is the same to the second.
  • App access is decided only after the user is proven.